/hardware/interfaces/tv/hdmi/ |
D | README.md | 3 This directory bundles 3 HDMI-related AIDL HALs: HDMI Connection HAL, CEC HAL and eARC HAL. 5 The HDMI Connection HAL contains general APIs for the HDMI Connection. These methods are required by 7 Connection HAL and the CEC HAL. Devices that implement eARC need to support the HDMI Connection HAL 8 and the eARC HAL. 11 reasons, e.g. Display HAL and TV Input HAL.
|
/hardware/interfaces/bluetooth/a2dp/1.0/ |
D | IBluetoothAudioHost.hal | 20 * HAL interface for Bluetooth A2DP Offload functionality where 25 * This interface is from HAL server to HAL client. 27 * The HAL server must call into the IBluetoothAudioHost to initiate 35 * Invoked when the start stream is requested from HAL server 36 * to HAL client. This indicates that the HAL server 38 * HAL client can proceed with the streaming procedure. The 39 * result of the operation must be provided by the HAL 45 * Invoked when the suspend stream is requested from HAL server 46 * to HAL client. This indicates that the HAL server 48 * operation must be provided by the HAL client using the [all …]
|
D | IBluetoothAudioOffload.hal | 22 * HAL interface for Bluetooth A2DP Offload functionality where 27 * This interface is from HAL client to HAL server. 29 * The HAL client must provide the handle of IBluetoothAudioHost as well 30 * as codec configuration to the HAL server, when its connected to an 31 * active A2DP Sink device. HAL Server, based on the feedback from the Audio 33 * HAL client must call into IBluetoothAudioOffload to provide the status of 34 * these commands. Once the device becomes inactive, the HAL client must 35 * call the endSession to terminate the session with the HAL server. 40 * Indicates that the HAL client is connected to an A2DP Sink device 51 * SUCCESS if HAL server successfully initializes the platform with the [all …]
|
/hardware/interfaces/camera/provider/ |
D | README.md | 1 ## Camera Provider HAL ## 6 The camera.provider HAL is used by the Android camera service to discover, 12 More complete information about the Android camera HAL and subsystem can be found at 21 Common enum and struct definitions for all camera HAL interfaces. Does not 28 First HIDL version of the camera provider HAL, closely matching the feature set 29 and operation of the pre-HIDL camera HAL module v2.4. 35 First HIDL version of the camara provider HAL callback interface, closely 36 matching the feature set and operation of the pre-HIDL camera HAL module 39 ### AIDL Camera HAL Default Implementation ###
|
/hardware/qcom/data/ipacfg-mgr/msm8998/hal/src/ |
D | HAL.cpp | 65 HAL* HAL::makeIPAHAL(int version, IOffloadManager* mgr) { in makeIPAHAL() 71 HAL* ret = new HAL(mgr); in makeIPAHAL() 80 HAL::HAL(IOffloadManager* mgr) : mLogs("HAL Function Calls", 100) { in HAL() function in HAL 87 void HAL::registerAsSystemService() { in registerAsSystemService() 103 void HAL::doLogcatDump() { in doLogcatDump() 114 HAL::BoolResult HAL::makeInputCheckFailure(string customErr) { in makeInputCheckFailure() 121 HAL::BoolResult HAL::ipaResultToBoolResult(RET in) { in ipaResultToBoolResult() 164 vector<string> HAL::convertHidlStrToStdStr(hidl_vec<hidl_string> in) { in convertHidlStrToStdStr() 173 void HAL::registerEventListeners() { in registerEventListeners() 178 void HAL::registerIpaCb() { in registerIpaCb() [all …]
|
/hardware/qcom/sm8150/data/ipacfg-mgr/hal/src/ |
D | HAL.cpp | 65 Return<::android::sp<HAL>> HAL::makeIPAHAL(int version, IOffloadManager* mgr) { in makeIPAHAL() 73 ::android::sp<HAL> ret = new HAL(mgr); in makeIPAHAL() 82 HAL::HAL(IOffloadManager* mgr) : mLogs("HAL Function Calls", 50) { in HAL() function in HAL 89 void HAL::registerAsSystemService(const char* name) { in registerAsSystemService() 105 void HAL::doLogcatDump() { in doLogcatDump() 116 HAL::BoolResult HAL::makeInputCheckFailure(string customErr) { in makeInputCheckFailure() 123 HAL::BoolResult HAL::ipaResultToBoolResult(RET in) { in ipaResultToBoolResult() 166 vector<string> HAL::convertHidlStrToStdStr(hidl_vec<hidl_string> in) { in convertHidlStrToStdStr() 175 void HAL::registerEventListeners() { in registerEventListeners() 180 void HAL::registerIpaCb() { in registerIpaCb() [all …]
|
/hardware/interfaces/sensors/common/default/2.X/multihal/tests/fake_subhal/ |
D | README | 2 provided for sensors HAL 2.0 to support multi-HAL 2.0. It should be used as a 3 means to verify the multi-HAL 2.0 implementation can successfully load and 6 This sub-HAL implementation has two macros that can be used to configure support 11 but more targets could be added to support both in one sub-HAL or none at all, 17 Take this .so and place it where the multi-HAL config will cause the HalProxy to 19 to cause the multi-HAL to restart and attempt to load in the sub-HAL.
|
/hardware/qcom/camera/msm8998/QCamera2/ |
D | Android.mk | 57 HAL/QCamera2HWI.cpp \ 58 HAL/QCameraMuxer.cpp \ 59 HAL/QCameraMem.cpp \ 60 HAL/QCameraStateMachine.cpp \ 61 HAL/QCameraChannel.cpp \ 62 HAL/QCameraStream.cpp \ 63 HAL/QCameraPostProc.cpp \ 64 HAL/QCamera2HWICallbacks.cpp \ 65 HAL/QCameraParameters.cpp \ 66 HAL/QCameraParametersIntf.cpp \ [all …]
|
/hardware/interfaces/camera/ |
D | README.md | 6 The camera.* HAL tree is used by the Android camera service to discover and 9 More details and versioning information can be found within each particular HAL. 11 More complete information about the Android camera HAL and subsystem can be found at 14 ### AIDL Camera HAL Interfaces 16 The AIDL Camera HAL interfaces can be found in the respective <interface>/aidl
|
/hardware/interfaces/camera/device/ |
D | README.md | 1 ## Camera Device HAL ## 6 The camera.device HAL interface is used by the Android camera service to operate 7 individual camera devices. Instances of camera.device HAL interface can be obtained 16 More complete information about the Android camera HAL and subsystem can be found at 23 HIDL version of the legacy camera device HAL. Intended as a shim for devices 24 needing to use the deprecated pre-HIDL camera device HAL v1.0. 33 This HAL interface version only allows support at the LEGACY level for the 47 Callback interface for sending events and data buffers from the HAL to the 52 HIDL version of the baseline camera device HAL, required for LIMITED or FULL 55 The main HAL contains methods for static queries about the device, similar to [all …]
|
/hardware/interfaces/broadcastradio/aidl/rust_impl/ |
D | README.md | 1 # Rust Skeleton BroadcastRadio HAL implementation. 3 WARNING: This is not a reference BroadcastRadio HAL implementation and does 6 This folder contains a skeleton broadcast radio HAL implementation in Rust to 7 demonstrate how vendor may implement a Rust broadcast radio HAL. To run this 8 broadcast radio HAL, include `android.hardware.broadcastradio-rust-service`
|
/hardware/interfaces/audio/ |
D | README.md | 1 # Audio HAL 3 Directory structure of the audio HAL related code. 5 ## Directory Structure for AIDL audio HAL 17 between various HALs: BT HAL, core and effects audio HALs. 19 core audio HAL. 20 * `default` — the default, reference implementation of the audio HAL service. 21 * `vts` — VTS tests for the AIDL HAL. 23 ## Directory Structure for HIDL audio HAL 26 HAL based on an existing one. Note that this isn't possible since Android T 27 release. Android U and above uses AIDL audio HAL. [all …]
|
/hardware/libhardware/modules/camera/3_4/ |
D | README.md | 6 introduce some [caveats](#V4L2-Deficiencies), causing this HAL to 13 camera HAL implementation which is maintained by Android Camera team 17 ## Building a Device with the HAL 19 To ensure the HAL is built for a device, include the following in your 28 The first line ensures the V4L2 HAL module is visible to the build system. 32 to load the V4L2 HAL instead of a default Camera HAL. 34 ## Requirements for Using the HAL 36 Devices and cameras wishing to use this HAL must meet 43 ## Understanding the HAL Code 45 There are three large pieces to the V4L2 Camera HAL: the general HALv3 [all …]
|
/hardware/interfaces/contexthub/1.0/ |
D | IContexthubCallback.hal | 21 * This callback is passed by the Contexthub service to the HAL 22 * implementation to allow the HAL to send asynchronous messages back 31 * This callback is passed by the Contexthub service to the HAL 32 * implementation to allow the HAL to send the response for a 43 * This callback is passed by the Contexthub service to the HAL 44 * implementation to allow the HAL to send an asynchronous event 53 * This callback is passed by the Contexthub service to the HAL 54 * implementation to allow the HAL to send a notification to the service 67 * This callback is passed by the Contexthub service to the HAL 68 * implementation to allow the HAL to send information about the
|
/hardware/interfaces/gnss/1.1/ |
D | IGnssCallback.hal | 22 * The interface is required for the HAL to communicate certain information 24 * the interfaces and passes a handle to the HAL. 28 * Callback to inform framework of the GNSS HAL implementation model & version name. 30 * This is a user-visible string that identifies the model and version of the GNSS HAL. 38 * @param name String providing the name of the GNSS HAL implementation 45 * HAL implementation must call this when it wants the framework to provide locations to assist 46 * with GNSS HAL operation, for example, to assist with time to first fix, error recovery, or to 47 * supplement GNSS location for other clients of the GNSS HAL. 53 * In response to this method call, GNSS HAL can expect zero, one, or more calls to 55 * from other sources, which may happen at some arbitrary delay. Generally speaking, HAL
|
/hardware/interfaces/gnss/2.0/ |
D | IGnssCallback.hal | 25 * This interface is required for the HAL to communicate certain information 27 * the interfaces and passes a handle to the HAL. 43 * Callback to inform framework of the GNSS HAL implementation's capabilities. 52 * @param location Location information from HAL. 59 * HAL implementation must call this when it wants the framework to provide locations to assist 60 * with GNSS HAL operation, for example, to assist with time to first fix, error recovery, or to 61 * supplement GNSS location for other clients of the GNSS HAL. 67 * In response to this method call, GNSS HAL can expect zero, one, or more calls to 69 * from other sources, which may happen at some arbitrary delay. Generally speaking, HAL 85 * In this version of the HAL, the field 'constellation' in the v1_0 struct is deprecated, [all …]
|
/hardware/interfaces/security/keymint/ |
D | README.md | 1 # KeyMint HAL 3 This directory contains the HAL definition for KeyMint. KeyMint provides 6 Note that the `IRemotelyProvisionedComponent` HAL, and it's associated types, 7 used to also be defined in this directory. As of Android U, this HAL has been
|
/hardware/interfaces/camera/device/3.2/ |
D | ICameraDeviceSession.hal | 41 * This must be a non-blocking call. The HAL should return from this call 52 * The camera HAL does not support the input template type 69 * Reset the HAL camera device processing pipeline and set up new input and 82 * If the HAL needs to change the stream configuration for an existing 89 * If a currently-active stream is not included in streamList, the HAL may 95 * requestedConfiguration. Upon return, the HAL device must set producerUsage, 112 * release sync fences have been signaled by the HAL. The framework must not 118 * The HAL device must configure itself to provide maximum possible output 127 * Nevertheless, the HAL device should attempt to minimize the 132 * The HAL should return from this call in 500ms, and must return from this [all …]
|
D | types.hal | 28 * The type of the camera stream, which defines whether the camera HAL device is 34 * This stream is an output stream; the camera HAL device must fill buffers 40 * This stream is an input stream; the camera HAL device must read buffers 86 * This defines the general operation mode for the HAL (for a given stream 94 * operation mode, where all semantics of HAL APIs and metadata controls 104 * mode can still be used for high speed output if the HAL can support high 105 * speed output while satisfying all the semantics of HAL APIs and metadata 106 * controls. It is recommended for the HAL to support high speed output in 112 * 1. The HAL must support up to 2 streams with sizes reported by 114 * 2. In this mode, the HAL is expected to output up to 120fps or [all …]
|
/hardware/interfaces/sensors/2.1/ |
D | ISensors.hal | 31 * HAL and its dependencies (for example, the sensor handle for a given 32 * sensor must not change across HAL restarts). 37 * Initialize the Sensors HAL's Fast Message Queues (FMQ) and callback. 40 * framework and the HAL. The callback is used by the HAL to notify the 43 * The Event FMQ is used to transport sensor events from the HAL to the 47 * sensor events, the HAL writes the sensor events to the Event FMQ. 49 * Once the HAL is finished writing sensor events to the Event FMQ, the HAL 62 * The Wake Lock FMQ is used by the framework to notify the HAL when it is 66 * Lock FMQ. When the HAL reads the data from the Wake Lock FMQ, the HAL 69 * zero. It is important to note that the HAL must acquire the wake lock and [all …]
|
/hardware/interfaces/camera/common/ |
D | README.md | 1 ## Camera common HAL definitions ## 9 This includes standard status codes returned by most camera HAL methods. 11 More complete information about the Android camera HAL and subsystem can be found at 20 Common enum and struct definitions for all camera HAL interfaces. Does not
|
/hardware/interfaces/biometrics/fingerprint/aidl/default/ |
D | README.md | 1 # Virtual Fingerprint HAL 3 This is a virtual HAL implementation that is backed by system properties instead 10 This HAL can be used on emulators, like cuttlefish, or on real devices. Add the 17 The virtual HAL will be ignored if a real HAL is also installed on the target 19 switch to the virtual HAL. Unset it and reboot again to switch back. 80 …mage acquisition states at HAL are reported to framework via onAcquired() callback. The valid acqu… 87 The states can be specified in sequence for the HAL operations involving fingerprint image captures… 109 The valid error codes for AIDL HAL include 116 There are many HAL operations which can result in errors, refer to [here](fingerprint.sysprop) file… 124 Three HAL operations (authenticate, enrollment and detect interaction) latency can be optionally sp… [all …]
|
/hardware/interfaces/automotive/audiocontrol/aidl/rust_impl/ |
D | README.md | 1 # Rust Skeleton Audio Control HAL implementation. 6 This folder contains a skeleton audio control HAL implementation in Rust to 7 demonstrate how vendor may implement a Rust audio control HAL. To run this 8 audio control HAL, include
|
/hardware/interfaces/bluetooth/audio/2.1/ |
D | IBluetoothAudioProvider.hal | 24 * HAL interface from the Bluetooth stack to the Audio HAL 27 * sessions and sends callback events to the Audio HAL. 37 * current negotiated codec to the Audio HAL. After this method is called, 38 * the Audio HAL can invoke IBluetoothAudioPort.startStream(). 50 * the Audio HAL 51 * UNSUPPORTED_CODEC_CONFIGURATION if the Audio HAL cannot register this 53 * FAILURE if the Audio HAL cannot register this IBluetoothAudioPort for
|
/hardware/interfaces/gnss/visibility_control/1.0/ |
D | IGnssVisibilityControl.hal | 24 * This interface is used to tell the GNSS HAL implementation whether the framework user has 25 * granted permission to the GNSS HAL implementation to provide GNSS location information for 30 * the GNSS HAL implementation must serve the emergency location supporting network initiated 33 * There is no separate need for the GNSS HAL implementation to monitor the global device location 41 * For device user visibility, the GNSS HAL implementation must call the method 46 * The HAL implementations that support this interface must not report GNSS location, measurement, 48 * expressly authorized by this HAL. This includes all endpoints for location information 53 * Enables/disables non-framework entity location access permission in the GNSS HAL. 55 * The framework will call this method to update GNSS HAL implementation every time the 60 * Whenever the user location information is delivered to non-framework entities, the HAL [all …]
|