Searched full:represented (Results 1 – 25 of 669) sorted by relevance
12345678910>>...27
| /Linux-v5.4/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
96 Valid values: Represented in microamps
105 Valid values: Represented in microamps
115 Valid values: Represented in microamps
125 Valid values: Represented in microamps
134 Valid values: Represented in microamps
180 Valid values: Represented in microamps
202 Valid values: Represented in microamps
[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
|
| /Linux-v5.4/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.4/Documentation/power/ |
| D | opp.rst | 61 OPP layer expects each domain to be represented by a unique device pointer. SoC
100 Add a new OPP for a specific domain represented by the device pointer.
250 framework to retrieve the information represented inside the OPP layer.
253 Retrieve the voltage represented by the opp pointer.
255 framework requires to set the voltage represented by the OPP using
271 Retrieve the freq represented by the opp pointer.
323 domain is represented by a device pointer. The relationship to OPP can be
324 represented as follows::
360 Overall, in a simplistic view, the data structure operations is represented as
|
| /Linux-v5.4/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.4/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 | leds-max77650.txt | 6 The LED controller is represented as a sub-node of the PMIC node on
17 Each LED is represented as a sub-node of the LED-controller node. Up to
|
| D | common.txt | 10 have to be tightly coupled with the LED device binding. They are represented
91 should be represented by a node in the device tree and be
108 Each trigger source should be represented by a device tree node. It may be e.g.
|
| /Linux-v5.4/lib/ |
| D | parser.c | 123 * as a number in that base. On success, sets @result to the integer represented
156 * as a number in that base. On success, sets @result to the integer represented
182 * success, sets @result to the integer represented by the string and returns 0.
198 * integer. On success, sets @result to the integer represented by the
214 * success, sets @result to the integer represented by the string and returns
229 * On success, sets @result to the integer represented by the string and
|
| D | ubsan.c | 183 pr_err("%s %c %s cannot be represented in type %s\n", in handle_overflow()
227 pr_err("negation of %s cannot be represented in type %s:\n", in __ubsan_handle_negate_overflow()
249 pr_err("division of %s by -1 cannot be represented in type %s\n", in __ubsan_handle_divrem_overflow()
400 " represented in type %s\n", in __ubsan_handle_shift_out_of_bounds()
|
| /Linux-v5.4/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.4/Documentation/driver-api/pm/ |
| D | cpuidle.rst | 57 The governor itself is represented by a |struct cpuidle_governor| object
87 (logical) CPU represented by the |struct cpuidle_device| object pointed
105 Called to make the governor stop handling the (logical) CPU represented
120 CPU represented by the |struct cpuidle_device| object pointed to by the
123 The list of idle states to take into consideration is represented by the
181 idle state represented by the |struct cpuidle_state| object holding it, this
261 be invoked for the logical CPU represented by it, so it must take place after
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | mc-core.rst | 39 A media device is represented by a struct :c:type:`media_device`
52 Entities are represented by a struct :c:type:`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 :c:type:`media_pad` instance,
107 Links are represented by a struct :c:type:`media_link` instance,
|
| /Linux-v5.4/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
182 represented by :c:type:`struct drm_property <drm_property>`, which only specify
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| 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.4/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.4/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.4/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 162 to start a transition of the system into the sleep state represented by
186 suspend variant represented by it to be associated with the "mem" string
224 represented by it to be selected.
227 that the operation represented by it will be carried out after creating
|
| D | cpufreq.rst | 71 performance scaling algorithms for P-state selection can be represented in a
80 interface it comes from and may not be easily represented in an abstract,
94 Sets of CPUs sharing hardware P-state control interfaces are represented by
140 to, represented by its policy object) and, if the policy object it has been
209 that may be different from the one represented by ``X``) for all of the CPUs
226 performance scaling interface represented by the ``policyX`` policy
477 is greater by 1000, this means that the time represented by
482 represented by it to be 750 times as high as the transition latency::
545 If the workload sensitivity is less than the threshold represented by
|
| /Linux-v5.4/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 5 controllers. Each pin controller must be represented as a node in device tree,
9 designated client devices. Again, each client device must be represented as a
215 settings represented as a single integer or an array of integers.
232 Many data items that are represented in a pin configuration node are common
|
| /Linux-v5.4/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.4/Documentation/filesystems/ |
| D | omfs.txt | 63 Files and directories are both represented by omfs_inode:
81 until a match is found on i_name. Empty buckets are represented by block
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 9 represented by any node in the device tree and can provide one or more PM
140 located inside a PM domain with index 0 of a power controller represented by a
144 is represented by a node with the label "power".
|
| /Linux-v5.4/include/linux/ |
| D | crc8.h | 47 * represented as shown below.
65 * represented as shown below.
|
| /Linux-v5.4/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
|
12345678910>>...27
