Searched full:utilizes (Results 1 – 25 of 91) sorted by relevance
1234
| /linux-6.12.1/drivers/staging/fbtft/ |
| D | Kconfig | 117 Say Y if you have such a display that utilizes this controller.
169 Say Y if you have such a display that utilizes this controller.
|
| /linux-6.12.1/drivers/pps/generators/ |
| D | Kconfig | 13 utilizes STROBE pin of a parallel port to send PPS signals. It uses
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-class-fc | 10 entity utilizes a block device via the cgroup id.
|
| /linux-6.12.1/Documentation/hwmon/ |
| D | pm6764tr.rst | 25 The device utilizes digital technology to implement all control and power management
|
| /linux-6.12.1/arch/arm/ |
| D | Kconfig-nommu | 37 used instead of the auto-probing which utilizes the register.
|
| /linux-6.12.1/Documentation/devicetree/bindings/w1/ |
| D | w1-uart.yaml | 13 UART 1-wire bus. Utilizes the UART interface via the Serial Device Bus
|
| /linux-6.12.1/Documentation/arch/sh/ |
| D | register-banks.rst | 21 in mind when writing code that utilizes these banked registers, for obvious
|
| /linux-6.12.1/Documentation/devicetree/bindings/clock/ |
| D | cirrus,cs2000-cp.yaml | 14 utilizes a programmable phase lock loop.
|
| /linux-6.12.1/drivers/cpufreq/ |
| D | Kconfig.x86 | 44 This driver adds a CPUFreq driver which utilizes a fine grain
91 This driver adds a CPUFreq driver which utilizes the ACPI
|
| /linux-6.12.1/Documentation/w1/masters/ |
| D | w1-uart.rst | 13 UART 1-Wire bus driver. The driver utilizes the UART interface via the
|
| /linux-6.12.1/Documentation/networking/device_drivers/ethernet/intel/ |
| D | igbvf.rst | 46 The driver utilizes the ethtool interface for driver configuration and
|
| D | idpf.rst | 34 The driver utilizes the ethtool interface for driver configuration and
|
| D | e100.rst | 134 The driver utilizes the ethtool interface for driver configuration and
|
| D | igb.rst | 125 The driver utilizes the ethtool interface for driver configuration and
|
| /linux-6.12.1/Documentation/filesystems/nfs/ |
| D | pnfs.rst | 65 PNFS utilizes what is called layout drivers. The STD defines 4 basic
|
| /linux-6.12.1/drivers/pinctrl/freescale/ |
| D | Kconfig | 19 utilizes the SCMI interface to do pinctrl configuration.
|
| /linux-6.12.1/include/linux/ |
| D | alloc_tag.h | 26 * an array of these. Embedded codetag utilizes codetag framework.
|
| /linux-6.12.1/Documentation/networking/device_drivers/ethernet/aquantia/ |
| D | atlantic.rst | 59 The driver utilizes the ethtool interface for driver configuration and
266 The driver utilizes the ethtool interface for configuring ntuple filters,
|
| /linux-6.12.1/net/ipv6/ |
| D | Kconfig | 189 customer premise equipment. Like 6to4, it utilizes stateless IPv6 in
|
| /linux-6.12.1/Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 27 losing performance. In other words, one OPP under-utilizes the CPU
|
| /linux-6.12.1/Documentation/networking/pse-pd/ |
| D | pse-pi.rst | 49 - **Alternative A:** Utilizes RJ45 conductors 1, 2, 3 and 6. In either case of
55 - **Alternative B:** Utilizes RJ45 conductors 4, 5, 7 and 8. In case of
|
| /linux-6.12.1/Documentation/fb/ |
| D | intel810.rst | 47 - Utilizes user-entered monitor specifications to automatically
|
| /linux-6.12.1/scripts/dtc/ |
| D | dtx_diff | 53 and DTx utilizes '#include' or '/include/' then the path of the
|
| /linux-6.12.1/arch/s390/kernel/ |
| D | hiperdispatch.c | 32 * threshold boundary, hiperdispatch utilizes all CPUs by giving all
|
| /linux-6.12.1/drivers/usb/misc/ |
| D | Kconfig | 25 device should work. This driver utilizes manual mode.
|
1234