Searched full:listed (Results 1 – 25 of 968) sorted by relevance
12345678910>>...39
| /Linux-v5.4/Documentation/devicetree/bindings/display/ |
| D | st,stih4xx.txt | 18 - clock-names: names of the clocks listed in clocks property in the same
36 - clock-names: names of the clocks listed in clocks property in the same
40 - reset-names: names of the resets listed in resets property in the same
49 - reg-names: names of the mapped memory regions listed in regs property in
53 - reset-names: names of the resets listed in resets property in the same
61 - reg-names: names of the mapped memory regions listed in regs property in
64 - interrupt-names: names of the interrupts listed in interrupts property in
68 - clock-names: names of the clocks listed in clocks property in the same
77 - reg-names: names of the mapped memory regions listed in regs property in
82 - clock-names: names of the clocks listed in clocks property in the same
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 6 "fsl,mpc8349-pmc" should be listed for any chip whose PMC is
7 compatible. "fsl,mpc8313-pmc" should also be listed for any chip
10 "fsl,mpc8548-pmc" should be listed for any chip whose PMC is
11 compatible. "fsl,mpc8536-pmc" should also be listed for any chip
14 "fsl,mpc8641d-pmc" should be listed for any chip whose PMC is
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | st,sti-asoc-card.txt | 20 - clock-names: name of the clocks listed in clocks property in the same order
22 - reg: CPU DAI IP Base address and size entries, listed in same
25 - reg-names: names of the mapped memory regions listed in regs property in
28 - interrupts: CPU_DAI interrupt line, listed in the same order than the
31 - dma: CPU_DAI DMA controller phandle and DMA request line, listed in the same
39 - clocks: CPU_DAI IP clock source, listed in the same order than the
|
| /Linux-v5.4/Documentation/devicetree/bindings/pinctrl/ |
| D | lantiq,pinctrl-falcon.txt | 21 Each subnode only affects those parameters that are explicitly listed. In
33 Valid values for these names are listed below.
35 group. Valid values for function names are listed below.
51 Valid values for these names are listed below.
|
| D | fsl,mxs-pinctrl.txt | 18 a group of pins, and only affects those parameters that are explicitly listed.
54 Valid values for these integers are listed below.
122 to be listed in the config nodes.
|
| D | lantiq,pinctrl-xway.txt | 30 Each subnode only affects those parameters that are explicitly listed. In
42 Valid values for these names are listed below.
44 group. Valid values for function names are listed below.
135 Valid values for these names are listed below.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-hv_gpci | 14 0 or 1. Indicates whether we have access to "GA" events (listed
21 0 or 1. Indicates whether we have access to "EXPANDED" events (listed
28 0 or 1. Indicates whether we have access to "LAB" events (listed
|
| D | sysfs-driver-typec-displayport | 9 All supported configurations are listed as space separated list
32 listed as space separated list with the active one wrapped in
|
| /Linux-v5.4/crypto/ |
| D | crypto_engine.c | 179 * @req: the request need to be listed into the engine queue
208 * @req: the request need to be listed into the engine queue
220 * @req: the request need to be listed into the engine queue
234 * @req: the request need to be listed into the engine queue
247 * @req: the request need to be listed into the engine queue
260 * @req: the request need to be listed into the engine queue
273 * @req: the request need to be listed into the engine queue
|
| /Linux-v5.4/Documentation/devicetree/bindings/lpddr2/ |
| D | lpddr2.txt | 7 "ti,jedec-lpddr2-s2" should be listed if the memory part is LPDDR2-S2 type
9 "ti,jedec-lpddr2-s4" should be listed if the memory part is LPDDR2-S4 type
11 "ti,jedec-lpddr2-nvm" should be listed if the memory part is LPDDR2-NVM type
|
| /Linux-v5.4/Documentation/devicetree/bindings/iio/accel/ |
| D | bma180.txt | 15 For the bma250 the first interrupt listed must be the one
17 listed must be the one connected to the INT2 pin.
|
| /Linux-v5.4/Documentation/devicetree/bindings/media/ |
| D | st,st-hva.txt | 7 - reg-names: names of the registers listed in registers property in the same
13 - clock-names: names of the clocks listed in clocks property in the same order.
|
| D | qcom,camss.txt | 14 Definition: Register ranges as listed in the reg-names property.
36 Definition: Interrupts as listed in the interrupt-names property.
60 Definition: A list of phandle and clock specifier pairs as listed
|
| /Linux-v5.4/Documentation/devicetree/bindings/rtc/ |
| D | rtc-sh.txt | 10 - clocks: The functional clock source for the RTC controller must be listed
12 listed.
|
| /Linux-v5.4/Documentation/devicetree/bindings/devfreq/event/ |
| D | exynos-ppmu.txt | 21 Example1 : PPMUv1 nodes in exynos3250.dtsi are listed below.
57 Example2 : Events of each PPMU node in exynos3250-rinato.dts are listed below.
111 Example3 : PPMUv2 nodes in exynos5433.dtsi are listed below.
|
| /Linux-v5.4/tools/usb/usbip/doc/ |
| D | usbip.8 | 9 On a USB/IP server, devices can be listed, bound, and unbound using
11 can be listed, attached and detached.
|
| /Linux-v5.4/include/linux/ |
| D | coda.h | 12 Additional copyrights listed below
17 technical and financial contributors to Coda are listed in the file
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/ |
| D | qca,ar71xx.txt | 18 - clock-names: the names of the clock listed in the clocks property. These are
21 - reset-names: Should contain the names of reset signal listed in the resets
|
| /Linux-v5.4/Documentation/media/uapi/rc/ |
| D | rc-sysfs-nodes.rst | 104 Note that protocol variants are listed, so ``nec``, ``sony``, ``rc-5``, ``rc-6``
105 have their different bit length encodings listed if available.
107 Note that all protocol variants are listed.
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | makefiles.rst | 217 compile the objects listed in $(isdn-y) and then run
251 Objects listed with obj-* are used for modules, or
255 All objects listed with lib-y are combined in a single
257 Objects that are listed in obj-y and additionally listed in
260 For consistency, objects listed in lib-m will be included in lib.a.
273 shall be listed in libs-y.
346 The two flags listed above are similar to ccflags-y and asflags-y.
544 one of the listed prefixes. The first prefix where there exist a
747 Kbuild knows targets listed in $(hostprogs-y), $(hostprogs-m), $(always),
797 Note 2: All directories listed in core-y, libs-y, drivers-y and net-y will
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/pci/ |
| D | qcom,pcie.txt | 18 Definition: Register ranges as listed in the reg-names property
77 Definition: List of phandle and clock specifier pairs as listed
132 Definition: List of phandle and reset specifier pairs as listed
221 Definition: List of phandle(s) as listed in phy-names property
|
| D | hisilicon-histb-pcie.txt | 21 - clocks: List of phandle and clock specifier pairs as listed in clock-names
28 - resets: List of phandle and reset specifier pairs as listed in reset-names
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ |
| D | pmu.yaml | 54 the SPIs listed in the interrupts property.
58 a PMU of this type signalling the PPI listed in the
|
| /Linux-v5.4/Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 29 subsystem, driver, or file, and is listed in the MAINTAINERS file in the
124 The address listed in the Code of Conduct goes to the Code of Conduct
126 are listed at https://kernel.org/code-of-conduct.html. Members can not
|
| /Linux-v5.4/Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 66 special files can be listed in a 'root-files' file. Both 'root-image'
67 and 'root-files' can be listed in CONFIG_INITRAMFS_SOURCE and a complete
135 some other init binary than listed at the end of init/main.c:init().
|
12345678910>>...39
