Home
last modified time | relevance | path

Searched full:represent (Results 1 – 25 of 237) sorted by relevance

12345678910

/Documentation/devicetree/bindings/spi/
Dnuvoton,npcm-fiu.txt29 fiu0 represent fiu 0 controller
30 fiu1 represent fiu 3 controller
31 fiu2 represent fiu x controller
/Documentation/devicetree/bindings/input/
Dinput-reset.txt3 A simple binding to represent a set of keys as described in
33 Would represent KEY_2, KEY_3 and KEY_9.
/Documentation/sound/designs/
Dtracepoints.rst50 :c:type:`struct snd_mask` and represent mask values. As of PCM protocol
58 :c:type:`struct snd_interval` and represent values with a range. As of
155 The first three fields are common. They represent name of ALSA PCM character
161 The rest of field represent state of the parameter before/after changing. These
163 type, the fields represent hexadecimal dump of content of the parameter. For
164 parameters of interval type, the fields represent values of each member of
/Documentation/devicetree/bindings/bus/
Dnvidia,tegra210-aconnect.txt15 - #address-cells: The number of cells used to represent physical base addresses
17 - #size-cells: The number of cells used to represent the size of an address
/Documentation/devicetree/bindings/reset/
Dreset.txt3 This binding is intended to represent the hardware reset signals present
11 ordinate module is reset). This binding exists to represent the provider and
22 at once. In this case, it would be unwise to represent this reset signal in
/Documentation/devicetree/bindings/
Dchosen.txt4 The chosen node does not represent a real device, but serves as a place
6 arguments. Data in the chosen node does not represent the hardware.
102 While this property does not represent a real hardware, the address
120 While this property does not represent a real hardware, the address
/Documentation/devicetree/bindings/mfd/
Dmfd.txt32 - #address-cells: Specifies the number of cells used to represent physical base
35 - #size-cells: Specifies the number of cells used to represent the size of an
/Documentation/devicetree/bindings/input/touchscreen/
Dti-tsc-adc.txt25 8 bit number where in the 1st four bits represent the
26 analog lines and the next 4 bits represent positive/
28 represent the input lines and terminals resoectively
/Documentation/devicetree/bindings/clock/
Dst,nomadik.txt23 PLL nodes: these nodes represent the two PLLs on the system,
34 HCLK nodes: these represent the clock gates on individual
/Documentation/devicetree/bindings/powerpc/nintendo/
Dwii.txt102 Represent the USB 1.x Open Host Controller Interfaces.
122 Represent the Secure Digital Host Controller Interfaces.
132 Represent the Inter-Processor Communication interface. This interface
/Documentation/devicetree/bindings/usb/
Damlogic,dwc3.txt13 A child node must exist to represent the core DWC3 IP block. The name of
81 A child node must exist to represent the core DWC3 IP block. The name of
84 A child node must exist to represent the core DWC2 IP block. The name of
Ddwc3-cavium.txt7 A child node must exist to represent the core DWC3 IP block. The name of
/Documentation/powerpc/
Dvcpudispatch_stats.txt25 The next 4 numbers represent vcpu dispatch dispersions:
34 The final 3 numbers represent statistics in relation to the home node of
/Documentation/devicetree/bindings/hwmon/
Dnpcm750-pwm-fan.txt33 integer value in the range 0 through 7, that represent
37 integer value in the range 0 through 15, that represent
/Documentation/devicetree/bindings/mmc/
Dbrcm,bcm2835-sdhost.txt4 by mmc.txt and the properties that represent the BCM2835 controller.
/Documentation/devicetree/bindings/nvmem/
Dqfprom.txt3 This binding is intended to represent QFPROM which is found in most QCOM SOCs.
Dmtk-efuse.txt3 This binding is intended to represent MTK-EFUSE which is found in most Mediatek SOCs.
/Documentation/devicetree/bindings/display/rockchip/
Ddw_mipi_dsi_rockchip.txt9 - reg: Represent the physical address range of the controller.
10 - interrupts: Represent the controller's interrupt to the CPU(s).
/Documentation/devicetree/bindings/pinctrl/
Datmel,at91-pinctrl.txt28 Each column will represent the possible peripheral of the pinctrl
29 Each line will represent a pio bank
109 1. We have pin function node defined under at91 controller node to represent
Dfsl,imx-pinctrl.txt46 1. We have pin function node defined under iomux controller node to represent
50 The function node's name should represent well about what function
/Documentation/devicetree/bindings/fsi/
Dfsi.txt16 represent the FSI slaves and their slave engines. As a basic outline:
80 That address space has a maximum of 23 bits, so we use one cell to represent
95 use a single cell for address and size. Engine nodes represent the endpoint
/Documentation/devicetree/bindings/hwlock/
Dsirf,hwspinlock.txt10 - #hwlock-cells : hwlock users only use the hwlock id to represent a specific
Dqcom-hwspinlock.txt24 Definition: must be 1, the specified cell represent the lock id
Dst,stm32-hwspinlock.txt7 - #hwlock-cells : hwlock users only use the hwlock id to represent a specific
Dsprd-hwspinlock.txt7 - #hwlock-cells : hwlock users only use the hwlock id to represent a specific

12345678910