Searched full:represent (Results 1 – 25 of 853) sorted by relevance
12345678910>>...35
| /Linux-v5.10/Documentation/sound/designs/ |
| D | tracepoints.rst | 50 struct snd_mask and represent mask values. As of PCM protocol
58 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
|
| /Linux-v5.10/Documentation/devicetree/bindings/spi/ |
| D | nuvoton,npcm-fiu.txt | 29 fiu0 represent fiu 0 controller
30 fiu1 represent fiu 3 controller
31 fiu2 represent fiu x controller
|
| /Linux-v5.10/drivers/iio/adc/ |
| D | qcom-vadc-common.h | 62 * @x: Represent the ADC digitized code.
63 * @y: Represent the physical data which can be temperature, voltage,
82 * struct vadc_linear_graph - Represent ADC characteristics.
97 * struct vadc_prescale_ratio - Represent scaling ratio for ADC input.
|
| /Linux-v5.10/drivers/pinctrl/samsung/ |
| D | pinctrl-samsung.h | 46 * packed together into a 16-bits. The upper 8-bits represent the configuration
108 * struct samsung_pin_bank_data: represent a controller pin-bank (init data).
132 * struct samsung_pin_bank: represent a controller pin-bank.
200 * struct samsung_retention_data: represent a pin-bank retention control data.
217 * struct samsung_pin_ctrl: represent a pin controller.
306 * struct samsung_pin_group: represent group of pins of a pinmux function.
320 * struct samsung_pmx_func: represent a pin function.
|
| /Linux-v5.10/Documentation/devicetree/bindings/ |
| D | chosen.txt | 4 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
|
| /Linux-v5.10/Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 3 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
|
| /Linux-v5.10/Documentation/devicetree/bindings/input/ |
| D | input-reset.txt | 3 A simple binding to represent a set of keys as described in
33 Would represent KEY_2, KEY_3 and KEY_9.
|
| /Linux-v5.10/arch/mips/include/asm/mach-cavium-octeon/ |
| D | irq.h | 15 /* 1 - 8 represent the 8 MIPS standard interrupt sources */
51 /* 256 - 511 represent the MSI interrupts 0-255 */
|
| /Linux-v5.10/Documentation/devicetree/bindings/input/touchscreen/ |
| D | ti-tsc-adc.txt | 25 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
|
| /Linux-v5.10/Documentation/devicetree/bindings/bus/ |
| D | nvidia,tegra210-aconnect.txt | 15 - #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
|
| /Linux-v5.10/Documentation/devicetree/bindings/mfd/ |
| D | mfd.txt | 32 - #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
|
| /Linux-v5.10/arch/powerpc/include/uapi/asm/ |
| D | auxvec.h | 21 * AT_*CACHEBSIZE above represent the cache *block* size which is
28 * The set of entries below represent more extensive information
|
| /Linux-v5.10/Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 102 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
|
| /Linux-v5.10/drivers/pinctrl/ |
| D | pinctrl-equilibrium.h | 71 * struct eqbr_pmx_func: represent a pin function.
83 * struct eqbr_pin_bank: represent a pin bank.
99 * struct eqbr_gpio_ctrl: represent a gpio controller.
|
| /Linux-v5.10/Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 16 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
|
| /Linux-v5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pinctrl.txt | 28 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
|
| /Linux-v5.10/Documentation/devicetree/bindings/clock/ |
| D | st,nomadik.txt | 23 PLL nodes: these nodes represent the two PLLs on the system,
34 HCLK nodes: these represent the clock gates on individual
|
| /Linux-v5.10/include/linux/ |
| D | relay.h | 124 * create_buf_file - create file to represent a relay channel buffer
133 * represent the corresponding channel buffer. If the file is
138 * to represent the relay buffer.
157 * to allow the client to remove a file used to represent a
|
| /Linux-v5.10/include/xen/arm/ |
| D | interface.h | 34 /* Explicitly size integers that represent pfns in the interface with
37 * representing pfn's which the guest cannot represent in its own pfn
|
| /Linux-v5.10/Documentation/x86/ |
| D | cpuinfo.rst | 13 an X86_FEATURE_* defined. These flags represent hardware features as
70 d: Flags can represent purely software features.
72 These flags do not represent hardware features. Instead, they represent a
|
| /Linux-v5.10/Documentation/devicetree/bindings/hwmon/ |
| D | npcm750-pwm-fan.txt | 33 integer value in the range 0 through 7, that represent
37 integer value in the range 0 through 15, that represent
|
| /Linux-v5.10/Documentation/powerpc/ |
| D | vcpudispatch_stats.rst | 29 The next 4 numbers represent vcpu dispatch dispersions:
39 The final 3 numbers represent statistics in relation to the home node of
|
| /Linux-v5.10/Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 38 a local offset to the GPIO line and the second cell represent consumer flags,
90 The gpio-specifier's polarity flag should represent the physical level at the
94 the GPIO controller and the device, then the gpio-specifier will represent the
120 in the binding. The gpio-specifier should represent the polarity of the signal
242 It is useful to represent which GPIOs correspond to which pins on which pin
|
| /Linux-v5.10/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 26 Device nodes compatible with this binding represent hardware with some of the
55 one cell can be required to represent a single master ID.
63 definitions to represent their individual needs. Always refer to the specific
|
| /Linux-v5.10/Documentation/devicetree/bindings/display/ |
| D | mipi-dsi-bus.txt | 6 define the syntax used to represent a DSI bus in a device tree.
25 - #address-cells: The number of cells required to represent an address on the
78 The graph bindings should be used to represent the multiple DSI busses that are
|
12345678910>>...35
