Home
last modified time | relevance | path

Searched refs:HAL (Results 1 – 25 of 121) sorted by relevance

12345

/hardware/interfaces/camera/provider/
DREADME.md1 ## 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
/hardware/qcom/data/ipacfg-mgr/msm8998/hal/src/
DHAL.cpp65 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/camera/msm8998/QCamera2/
DAndroid.mk51 HAL/QCamera2HWI.cpp \
52 HAL/QCameraMuxer.cpp \
53 HAL/QCameraMem.cpp \
54 HAL/QCameraStateMachine.cpp \
55 HAL/QCameraChannel.cpp \
56 HAL/QCameraStream.cpp \
57 HAL/QCameraPostProc.cpp \
58 HAL/QCamera2HWICallbacks.cpp \
59 HAL/QCameraParameters.cpp \
60 HAL/QCameraParametersIntf.cpp \
[all …]
/hardware/interfaces/camera/device/
DREADME.md1 ## 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/libhardware/modules/camera/3_4/
DREADME.md6 introduce some [caveats](#V4L2-Deficiencies), causing this HAL to
9 ## Building a Device with the HAL
11 To ensure the HAL is built for a device, include the following in your
20 The first line ensures the V4L2 HAL module is visible to the build system.
24 to load the V4L2 HAL instead of a default Camera HAL.
26 ## Requirements for Using the HAL
28 Devices and cameras wishing to use this HAL must meet
35 ## Understanding the HAL Code
37 There are three large pieces to the V4L2 Camera HAL: the general HALv3
38 Camera & HAL code, the specific implementation using V4L2,
[all …]
/hardware/interfaces/contexthub/1.0/
DIContexthubCallback.hal21 * 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/camera/device/3.2/
DICameraDeviceSession.hal41 * 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 * set to 0. The usage must be set to the consumer usage flags. The HAL
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 …]
Dtypes.hal28 * 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 …]
DICameraDeviceCallback.hal23 * Callback methods for the HAL to call into the framework.
29 * The framework must not call back into the HAL from within these callbacks,
40 * processCaptureResult() may be invoked multiple times by the HAL in
46 * may be made at a time by the HAL although the calls may come from
47 * different threads in the HAL.
51 * and the result metadata, must be returned by the HAL for each request in
73 * The HAL retains ownership of result structure, which only needs to be
78 * data. Therefore, this method should be called by the HAL as soon as
80 * being filled. The HAL must include valid release sync fences into each
84 * If the result buffer cannot be constructed for a request, the HAL must
[all …]
/hardware/interfaces/camera/common/
DREADME.md1 ## 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/broadcastradio/1.0/
DITunerCallback.hal23 * Method called by the HAL when a HW failure occurs.
29 * Method called by the HAL when a new configuration is applied
39 * Method called by the HAL when a tuning operation completes
47 * Method called by the HAL when a frequency switch occurs.
53 * Method called by the HAL when the antenna connection state changes.
59 * Method called by the HAL when a traffic announcement starts or
66 * Method called by the HAL when an emergency announcement starts
73 * Method called by the HAL when metadata for current station
/hardware/interfaces/camera/device/1.0/
DICameraDevice.hal24 * Camera device HAL, legacy version
26 * DEPRECATED. New devices are strongly recommended to use Camera HAL v3.2 or
45 * An unexpected internal camera HAL error occurred, and the
68 * An unexpected internal camera HAL error occurred, and the
85 * camera ID. If the operation is successful, HAL must notify the framework
101 * flash unit, if HAL cannot keep multiple torch modes on simultaneously,
102 * HAL must turn off the torch mode that was turned on by
159 * @param callback Interface to invoke by the HAL for device callbacks.
202 * HAL must not rely on its client to call releaseRecordingFrame() to
203 * release video recording frames sent out by the cameral HAL before and
[all …]
/hardware/libhardware/tests/vehicle/
DREADME4 HAL. It lists the various places to look for code and how to build and test the
8 vehicle HAL.
13 a) hardware/libhardware/include/hardware/vehicle.h - this is the main HAL
16 various units, capabilities and any other relevant details about the HAL design
22 critical HAL functions such as, get(), set() and subscribe().
26 features of HAL implementation. Things such as loading of HAL and
33 HAL such as:
35 ii) Setting a property (and the HAL will take some setting action).
36 iii) Subscribe to a property (and the HAL should send you values at some certain
/hardware/interfaces/audio/2.0/
DIDevice.hal44 * Get the current master volume value for the HAL, if the HAL supports
46 * from the primary audio HAL when the service starts and use the value for
81 * Get the current master mute status for the HAL, if the HAL supports
83 * audio HAL when the service starts and use the value for setting the
84 * initial master mute across all HALs. HAL must indicate that the feature
106 * HAL must provide suggested values for the audio config.
128 * HAL must provide suggested values for the audio config.
150 * Returns whether HAL supports audio patches.
158 * is allocated by the HAL and must be unique for this audio HAL module.
180 * needed by the HAL to identify the port.
[all …]
DIPrimaryDevice.hal34 * This method is used to notify the HAL about audio mode changes.
44 * on the legacy HAL.
54 * on the legacy HAL.
63 * equivalent to getting AUDIO_PARAMETER_KEY_BT_SCO_WB on the legacy HAL.
72 * equivalent to setting AUDIO_PARAMETER_KEY_BT_SCO_WB on the legacy HAL.
88 * getting AUDIO_PARAMETER_KEY_TTY_MODE on the legacy HAL.
97 * AUDIO_PARAMETER_KEY_TTY_MODE on the legacy HAL.
107 * AUDIO_PARAMETER_KEY_HAC on the legacy HAL.
117 * AUDIO_PARAMETER_KEY_HAC on the legacy HAL.
DIStream.hal34 * to getting AUDIO_PARAMETER_STREAM_FRAME_COUNT on the legacy HAL.
58 * legacy HAL.
66 * to setting AUDIO_PARAMETER_STREAM_SAMPLING_RATE on the legacy HAL.
83 * HAL.
91 * setting AUDIO_PARAMETER_STREAM_CHANNELS on the legacy HAL.
108 * HAL.
116 * setting AUDIO_PARAMETER_STREAM_FORMAT on the legacy HAL.
172 * equivalent to setting AUDIO_PARAMETER_STREAM_ROUTING in the legacy HAL
183 * HAL.
194 * setting AUDIO_PARAMETER_STREAM_HW_AV_SYNC on the legacy HAL.
[all …]
/hardware/interfaces/camera/
DREADME.md6 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
/hardware/interfaces/broadcastradio/1.1/
DITunerCallback.hal23 * @1.0:ITunerCallback. All 1.1 HAL implementations must call both
29 * Method called by the HAL when a tuning operation completes
33 * The 1.0 callback must not be called when HAL implementation detects
46 * Called by the HAL when background scan feature becomes available or not.
54 * Called by the HAL when background scan initiated by startBackgroundScan
65 * Called each time the internally cached program list changes. HAL may not
80 * Method called by the HAL when current program information (including
90 * 1.0 callbacks must not be called when HAL implementation detects
/hardware/interfaces/gnss/1.0/
DIGnssNavigationMessage.hal33 * Initializes the interface and registers the callback routines with the HAL.
34 * After a successful call to 'setCallback' the HAL must begin to provide updates as
43 * expected that the HAL will not generate any updates upon returning
49 * Stops updates from the HAL, and unregisters the callback routines.
51 * considered invalid by the HAL.
DIGnssNi.hal22 * to respond to NI notifications originating from the HAL.
26 * Registers the callbacks for HAL to use.
33 * Sends a response to HAL.
35 * @param notifId An ID generated by HAL to associate NI notifications and
DIGnssMeasurement.hal33 * Initializes the interface and registers the callback routines with the HAL.
34 * After a successful call to 'setCallback' the HAL must begin to provide updates at
44 * Returns ERROR_GENERIC for any other error. The HAL must
50 * Stops updates from the HAL, and unregisters the callback routines.
52 * considered invalid by the HAL.
/hardware/interfaces/wifi/1.1/default/
DTHREADING.README1 Vendor HAL Threading Model
3 The vendor HAL service has two threads:
6 2. Legacy HAL event loop thread: This is the thread forked off for processing
7 the legacy HAL event loop (wifi_event_loop()). This thread is used to process
9 callbacks passed to the legacy HAL API's are invoked on this thread.
/hardware/interfaces/wifi/1.0/
DIWifi.hal23 * This is the root of the HAL module and is the interface returned when
24 * loading an implementation of the Wi-Fi HAL. There must be at most one
29 * Requests notifications of significant events for the HAL. Multiple calls to
32 * state of the rest of the HAL and must persist though stops/starts. These
48 * Get the current state of the HAL.
71 * stopped then this must be a noop. If the HAL is already stopped or it
77 * Calling stop then start is a valid way of resetting state in the HAL,
/hardware/interfaces/tv/cec/1.0/
DIHdmiCec.hal22 * HDMI-CEC HAL interface definition.
28 * HAL must use it to configure the hardware so that the CEC commands
46 * hence to tell HAL to stop receiving commands from the CEC bus, and change
62 * FAILURE_INVALID_STATE if HAL cannot retrieve the physical
88 * Sets a callback that HDMI-CEC HAL must later use for incoming CEC
125 * Sets flags controlling the way HDMI-CEC service works down to HAL
127 * in HAL itself, firmware or microcontroller.
137 * three-letter code as defined in ISO/FDIS 639-2. Must be used for HAL to
161 * @return status True if a device is connected, otherwise false. The HAL
/hardware/qcom/data/ipacfg-mgr/msm8998/hal/inc/
DHAL.h68 class HAL : public IOffloadControl, IOffloadConfig {
125 static HAL* makeIPAHAL(int /* version */, IOffloadManager* /* mgr */);
173 HAL(IOffloadManager* /* mgr */);

12345