Searched full:status (Results 1 – 25 of 799) sorted by relevance
12345678910>>...32
| /Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 38 - secure-status : specifies whether the device is present and usable
39 in the secure world. The combination of this with "status" allows
41 specified. If "secure-status" is not specified it defaults to the
42 same value as "status"; if "status" is not specified either then
47 secure-status = "okay"; /* visible in both */
48 status = "okay"; /* visible in both */
49 status = "okay"; secure-status = "okay"; /* visible in both */
50 secure-status = "disabled"; /* NS-only */
51 status = "okay"; secure-status = "disabled"; /* NS-only */
52 status = "disabled"; secure-status = "okay"; /* S-only */
[all …]
|
| /Documentation/arch/riscv/ |
| D | vector.rst | 14 status for the use of Vector in userspace. The intended usage guideline for
26 Sets the Vector enablement status of the calling thread, where the control
30 Enablement status is a tri-state value each occupying 2-bit of space in
34 enablement status on execve(). The system-wide default setting can be
49 enablement status of current thread, and the setting at bit[3:2] takes place
54 Vector enablement status for the calling thread. The calling thread is
57 but the current enablement status is not off. Setting
59 the original enablement status.
64 then the enablement status will be decided by the system-wide
65 enablement status when execve() happen.
[all …]
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-receive.rst | 153 to :ref:`CEC_RX_STATUS_TIMEOUT <CEC-RX-STATUS-TIMEOUT>` or
154 :ref:`CEC_RX_STATUS_FEATURE_ABORT <CEC-RX-STATUS-FEATURE-ABORT>`.
165 - The status bits of the received message. See
166 :ref:`cec-rx-status` for the possible status values.
169 - The status bits of the transmitted message. See
170 :ref:`cec-tx-status` for the possible status values.
175 :ref:`CEC_TX_STATUS_NACK <CEC-TX-STATUS-NACK>` without ever actually
182 :ref:`CEC_TX_STATUS_ARB_LOST <CEC-TX-STATUS-ARB-LOST>` status bit is set.
188 :ref:`CEC_TX_STATUS_NACK <CEC-TX-STATUS-NACK>` status bit is set.
194 :ref:`CEC_TX_STATUS_LOW_DRIVE <CEC-TX-STATUS-LOW-DRIVE>` status bit is set.
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-read-status.rst | 13 FE_READ_STATUS - Returns status information about the front-end. This call only requires - read-onl…
20 ``int ioctl(int fd, FE_READ_STATUS, unsigned int *status)``
28 ``status``
36 used to check about the locking status of the frontend after being
37 tuned. The ioctl takes a pointer to an integer where the status will be
42 The size of status is actually sizeof(enum fe_status), with
|
| D | dvb-fe-read-status.rst | 3 .. _dvb-fe-read-status:
6 Querying frontend status and statistics
11 tuner lock status and provide statistics about the quality of the
14 The information about the frontend tuner locking status can be queried
|
| /Documentation/hwmon/ |
| D | max31827.rst | 56 devicetree. In Comparator mode, the OT/UT status bits have a value of 1 when the
58 the Fault Queue selection. OT status returns to 0 when the temperature drops
59 below the TH_HYST value or when shutdown mode is entered. Similarly, UT status
63 In interrupt mode exceeding TH also sets OT status to 1, which remains set until
64 a read operation is performed on the configuration/status register (max or min
65 attribute); at this point, it returns to 0. Once OT status is set to 1 from
69 to the operation of the UT status bit.
71 Putting the MAX31827 into shutdown mode also resets the OT/UT status bits. Note
72 that if the mode is changed while OT/UT status bits are set, an OT/UT status
74 it is recommended to perform a read of the configuration/status register to
[all …]
|
| D | max8688.rst | 55 in1_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
56 in1_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
58 status.
60 status.
70 curr1_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
79 status is set.
82 status is set.
|
| D | pmbus.rst | 203 inX_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
204 inX_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
206 From VOLTAGE_UV_FAULT status.
208 From VOLTAGE_OV_FAULT status.
223 From IIN_OC_WARNING or IOUT_OC_WARNING status.
225 From IIN_OC_WARN_LIMIT or IOUT_OC_WARN_LIMIT status.
227 From IOUT_UC_FAULT status.
229 From IIN_OC_FAULT or IOUT_OC_FAULT status.
243 From PIN_OP_WARNING or POUT_OP_WARNING status.
245 From POUT_OP_FAULT status.
[all …]
|
| D | ucd9200.rst | 68 in1_min_alarm Voltage low alarm. From VIN_UV_WARNING status.
69 in1_max_alarm Voltage high alarm. From VIN_OV_WARNING status.
70 in1_lcrit_alarm Voltage critical low alarm. From VIN_UV_FAULT status.
71 in1_crit_alarm Voltage critical high alarm. From VIN_OV_FAULT status.
80 in[2-5]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
81 in[2-5]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
83 status.
85 status.
97 curr[2-5]_max_alarm Current high alarm. From IOUT_OC_WARNING status.
98 curr[2-5]_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
|
| D | max16064.rst | 55 in[1-4]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
56 in[1-4]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
58 status.
60 status.
69 status is set.
72 status is set.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-bno055 | 55 Reports the autocalibration status for the accelerometer sensor.
57 the number, the better the calibration status.
63 Reports the autocalibration status for the gyroscope sensor.
65 the number, the better the calibration status.
71 Reports the autocalibration status for the magnetometer sensor.
73 the number, the better the calibration status.
79 Reports the status for the IMU overall autocalibration.
81 the number, the better the calibration status.
|
| D | sysfs-class-firmware | 28 upload. This string will be in the form of <STATUS>:<ERROR>,
29 where <STATUS> will be one of the status strings described
30 for the status sysfs file and <ERROR> will be one of the
34 upload status is "idle". If this file is read while a firmware
62 What: /sys/class/firmware/.../status
66 Description: Read-only. Returns a string describing the current status of
|
| D | sysfs-devices-platform-ACPI-TAD | 15 BIT(4): Correct status reported for wakeups from S4/S5 if set
38 sleep state (and from S4/S5 too if supported) until its status
61 (RW) The AC alarm status.
64 timer status with the following meaning of bits (see ACPI 6.2,
75 Reads also cause the AC alarm timer status to be reset.
77 Another way to reset the status of the AC alarm timer is to
80 If the status return value indicates that the timer has expired,
82 (and from S4/S5 too if supported) until its status is explicitly
112 (RW,optional) The DC alarm status.
|
| D | sysfs-class-mei | 21 Description: Display fw status registers content
23 The ME FW writes its status information into fw status
88 Description: Display trc status register content
91 status information into trc status register
|
| D | debugfs-driver-qat | 20 health status. High frequency Heartbeat monitoring wastes CPU cycles
39 status query results negative.
49 every status query.
51 What: /sys/kernel/debug/qat_<device>_<BDF>/heartbeat/status
55 Description: (RO) Read returns the device health status.
61 to poll the status periodically.
96 `heartbeat/status` attribute might report -1, i.e. device
|
| /Documentation/admin-guide/RAS/ |
| D | error-decoding.rst | 16 $ rasdaemon -p --status <STATUS> --ipid <IPID> --smca
21 …$ rasdaemon -p --status <STATUS> --ipid <IPID> --smca --family <CPU Family> --model <CPU Model> --…
|
| /Documentation/sound/designs/ |
| D | jack-injection.rst | 30 ``status``, after we finish our test, we need to disable the jack
48 |-- |-- |-- status
56 |-- |-- status
64 |-- |-- status
72 |-- |-- status
79 |-- status
100 status
101 read-only, get jack_kctl's current status
107 sound/card1/Headphone_Jack# cat status
114 sound/card1/Headphone_Jack# cat status
|
| /Documentation/devicetree/bindings/pci/ |
| D | ralink,rt3883-pci.txt | 23 - status: indicates the operational status of the device.
96 - status: indicates the operational status of the sub-node.
110 status = "disabled";
158 status = "disabled";
165 status = "disabled";
172 status = "disabled";
180 status = "okay";
184 status = "okay";
|
| D | nvidia,tegra20-pcie.txt | 197 status = "disabled";
203 status = "disabled";
217 status = "disabled";
231 status = "okay";
238 status = "okay";
304 status = "disabled";
310 status = "disabled";
323 status = "disabled";
336 status = "disabled";
349 status = "okay";
[all …]
|
| /Documentation/sound/soc/ |
| D | jack.rst | 15 automatically based on the detected jack status (eg, turning off the
27 headphone when the headphone jack status changes.
41 These represent a DAPM pin to update depending on some of the status
44 and associated with the jack using snd_soc_jack_add_pins(). The status
45 of the endpoint may configured to be the opposite of the jack status if
58 Often this is done based on the status of a GPIO - a handler for this is
72 mechanisms to update that jack based on their current status.
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | mscc,ocelot.yaml | 114 managed = "in-band-status";
121 managed = "in-band-status";
128 managed = "in-band-status";
135 managed = "in-band-status";
183 managed = "in-band-status";
190 managed = "in-band-status";
197 managed = "in-band-status";
204 managed = "in-band-status";
211 managed = "in-band-status";
218 managed = "in-band-status";
[all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | snps-dw-apb-uart.yaml | 108 description: Override the DCD modem status signal. This signal will
110 status register. Define this if your serial port does not use this
115 description: Override the DTS modem status signal. This signal will
117 status register. Define this if your serial port does not use this
122 description: Override the CTS modem status signal. This signal will
124 status register. Define this if your serial port does not use this
129 description: Override the RI modem status signal. This signal will always
130 be reported as inactive instead of being obtained from the modem status
|
| /Documentation/usb/ |
| D | gadget_printer.rst | 26 printer gadget driver using a device file. The printer returns a printer status
27 byte when the USB HOST sends a device request to get the printer status. The
28 user space firmware can read or write this status byte using a device file
111 To get the current printer status for the gadget driver:::
115 Printer status is:
131 To set paper status to paper out::
136 To set paper status to paper loaded::
141 To set error status to printer OK::
146 To set error status to ERROR::
186 fputs("-get_status Get the current printer status.\n", stderr);
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | fsl-qdma.yaml | 26 - description: Status regs
60 status-sizes:
62 description: status queue size of per virtual block
85 - status-sizes
120 <0x8389000 0x1000>, /* Status regs */
130 status-sizes = <64>;
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | dtx.rst | 113 As this changes the latch state, a *latch-status* event
155 Error Codes and Status Values
158 Error and status codes are divided into different categories, which can be
159 used to determine if the status code is an error, and, if it is, the
162 .. flat-table:: Overview of Status/Error Categories.
170 * - ``STATUS``
172 - Non-error status codes.
187 can be used to determine the category of any status value. The
188 ``SDTX_SUCCESS()`` macro can be used to check if the status value is a
191 Unknown status or error codes sent by the EC are assigned to the ``UNKNOWN``
[all …]
|
12345678910>>...32