Searched full:listed (Results 1 – 25 of 1058) sorted by relevance
12345678910>>...43
| /Linux-v6.6/Documentation/riscv/ |
| D | uabi.rst | 26 ordered first by category, in canonical order, as listed above, then
29 #. Standard supervisor-level extensions (starting with 'S') will be listed
31 extensions are listed, they will be ordered alphabetically.
33 #. Standard machine-level extensions (starting with 'Zxm') will be listed
35 extensions are listed, they will be ordered alphabetically.
37 #. Non-standard extensions (starting with 'X') will be listed after all standard
38 extensions. If multiple non-standard extensions are listed, they will be
|
| /Linux-v6.6/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-v6.6/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-v6.6/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-v6.6/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 | samsung,pinctrl-pins-cfg.yaml | 39 The pin function selection that should be applied on the pins listed in the
41 of this property that should be applied to each of the pins listed in the
44 no specific function selection is desired for the pins listed in the child
|
| D | lantiq,pinctrl-xway.txt | 26 Each subnode only affects those parameters that are explicitly listed. In
38 Valid values for these names are listed below.
40 group. Valid values for function names are listed below.
108 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 | nvidia,tegra-pinmux-common.yaml | 28 Each subnode only affects those parameters that are explicitly listed. In
48 or group. Valid values for these names are listed below.
53 pin or group. Valid values for function names are listed below. See the
|
| /Linux-v6.6/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.
|
| /Linux-v6.6/include/linux/ |
| D | xattr.h | 51 * xattr_handler_can_list - check whether xattr can be listed
55 * Determine whether the xattr associated with @dentry can be listed given
58 * Return: true if xattr can be listed, false if not.
|
| D | coda.h | 12 Additional copyrights listed below
17 technical and financial contributors to Coda are listed in the file
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-hv_gpci | 9 perf_event_attr.config. All supported attributes are listed
46 0 or 1. Indicates whether we have access to "GA" events (listed
53 0 or 1. Indicates whether we have access to "EXPANDED" events (listed
60 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
|
| D | sysfs-driver-hid-logitech-lg4ff | 14 mode is listed as follows:
22 of the wheel not all listed modes might always be selectable.
|
| /Linux-v6.6/Documentation/userspace-api/media/rc/ |
| D | rc-sysfs-nodes.rst | 97 Note that protocol variants are listed, so ``nec``, ``sony``, ``rc-5``, ``rc-6``
98 have their different bit length encodings listed if available.
100 Note that all protocol variants are listed.
|
| /Linux-v6.6/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-v6.6/Documentation/devicetree/bindings/rtc/ |
| D | renesas,sh-rtc.yaml | 32 # The functional clock source for the RTC controller must be listed
34 # are to be listed.
|
| /Linux-v6.6/Documentation/kbuild/ |
| D | makefiles.rst | 166 compile the objects listed in $(isdn-y) and then run
194 Objects listed with obj-* are used for modules, or
198 All objects listed with lib-y are combined in a single
200 Objects that are listed in obj-y and additionally listed in
203 For consistency, objects listed in lib-m will be included in lib.a.
216 shall be listed in libs-y.
352 The two flags listed above are similar to ccflags-y and asflags-y.
508 Any target that utilizes if_changed must be listed in $(targets),
512 If the target is already listed in the recognized syntax such as
635 one of the listed prefixes. The first prefix where there exist a
[all …]
|
| /Linux-v6.6/crypto/ |
| D | crypto_engine.c | 233 * @req: the request need to be listed into the engine queue
263 * @req: the request need to be listed into the engine queue
275 * @req: the request need to be listed into the engine queue
288 * @req: the request need to be listed into the engine queue
301 * @req: the request need to be listed into the engine queue
314 * @req: the request need to be listed into the engine queue
327 * @req: the request need to be listed into the engine queue
|
| /Linux-v6.6/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,pru-consumer.yaml | 39 correspond to the PRU cores listed in the 'ti,prus' property
50 should correspond to the PRU cores listed in the 'ti,prus' property. The
|
| /Linux-v6.6/Documentation/devicetree/bindings/pci/ |
| 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-v6.6/Documentation/devicetree/bindings/mux/ |
| D | mux-consumer.yaml | 25 strings to label each of the mux controllers listed in the "mux-controls"
31 each of the multiplixer states listed in the "mux-states" property.
|
| /Linux-v6.6/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().
|
| /Linux-v6.6/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
|
12345678910>>...43
