Home
last modified time | relevance | path

Searched refs:to (Results 1 – 25 of 1309) sorted by relevance

12345678910>>...53

/hardware/qcom/msm8998/json-c/
Dconfig.h.in9 /* Define to 1 if you have the declaration of `INFINITY', and to 0 if you
13 /* Define to 1 if you have the declaration of `isinf', and to 0 if you don't.
17 /* Define to 1 if you have the declaration of `isnan', and to 0 if you don't.
21 /* Define to 1 if you have the declaration of `nan', and to 0 if you don't. */
24 /* Define to 1 if you have the declaration of `_finite', and to 0 if you
28 /* Define to 1 if you have the declaration of `_isnan', and to 0 if you don't.
32 /* Define to 1 if you have the <dlfcn.h> header file. */
35 /* Define to 1 if you don't have `vprintf' but do have `_doprnt.' */
38 /* Define to 1 if you have the <endian.h> header file. */
41 /* Define to 1 if you have the <fcntl.h> header file. */
[all …]
DDoxyfile3 # This file describes the settings to be used by the documentation system
22 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
28 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
30 # If a relative path is entered, it will be relative to the location
35 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
44 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
46 # information to generate all constant output in the proper language.
56 # This tag can be used to specify the encoding used in the generated output.
59 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
61 # whereas setting the tag to NO uses a Unix-style encoding (the default for
[all …]
DChangeLog19 * change the floating point output format to %.17g so values with
28 * Various changes to fix the build on MSVC.
37 * Added a json_object_new_double_s() convenience function to allow
38 an exact string representation of a double to be specified when
47 * IMPORTANT: the name of the library has changed to libjson-c.so and
49 The pkgconfig name has also changed from json to json-c.
50 You should change your build to use appropriate -I and -l options.
52 continue to work, but that will be removed in the next release.
58 …* Rewrite json_object_object_add to replace just the value if the key already exists so keys remai…
59 * Make it safe to delete keys while iterating with the json_object_object_foreach macro.
[all …]
DCOPYING4 Permission is hereby granted, free of charge, to any person obtaining a
6 to deal in the Software without restriction, including without limitation
7 the rights to use, copy, modify, merge, publish, distribute, sublicense,
8 and/or sell copies of the Software, and to permit persons to whom the
9 Software is furnished to do so, subject to the following conditions:
26 Permission is hereby granted, free of charge, to any person obtaining a
28 to deal in the Software without restriction, including without limitation
29 the rights to use, copy, modify, merge, publish, distribute, sublicense,
30 and/or sell copies of the Software, and to permit persons to whom the
31 Software is furnished to do so, subject to the following conditions:
/hardware/interfaces/tests/msgq/1.0/
DITestMsgQ.hal10 * Unless required by applicable law or agreed to in writing, software
26 * This method requests the service to set up a synchronous read/write
30 * client. Server uses this descriptor to set up a FMQ object at its end.
37 * This method requests the service to return an MQDescriptor to
40 * method is to be used to test multiple reader processes.
47 * set up by the service. Client can use it to set up the FMQ at its end.
52 * This method request the service to write into the synchronized read/write
55 * @param count Number to messages to write.
62 * This method request the service to read from the synchronized read/write
65 * @param count Number to messages to read.
[all …]
/hardware/interfaces/biometrics/face/1.0/
Dtypes.hal10 * Unless required by applicable law or agreed to in writing, software
39 * One of the arguments to the method call is invalid.
62 * Require the user to look at the device during enrollment and
63 * authentication. Note this is to accommodate people who have limited
69 * Require a diverse set of poses during enrollment. Note this is to
91 * e.g. the sensor was unable to process the current image or the HAT was
97 * The current operation took too long to complete. This is intended to
102 * The timeout is a device-specific time meant to optimize power. For
103 * example after 30 seconds of searching for a face it can be use to
111 * storage space remaining to do so.
[all …]
/hardware/interfaces/contexthub/1.0/
DIContexthubCallback.hal10 * Unless required by applicable law or agreed to in writing, software
21 * This callback is passed by the Contexthub service to the HAL
22 * implementation to allow the HAL to send asynchronous messages back
23 * to the service and registered clients of the ContextHub service.
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
45 * to the ContextHub service.
53 * This callback is passed by the Contexthub service to the HAL
[all …]
/hardware/interfaces/tv/tuner/1.0/
DIDescrambler.hal10 * Unless required by applicable law or agreed to in writing, software
22 * Descrambler is used to descramble input data.
29 * It is used by the client to specify a demux as source of this
33 * @param demuxId the id of the demux to be used as descrambler's source.
42 * Set a key token to link descrambler to a key slot
44 * It is used by the client to link a hardware key slot to a descrambler.
45 * A descrambler instance can have only one key slot to link, but a key
48 * @param keyToken the token to be used to link the key slot.
57 * Add packets' PID to the descrambler for descrambling
59 * It is used by the client to specify Package ID (PID) of packets which the
[all …]
/hardware/interfaces/health/1.0/
Dtypes.hal10 * Unless required by applicable law or agreed to in writing, software
70 * suspend, or in suspend and connected to a charger (to watch for battery
71 * overheat due to charging)
77 * not connected to a charger (to watch for a battery drained to zero
83 * power_supply sysfs attribute file paths. Set these to specific paths
84 * to use for the associated battery parameters. Clients must search
85 * for appropriate power_supply attribute files to use, for any paths
90 * batteryStatusPath - file path to read battery charging status.
97 * batteryHealthPath - file path to read battery health.
103 * batteryPresentPath - file path to read battery present status.
[all …]
/hardware/interfaces/bluetooth/1.0/
DIBluetoothHciCallbacks.hal10 * Unless required by applicable law or agreed to in writing, software
19 /** The interface from the Bluetooth Controller to the stack. */
29 * Bluetooth controller to be forwarded to the Bluetooth stack.
30 * @param event is the HCI event to be sent to the Bluetooth stack.
35 * Send an ACL data packet form the controller to the host.
36 * @param data the ACL HCI packet to be passed to the host stack
41 * Send a SCO data packet form the controller to the host.
42 * @param data the SCO HCI packet to be passed to the host stack
/hardware/interfaces/gnss/2.0/
DIGnssCallback.hal10 * Unless required by applicable law or agreed to in writing, software
25 * This interface is required for the HAL to communicate certain information
26 * like status and location info back to the platform, the platform implements
27 * the interfaces and passes a handle to the HAL.
43 * Callback to inform framework of the GNSS HAL implementation's capabilities.
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
63 * If a request is made with independentFromGnss set to true, the framework must avoid
64 * providing locations derived from GNSS locations (such as "fused" location), to help improve
67 * In response to this method call, GNSS HAL can expect zero, one, or more calls to
[all …]
/hardware/interfaces/sensors/2.1/
DISensors.hal10 * Unless required by applicable law or agreed to in writing, software
28 * from the initial call to getSensorsList after a device boot until the
30 * between subsequent calls to getSensorsList, even across restarts of the
39 * The Fast Message Queues (FMQ) that are used to send data between the
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
45 * Data may only be written to the Event FMQ. Data must not be read from
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
50 * must notify the framework that sensor events are available to be read and
[all …]
/hardware/interfaces/gnss/1.1/
DIGnssCallback.hal10 * Unless required by applicable law or agreed to in writing, software
22 * The interface is required for the HAL to communicate certain information
23 * like status and location info back to the platform, the platform implements
24 * the interfaces and passes a handle to the HAL.
28 * Callback to inform framework of the GNSS HAL implementation model & version name.
36 * This must be called in response to IGnss::setCallback
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
49 * If a request is made with independentFromGnss set to true, the framework must avoid
50 * providing locations derived from GNSS locations (such as "fused" location), to help improve
[all …]
/hardware/interfaces/tv/cec/2.0/
DIHdmiCec.hal10 * Unless required by applicable law or agreed to in writing, software
28 * HAL must use it to allocate logical address as specified in CEC section
31 * This method shall be able to be called up to twice to support two Primary
35 * value in CecDeviceType for the call to succeed.
46 * It is used when the system plan to reconfigure Primary Device Type,
47 * hence to tell HAL to release all logical address associated to them,
48 * and change the state back to the beginning.
57 * This value must be used in REPORT_FEATURES message to response
68 * This value must be used in REPORT_FEATURES message to response
81 * This value must be used in REPORT_FEATURES message to response
[all …]
/hardware/interfaces/renderscript/1.0/
DIContext.hal10 * Unless required by applicable law or agreed to in writing, software
21 // TODO: is there any way to keep this documentation in sync with the
28 // TODO: There was some confusion as to why some paramters use vec<> and others
30 // only an input parameter. HIDL is not supposed to include any output
36 * TODO: Do we need to define "selectors"? It may be a property of the
41 * equal to or smaller than the dimensions in the source allocation. A
60 * TODO: Need to relate "offset" back to the terminology in
97 * @param ptr Pointer to client-side data
139 * Returns the handle to a raw buffer that is being managed by the screen
156 * @param allocation Allocation to be modified
[all …]
/hardware/interfaces/media/bufferpool/1.0/
DREADME.md3 A buffer pool enables processes to transfer buffers asynchronously.
6 unwanted latency due to context switching. With help from a buffer pool, a
11 rogue clients, FMQ is used to communicate between a buffer pool and a client
12 process. FMQ is used to send buffer ownership change status from a client
13 process to a buffer pool. Except FMQ, a buffer pool does not use any shared
18 FMQ is used to send buffer ownership status changes to a buffer pool from a
21 to communicate with the buffer pool. So sending an FMQ message on behalf of
25 are sent when a buffer is transferred from a client to another client. FMQ has
30 transaction ID to fetch a buffer from a buffer pool. Since the sender already
32 receiver with the transaction ID. In order to prevent faking a receiver, a
[all …]
/hardware/interfaces/media/bufferpool/2.0/
DREADME.md3 A buffer pool enables processes to transfer buffers asynchronously.
6 unwanted latency due to context switching. With help from a buffer pool, a
11 rogue clients, FMQ is used to communicate between a buffer pool and a client
12 process. FMQ is used to send buffer ownership change status from a client
13 process to a buffer pool. Except FMQ, a buffer pool does not use any shared
18 FMQ is used to send buffer ownership status changes to a buffer pool from a
21 to communicate with the buffer pool. So sending an FMQ message on behalf of
25 are sent when a buffer is transferred from a client to another client. FMQ has
30 transaction ID to fetch a buffer from a buffer pool. Since the sender already
32 receiver with the transaction ID. In order to prevent faking a receiver, a
[all …]
/hardware/interfaces/graphics/bufferqueue/2.0/
DIGraphicBufferProducer.hal10 * Unless required by applicable law or agreed to in writing, software
35 * the consumer. Calling this may cause some buffer slots to be emptied. If
50 * - @p maxDequeuedBuffers is greater than or equal to 1.
51 * - @p maxDequeuedBuffers is greater than or equal to the number of
53 * If any of these conditions do not hold, or if the request to set the new
68 * Assigns a newly created buffer to the given slot index. The client is
69 * expected to mirror the slot-to-buffer mapping so that it is not necessary
70 * to transfer a `HardwareBuffer` object for every dequeue operation.
72 * If @p slot is not a valid slot index corresponding to a dequeued buffer,
73 * the call shall fail with @p status set to `BAD_VALUE`.
[all …]
/hardware/interfaces/sensors/2.0/
DISensors.hal10 * Unless required by applicable law or agreed to in writing, software
32 * from the initial call to getSensorsList after a device boot until the
34 * between subsequent calls to getSensorsList, even across restarts of the
59 * been written to the event queue must be abandoned immediately so that
61 * that are generated prior to the latter activation).
63 * @param sensorHandle is the handle of the sensor to change.
64 * @param enabled set to true to enable, or false to disable the sensor.
72 * The Fast Message Queues (FMQ) that are used to send data between the
73 * framework and the HAL. The callback is used by the HAL to notify the
76 * The Event FMQ is used to transport sensor events from the HAL to the
[all …]
/hardware/interfaces/tv/cec/1.0/
DIHdmiCec.hal10 * Unless required by applicable law or agreed to in writing, software
28 * HAL must use it to configure the hardware so that the CEC commands
30 * be able to be called as many times as necessary in order to support
34 * in the range of valid logical addresses for the call to succeed.
45 * It is used when the system doesn't need to process CEC command any more,
46 * hence to tell HAL to stop receiving commands from the CEC bus, and change
47 * the state back to the beginning.
57 * connected HDMI devices. It is therefore likely to change if the cable is
58 * plugged off and on again. It is advised to call getPhysicalAddress to get
70 * Transmits HDMI-CEC message to other HDMI device.
[all …]
/hardware/interfaces/gnss/1.0/
DIGnss.hal10 * Unless required by applicable law or agreed to in writing, software
42 * It is strongly recommended to use MS_BASED instead.
57 * Flags used to specify which aiding data to delete when calling
78 * Opens the interface and provides the callback routines to the implementation of this
81 * The framework calls this method to instruct the GPS engine to prepare for serving requests
82 * from the framework. The GNSS HAL implementation must respond to all GNSS requests from the
83 * framework upon successful return from this method until cleanup() method is called to
94 * gnssLocationCb(), following the settings from the most recent call to
114 * The cleanup() method is called by the framework to tell the GNSS HAL implementation to
117 * implementation must immediately stop responding to any existing requests until the
[all …]
/hardware/interfaces/biometrics/fingerprint/2.2/
Dtypes.hal10 * Unless required by applicable law or agreed to in writing, software
23 * Anything but START and ACQUIRED_GOOD must be shown to the user as feedback on
24 * how to take action on the current operation. For example,
25 * ACQUIRED_IMAGER_DIRTY may be used to tell the user to clean the sensor if it
26 * is detected to be dirty.
27 * If this causes the current operation to fail, an additional ERROR_CANCELED
28 * must be sent to stop the operation in progress (e.g. enrollment).
34 * authentication pipeline. It is expected to be used to measure latency. For
35 * example, in a camera-based authentication system it's expected to be sent
36 * prior to camera initialization. Note this should be sent whenever
/hardware/interfaces/power/1.0/
DIPower.hal10 * Unless required by applicable law or agreed to in writing, software
20 * runtime startup, such as to set default cpufreq parameters.
30 * inactivity in order to conserve battery power during
33 * Typical actions are to turn on or off devices and adjust
35 * appropriate interfaces to allow the kernel to suspend the
36 * system to low-power sleep state when entering non-interactive
37 * state, and to disallow low-power suspend when the system is in
42 * This function can be called to enter non-interactive state after
43 * turning off the screen (if present) and called to enter
44 * interactive state prior to turning on the screen.
[all …]
/hardware/interfaces/drm/1.2/
DICryptoPlugin.hal10 * Unless required by applicable law or agreed to in writing, software
28 * It allows crypto sessions to be opened and operated on, to
29 * load crypto keys for a codec to decrypt protected video content.
34 * Decrypt an array of subsamples from the source memory buffer to the
40 * @param secure a flag to indicate if a secure decoder is being used. This
41 * enables the plugin to configure buffer modes to work consistently with
43 * @param the keyId for the key that is used to do the the decryption. The
44 * keyId refers to a key in the associated MediaDrm instance.
45 * @param iv the initialization vector to use
46 * @param mode the crypto mode to use
[all …]
/hardware/interfaces/wifi/supplicant/1.0/
DISupplicantP2pIfaceCallback.hal10 * Unless required by applicable law or agreed to in writing, software
23 * Clients need to host an instance of this HIDL interface object and
24 * pass a reference of the object to the supplicant via the
73 * Used to indicate that a new network has been added.
75 * @param id Network ID allocated to the corresponding network.
80 * Used to indicate that a network has been removed.
82 * @param id Network ID allocated to the corresponding network.
87 * Used to indicate that a P2P device has been found.
92 * @param primaryDeviceType Type of device. Refer to section B.1 of Wifi P2P
97 * @param deviceCapabilities Refer to section 4.1.4 of Wifi P2P Technical
[all …]

12345678910>>...53