Searched full:represented (Results 1 – 25 of 774) sorted by relevance
12345678910>>...31
| /Linux-v5.15/Documentation/ABI/testing/ |
| 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-driver-input-exc3000 | 8 Valid values: Represented as string
17 Valid values: Represented as string
26 Valid values: Represented as string
|
| 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
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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
98 The various Data RAMs within a single PRU-ICSS unit are represented as a
129 PRU-ICSS configuration space. CFG sub-module represented as a SysCon.
245 MII-RT sub-module represented as a SysCon.
264 represented as a SysCon.
282 that is common to all the PRU cores. This should be represented as an
303 PRU Node. Each PRUSS has dual PRU cores, each represented as a RemoteProc
|
| /Linux-v5.15/lib/ |
| D | parser.c | 126 * Return: On success, sets @result to the integer represented by the
161 * Return: On success, sets @result to the integer represented by the
188 * Return: On success, sets @result to the integer represented by the string
204 * Return: On success, sets @result to the integer represented by the string
229 * Return: On success, sets @result to the integer represented by the string
245 * Return: On success, sets @result to the integer represented by the string
261 * Return: On success, sets @result to the integer represented by the string
|
| /Linux-v5.15/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::
|
| /Linux-v5.15/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:
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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
|
| /Linux-v5.15/Documentation/driver-api/media/ |
| D | mc-core.rst | 39 A media device is represented by a struct media_device
52 Entities are represented by a struct media_entity
69 Interfaces are represented by a
72 defined: a device node. Such interfaces are represented by a
82 Pads are represented by a struct media_pad instance,
107 Links are represented by a struct media_link instance,
|
| /Linux-v5.15/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".
|
| /Linux-v5.15/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
|
| /Linux-v5.15/Documentation/gpu/ |
| D | drm-kms.rst | 58 Framebuffers (represented by :c:type:`struct drm_framebuffer <drm_framebuffer>`,
59 see `Frame Buffer Abstraction`_) feed into planes. Planes are represented by
62 (represented by :c:type:`struct drm_crtc <drm_crtc>`, see `CRTC Abstraction`_)
66 For the output routing the first step is encoders (represented by
78 The final, and real, endpoint in the display chain is the connector (represented
137 more :ref:`drm_bridges` (represented by :c:type:`struct drm_bridge
145 The second object is for panels, represented by :c:type:`struct drm_panel
184 represented by :c:type:`struct drm_property <drm_property>`, which only specify
|
| /Linux-v5.15/drivers/net/ipa/ |
| D | ipa_gsi.h | 39 * @byte_count: Number of bytes to transfer represented by transactions
52 * @byte_count: Number of bytes transferred represented by transactions
|
| /Linux-v5.15/Documentation/networking/ |
| D | nf_flowtable.rst | 37 The flowtable datapath is represented in Fig.1, which describes the classic IP
138 (represented as eth1 and eth2 in the example figure below) and the gateway
139 device (represented as eth0) in your switch/router.
163 represented by the real netdevice) to your flowtable definition.
|
| /Linux-v5.15/Documentation/devicetree/bindings/input/ |
| D | samsung-keypad.txt | 28 - Keys represented as child nodes: Each key connected to the keypad
29 controller is represented as a child node to the keypad controller
|
| /Linux-v5.15/Documentation/power/powercap/ |
| D | powercap.rst | 22 well as controls represented in the form of power constraints. If the parts of
23 the system represented by different power zones are hierarchical (that is, one
162 part of the system represented by that zone to be identified.
|
| /Linux-v5.15/Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 70 performance scaling algorithms for P-state selection can be represented in a
79 interface it comes from and may not be easily represented in an abstract,
93 Sets of CPUs sharing hardware P-state control interfaces are represented by
139 to, represented by its policy object) and, if the policy object it has been
208 that may be different from the one represented by ``X``) for all of the CPUs
225 performance scaling interface represented by the ``policyX`` policy
476 is greater by 1000, this means that the time represented by
481 represented by it to be 750 times as high as the transition latency::
544 If the workload sensitivity is less than the threshold represented by
|
| D | sleep-states.rst | 165 to start a transition of the system into the sleep state represented by
189 suspend variant represented by it to be associated with the "mem" string
236 represented by it to be selected.
239 that the operation represented by it will be carried out after creating
|
| /Linux-v5.15/Documentation/devicetree/bindings/iio/proximity/ |
| D | semtech,sx9310.yaml | 50 List of which sensors are combined and represented by CS3.
80 sensor is represented by the value 3. This is used for initial
|
| /Linux-v5.15/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
|
| /Linux-v5.15/Documentation/driver-api/thermal/ |
| D | cpu-cooling-api.rst | 83 A high level dynamic power consumption model may then be represented as::
95 represented as a constant coefficient. This is a simplification
|
| /Linux-v5.15/include/linux/ |
| D | crc8.h | 47 * represented as shown below.
65 * represented as shown below.
|
12345678910>>...31
