Home
last modified time | relevance | path

Searched refs:bridge (Results 1 – 25 of 28) sorted by relevance

12

/system/core/libappfuse/
DFuseBridgeLoop.cc264 bool AddBridgePoll(FuseBridgeEntry* bridge) const { in AddBridgePoll()
265 return InvokeControl(EPOLL_CTL_ADD, bridge); in AddBridgePoll()
268 bool UpdateOrDeleteBridgePoll(FuseBridgeEntry* bridge) const { in UpdateOrDeleteBridgePoll()
270 bridge->state_ != FuseBridgeState::kClosing ? EPOLL_CTL_MOD : EPOLL_CTL_DEL, bridge); in UpdateOrDeleteBridgePoll()
290 bool InvokeControl(int op, FuseBridgeEntry* bridge) const { in InvokeControl()
291 LOG(VERBOSE) << "InvokeControl op=" << op << " bridge=" << bridge->mount_id_ in InvokeControl()
292 << " state=" << static_cast<int>(bridge->state_) in InvokeControl()
293 << " last_state=" << static_cast<int>(bridge->last_state_); in InvokeControl()
299 GetObservedEvents(bridge->last_state_, &last_device_events, &last_proxy_events); in InvokeControl()
300 GetObservedEvents(bridge->state_, &device_events, &proxy_events); in InvokeControl()
[all …]
/system/sepolicy/prebuilts/api/26.0/public/
Dbufferhubd.te17 # connects to bufferhubd via PDX. Instead, a VR app acts as a bridge between
Dmediacodec.te44 # directly connects to bufferhubd via PDX. Instead, a VR app acts as a bridge
/system/sepolicy/prebuilts/api/28.0/public/
Dbufferhubd.te17 # connects to bufferhubd via PDX. Instead, a VR app acts as a bridge between
Dmediacodec.te47 # directly connects to bufferhubd via PDX. Instead, a VR app acts as a bridge
/system/sepolicy/prebuilts/api/27.0/public/
Dbufferhubd.te17 # connects to bufferhubd via PDX. Instead, a VR app acts as a bridge between
Dmediacodec.te46 # directly connects to bufferhubd via PDX. Instead, a VR app acts as a bridge
/system/core/adb/
Dprotocol.txt13 The host side becomes a simple comms bridge with no "UI", which will
15 a device or emulator that is connected to the bridge.
124 * "fs-bridge" - FUSE protocol filesystem bridge
190 is broken. It was only used internally to the bridge and never valid
215 The core of the bridge program will use three threads. One thread
230 The bridge program will be able to have a number of mini-servers
232 "shell", "fs-bridge", etc) and upon receiving an OPEN() to such a
233 service, the bridge program will create a stream socketpair and spawn
/system/sepolicy/prebuilts/api/29.0/public/
Dbufferhubd.te18 # connects to bufferhubd via PDX. Instead, a VR app acts as a bridge between
Dhal_omx.te16 # directly connects to bufferhubd via PDX. Instead, a VR app acts as a bridge
/system/sepolicy/public/
Dbufferhubd.te18 # connects to bufferhubd via PDX. Instead, a VR app acts as a bridge between
Dhal_omx.te16 # directly connects to bufferhubd via PDX. Instead, a VR app acts as a bridge
/system/sepolicy/prebuilts/api/27.0/private/
Daudioserver.te45 # For A2DP bridge which is loaded directly into audioserver
Dzygote.te75 # Native bridge functionality requires that zygote replaces
/system/sepolicy/prebuilts/api/26.0/private/
Daudioserver.te45 # For A2DP bridge which is loaded directly into audioserver
Dzygote.te75 # Native bridge functionality requires that zygote replaces
/system/tools/aidl/
Daidl_language_l.ll16 %option bison-bridge
/system/sepolicy/prebuilts/api/28.0/private/
Daudioserver.te55 # For A2DP bridge which is loaded directly into audioserver
Dzygote.te76 # Native bridge functionality requires that zygote replaces
/system/sepolicy/private/
Daudioserver.te60 # For A2DP bridge which is loaded directly into audioserver
Dzygote.te82 # Native bridge functionality requires that zygote replaces
/system/sepolicy/prebuilts/api/29.0/private/
Daudioserver.te60 # For A2DP bridge which is loaded directly into audioserver
Dzygote.te82 # Native bridge functionality requires that zygote replaces
/system/tools/hidl/
Dhidl-gen_l.ll78 %option bison-bridge
/system/tools/hidl/c2hal/
Dc2hal_l.ll89 %option bison-bridge

12