Searched full:individual (Results 1 – 25 of 2321) sorted by relevance
12345678910>>...93
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-module | 16 This directory contains individual files that are each
17 individual parameters of the module that are able to be
18 changed at runtime. See the individual module
22 Note: The individual parameter names and values are not
25 individual driver documentation for details as to the
|
| /kernel/linux/linux-4.19/Documentation/ABI/stable/ |
| D | sysfs-module | 16 This directory contains individual files that are each
17 individual parameters of the module that are able to be
18 changed at runtime. See the individual module
22 Note: The individual parameter names and values are not
25 individual driver documentation for details as to the
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | tlb.rst | 23 entire TLB than doing 2^48/PAGE_SIZE individual flushes.
26 all of the individual flush will have ended up being wasted
30 more attractive an individual flush looks. Data and
41 You may be doing too many individual invalidations if you see the
43 profiles. If you believe that individual invalidations being
49 Lowering it to 0 will disable the use of the individual flushes.
53 Despite the fact that a single individual flush on x86 is
|
| /kernel/linux/linux-4.19/Documentation/x86/ |
| D | tlb.txt | 15 entire TLB than doing 2^48/PAGE_SIZE individual flushes.
18 all of the individual flush will have ended up being wasted
22 more attractive an individual flush looks. Data and
33 You may be doing too many individual invalidations if you see the
35 profiles. If you believe that individual invalidations being
41 Lowering it to 0 will disable the use of the individual flushes.
45 Despite the fact that a single individual flush on x86 is
|
| /kernel/linux/linux-4.19/sound/soc/tegra/ |
| D | Kconfig | 18 Tegra20 AC97 interface. You will also need to select the individual
26 You will also need to select the individual machine drivers to
35 Tegra20 I2S interface. You will also need to select the individual
44 You will also need to select the individual machine drivers to support
52 You will also need to select the individual machine drivers to
61 Tegra30 I2S interface. You will also need to select the individual
|
| /kernel/linux/linux-5.10/sound/soc/tegra/ |
| D | Kconfig | 19 Tegra20 AC97 interface. You will also need to select the individual
27 You will also need to select the individual machine drivers to
36 Tegra20 I2S interface. You will also need to select the individual
45 You will also need to select the individual machine drivers to support
53 You will also need to select the individual machine drivers to
62 Tegra30 I2S interface. You will also need to select the individual
|
| /kernel/linux/linux-4.19/drivers/pinctrl/bcm/ |
| D | Kconfig | 58 It provides the framework where pins from the individual GPIO can be
61 support individual pin muxing.
74 configuration, with the exception that certain individual pins
118 configuration, with certain individual pins can be overridden
|
| /kernel/linux/linux-5.10/drivers/pinctrl/bcm/ |
| D | Kconfig | 63 It provides the framework where pins from the individual GPIO can be
66 support individual pin muxing.
79 configuration, with the exception that certain individual pins
136 configuration, with certain individual pins can be overridden
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 29 individual board device tree files, and any requirements imposed by the
30 bindings for the individual client devices in use by that board, i.e. whether
109 globally for the pin controller or in child nodes for individual
132 entirely by the binding for the individual pin controller device. There
139 nodes, is again defined entirely by the binding for the individual pin
|
| D | pinmux-node.yaml | 14 for the individual pin controller device. The pin configuration nodes need not
18 the binding for the individual pin controller device.
99 Each individual pin controller driver bindings documentation shall specify
121 configuration of whole groups rather than individual pins (either
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 29 individual board device tree files, and any requirements imposed by the
30 bindings for the individual client devices in use by that board, i.e. whether
109 globally for the pin controller or in child nodes for individual
132 entirely by the binding for the individual pin controller device. There
139 nodes, is again defined entirely by the binding for the individual pin
226 Each individual pin controller driver bindings documentation shall specify
235 for all hardware or binding structures. Each individual binding document
246 individual pins (either this, "pins" or "pinmux" has
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/usb/ |
| D | usb251xb.txt | 29 - {ganged,individual}-sensing : select over-current sense type in self-powered
30 mode (boolean, default is individual)
31 - {ganged,individual}-port-switching : select port power switching mode
32 (boolean, default is individual)
|
| /kernel/linux/linux-5.10/drivers/scsi/isci/ |
| D | sas.h | 80 * For specific information on each of these individual fields please
99 * For specific information on each of these individual fields please
119 * For specific information on each of these individual fields please reference
137 * For specific information on each of these individual fields please reference
161 * For specific information on each of these individual fields please reference
|
| /kernel/linux/linux-4.19/drivers/scsi/isci/ |
| D | sas.h | 80 * For specific information on each of these individual fields please
99 * For specific information on each of these individual fields please
119 * For specific information on each of these individual fields please reference
137 * For specific information on each of these individual fields please reference
161 * For specific information on each of these individual fields please reference
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/ |
| D | usb251xb.txt | 30 - {ganged,individual}-sensing : select over-current sense type in self-powered
31 mode (boolean, default is individual)
32 - {ganged,individual}-port-switching : select port power switching mode
33 (boolean, default is individual)
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | scsi.rst | 29 The individual upper and lower level drivers can be loaded in any order
38 The lower level drivers are the ones that support the individual cards that
40 individual cards are often called Host Bus Adapters (HBAs). For example the
|
| /kernel/linux/linux-4.19/Documentation/scsi/ |
| D | scsi.txt | 25 The individual upper and lower level drivers can be loaded in any order
34 The lower level drivers are the ones that support the individual cards that
36 individual cards are often called Host Bus Adapters (HBAs). For example the
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class | 6 subdirectories describing individual classes of devices
7 in the kernel. The individual directories will consist
|
| D | sysfs-devices-system-xen_cpu | 5 A collection of global/individual Xen physical cpu attributes
7 Individual physical cpu attributes are contained in
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-class | 6 subdirectories describing individual classes of devices
7 in the kernel. The individual directories will consist
|
| D | sysfs-devices-system-xen_cpu | 5 A collection of global/individual Xen physical cpu attributes
7 Individual physical cpu attributes are contained in
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/marvell/ |
| D | marvell,berlin.txt | 58 individual registers dealing with pinmux, padmux, clock, reset, and secondary
59 CPU boot address. Unfortunately, the individual registers are spread among the
74 individual registers dealing with pinmux, padmux, and reset.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | syna.txt | 67 individual registers dealing with pinmux, padmux, clock, reset, and secondary
68 CPU boot address. Unfortunately, the individual registers are spread among the
83 individual registers dealing with pinmux, padmux, and reset.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,c64x+megamod-pic.txt | 38 interrupt sources, individual megamodule interrupts may be cascaded to
39 the core interrupt controller. When an individual interrupt is cascaded,
83 This is a minimal example where all individual interrupts go through a
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,c64x+megamod-pic.txt | 38 interrupt sources, individual megamodule interrupts may be cascaded to
39 the core interrupt controller. When an individual interrupt is cascaded,
83 This is a minimal example where all individual interrupts go through a
|
12345678910>>...93