Searched full:represented (Results 1 – 25 of 339) sorted by relevance
12345678910>>...14
| /Documentation/ABI/testing/ |
| D | sysfs-driver-input-exc3000 | 8 Valid values: Represented as string
17 Valid values: Represented as string
26 Valid values: Represented as string
|
| D | sysfs-secvar | 32 Description: Each secure variable is represented as a directory named as
77 represented in ASCII decimal format.
89 Description: Total size of the PLPKS in bytes, represented in ASCII decimal
97 Description: Current space consumed by the key store, in bytes, represented
106 represented as an 8 byte hexadecimal ASCII string. Consult the
115 supports for signed update of objects, represented as a 16 byte
|
| D | sysfs-class-power | 10 Valid values: Represented as string
19 Valid values: Represented as string
28 Valid values: Represented as string
60 Valid values: Represented in microamps. Negative values are
77 Valid values: Represented in microamps
100 Valid values: Represented in microamps. Negative values are
120 Valid values: Represented in 1/10 Degrees Celsius
144 Valid values: Represented in 1/10 Degrees Celsius
169 Valid values: Represented in 1/10 Degrees Celsius
186 Valid values: Represented in 1/10 Degrees Celsius
[all …]
|
| D | sysfs-devices-lpss_ltr | 28 represented as an 8-digit hexadecimal number.
39 current value of the device's SW_LTR register (raw) represented
|
| D | sysfs-class-power-mp2629 | 9 Valid values: Represented in milli-ohms. Valid range is [0, 140].
|
| D | sysfs-bus-iio-dac-dpot-dac | 6 The range of available values represented as the minimum value,
|
| D | sysfs-bus-iio-potentiometer-mcp4531 | 6 The range of available values represented as the minimum value,
|
| D | sysfs-bus-iio-distance-srf08 | 11 Showing the range of available values is represented as the
|
| /Documentation/devicetree/bindings/media/xilinx/ |
| D | video.txt | 8 Each video IP core is represented by an AMBA bus child node in the device
10 cores are represented as defined in ../video-interfaces.txt.
12 The whole pipeline is represented by an AMBA bus child node in the device
|
| /Documentation/admin-guide/mm/ |
| D | cma_debugfs.rst | 8 Each CMA area represents a directory under <debugfs>/cma/, represented by
17 - [RO] order_per_bit: Order of pages represented by one bit.
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-netxbig.txt | 9 - timers: Timer array. Each timer entry is represented by three integers:
12 Each LED is represented as a sub-node of the netxbig-leds device.
16 - mode-val: Mode to value mapping. Each entry is represented by two integers:
|
| D | trigger-source.yaml | 14 Each trigger source provider should be represented by a device tree node. It
|
| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 17 layout (i.e. parent device objects in the namespace are represented by parent
28 information from the device objects represented by them and populating them with
37 component represented by the given device node which can be determined on the
39 called ACPI scan handlers represented by the following structure::
|
| /Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 5 standalone chips are most likely better represented as GPIOs, although there
14 A reset signal is represented by the phandle of the provider, plus a reset
24 may be reset. Instead, reset signals should be represented in the DT node
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | ti,pruss.yaml | 42 Various sub-modules within a PRU-ICSS subsystem are represented as individual
50 Each PRU-ICSS instance is represented as its own node with the individual PRU
51 processor cores, the memories node, an INTC node and an MDIO node represented
99 The various Data RAMs within a single PRU-ICSS unit are represented as a
130 PRU-ICSS configuration space. CFG sub-module represented as a SysCon.
247 MII-RT sub-module represented as a SysCon.
266 represented as a SysCon.
283 PA-STATS sub-module represented as a SysCon. PA_STATS is a set of
304 that is common to all the PRU cores. This should be represented as an
319 PRU Node. Each PRUSS has dual PRU cores, each represented as a RemoteProc
|
| /Documentation/power/ |
| D | opp.rst | 61 OPP layer expects each domain to be represented by a unique device pointer. SoC
102 Add a new OPP for a specific domain represented by the device pointer.
252 framework to retrieve the information represented inside the OPP layer.
255 Retrieve the voltage represented by the opp pointer.
257 framework requires to set the voltage represented by the OPP using
273 Retrieve the freq represented by the opp pointer.
325 domain is represented by a device pointer. The relationship to OPP can be
326 represented as follows::
362 Overall, in a simplistic view, the data structure operations is represented as
|
| /Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 9 represented by any node in the device tree and can provide one or more PM
47 located inside a PM domain with index 0 of a power controller represented by a
51 is represented by a node with the label "power".
|
| /Documentation/driver-api/pm/ |
| D | cpuidle.rst | 52 The governor itself is represented by a struct cpuidle_governor object
81 (logical) CPU represented by the struct cpuidle_device object pointed
99 Called to make the governor stop handling the (logical) CPU represented
114 CPU represented by the struct cpuidle_device object pointed to by the
117 The list of idle states to take into consideration is represented by the
175 idle state represented by the struct cpuidle_state object holding it, this
255 be invoked for the logical CPU represented by it, so it must take place after
|
| /Documentation/admin-guide/media/ |
| D | qcom_camss.rst | 114 - 2 / 3 CSIPHY sub-devices - each CSIPHY is represented by a single sub-device;
115 - 2 / 4 CSID sub-devices - each CSID is represented by a single sub-device;
116 - 2 / 4 ISPIF sub-devices - ISPIF is represented by a number of sub-devices
118 - 4 / 8 VFE sub-devices - VFE is represented by a number of sub-devices equal to
|
| /Documentation/driver-api/media/ |
| D | mc-core.rst | 39 A media device is represented by a struct media_device
59 Entities are represented by a struct media_entity
76 Interfaces are represented by a
79 defined: a device node. Such interfaces are represented by a
89 Pads are represented by a struct media_pad instance,
114 Links are represented by a struct media_link instance,
|
| /Documentation/devicetree/bindings/pwm/ |
| D | iqs620a-pwm.yaml | 14 output represented by a "pwm" child node from the parent MFD driver. See
|
| /Documentation/devicetree/bindings/regulator/ |
| D | max77650-regulator.yaml | 16 The regulator controller is represented as a sub-node of the PMIC node
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | firmware.txt | 14 firmware binary. It is a 64-bit number represented
|
| /Documentation/devicetree/bindings/iio/proximity/ |
| D | semtech,sx9310.yaml | 53 List of which sensors are combined and represented by CS3.
83 sensor is represented by the value 3. This is used for initial
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | srio.txt | 65 represented in the property for both transactions.
69 transactions then a pair of LIODNs are represented in the
|
12345678910>>...14