Searched full:compliant (Results 1 – 25 of 519) sorted by relevance
12345678910>>...21
| /Linux-v6.1/drivers/staging/nvec/ |
| D | Kconfig | 7 Say Y here to enable support for a nVidia compliant embedded
14 tristate "Keyboard on nVidia compliant EC"
18 a nVidia compliant embedded controller.
28 to a nVidia compliant embedded controller.
39 nVidia compliant embedded controllers.
|
| /Linux-v6.1/drivers/hid/ |
| D | Kconfig | 210 Support for Corsair devices that are not fully compliant with the
220 Support for Cougar devices that are not fully compliant with the
229 Support for Macally devices that are not fully compliant with the
428 Support for Keytouch HID devices not fully compliant with
435 Support for KYE/Genius devices not fully compliant with HID standard:
490 Support for ITE devices not fully compliant with HID standard.
537 Support for IBM/Lenovo devices that are not fully compliant with HID standard.
540 Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
567 Support for Logitech devices that are not fully compliant with HID standard.
577 Logitech receivers are capable of pairing multiple Logitech compliant
[all …]
|
| /Linux-v6.1/drivers/char/tpm/ |
| D | Kconfig | 52 If you have a TPM security chip that is compliant with the
64 non-tcg SPI master (i.e. most embedded platforms) that is compliant with the
83 If you have a TPM security chip, compliant with the TCG TPM PTP
94 If you have a TPM security chip that is compliant with the
123 If you have a TPM security chip that is compliant with the
193 If you have a TPM security chip that is compliant with the
|
| /Linux-v6.1/Documentation/hwmon/ |
| D | jc42.rst | 88 * JEDEC JC 42.4 compliant temperature sensor chips
108 This driver implements support for JEDEC JC 42.4 compliant temperature sensors,
114 to support other JC 42.4 compliant chips.
116 Example: the following will load the driver for a generic JC 42.4 compliant
122 A JC 42.4 compliant chip supports a single temperature sensor. Minimum, maximum,
|
| D | pxe1610.rst | 37 and compliant to
46 PXM1310 is a Multi-rail Controller and it is compliant to
|
| /Linux-v6.1/Documentation/ia64/ |
| D | ia64.rst | 20 Compiling and running this kernel requires an IA-64 compliant GCC
22 IA-64 compliant GCC compiler.
35 compliant GCC compiler.
|
| /Linux-v6.1/Documentation/devicetree/bindings/power/supply/ |
| D | sbs,sbs-battery.yaml | 7 title: SBS compliant battery
55 SBS batteries by default send broadcast messages to SBS compliant chargers to
57 compliant charger it should be disabled via this property to avoid blocking
|
| /Linux-v6.1/Documentation/devicetree/bindings/firmware/ |
| D | arm,scmi.yaml | 31 - description: SCMI compliant firmware with mailbox transport
34 - description: SCMI compliant firmware with ARM SMC/HVC transport
37 - description: SCMI compliant firmware with SCMI Virtio transport.
41 - description: SCMI compliant firmware with OP-TEE transport
57 Specifies the mailboxes used to communicate with SCMI compliant
|
| /Linux-v6.1/Documentation/fb/ |
| D | uvesafb.rst | 2 uvesafb - A Generic Driver for VBE2+ compliant video cards
8 uvesafb should work with any video card that has a Video BIOS compliant
43 - Adjusting the refresh rate is only possible with a VBE 3.0 compliant
45 compliant, while they simply ignore any refresh rate settings.
119 has any effect only if the Video BIOS is VBE 3.0 compliant. Use it
|
| /Linux-v6.1/Documentation/userspace-api/media/drivers/ |
| D | ccs.rst | 9 <https://www.mipi.org/specifications/camera-command-set>`_ compliant
20 as analogue crop functionality present in many compliant devices. The analogue
63 ``V4L2_CID_USER_BASE_CCS`` to control the MIPI CCS compliant camera sensors.
|
| /Linux-v6.1/arch/powerpc/kernel/ |
| D | cpu_specs_book3s_64.h | 176 { /* POWER6 in P5+ mode; 2.04-compliant processor */
200 { /* 2.05-compliant processor, i.e. Power6 "architected" mode */
211 { /* 2.06-compliant processor, i.e. Power7 "architected" mode */
226 { /* 2.07-compliant processor, i.e. Power8 "architected" mode */
241 { /* 3.00-compliant processor, i.e. Power9 "architected" mode */
255 { /* 3.1-compliant processor, i.e. Power10 "architected" mode */
|
| /Linux-v6.1/drivers/mtd/chips/ |
| D | Kconfig | 13 support any device that is CFI-compliant, you need to enable this
186 sets which a CFI-compliant chip may claim to implement. This code
196 sets which a CFI-compliant chip may claim to implement. This code
206 sets which a CFI-compliant chip may claim to implement. This code
|
| /Linux-v6.1/arch/arm/boot/dts/ |
| D | omap2430.dtsi | 179 interrupts = <64>, /* OCP compliant interrupt */
196 interrupts = <16>, /* OCP compliant interrupt */
212 interrupts = <17>, /* OCP compliant interrupt */
228 interrupts = <18>, /* OCP compliant interrupt */
244 interrupts = <19>, /* OCP compliant interrupt */
|
| /Linux-v6.1/Documentation/devicetree/bindings/sound/ |
| D | omap-mcbsp.txt | 14 <OCP compliant irq>,
28 interrupts = <0 17 0x4>, /* OCP compliant interrupt */
|
| /Linux-v6.1/Documentation/trace/coresight/ |
| D | coresight-trbe.rst | 18 The TRBE is not compliant to CoreSight architecture specifications, but is
20 CoreSight compliant) integration.
|
| /Linux-v6.1/arch/arm/mach-omap2/ |
| D | omap_hwmod_common_data.c | 27 * if the device ip is compliant with the original PRCM protocol
43 * device ip is compliant with the new PRCM protocol defined for new
|
| /Linux-v6.1/Documentation/devicetree/bindings/pci/ |
| D | host-generic-pci.yaml | 62 compliant for all devices other than the root complex.
85 CAM or ECAM compliant PCI host controllers without any quirks
95 default). Some host controllers have a 2nd non-compliant address range,
|
| /Linux-v6.1/Documentation/x86/i386/ |
| D | IO-APIC.rst | 9 Most (all) Intel-MP compliant SMP boards have the so-called 'IO-APIC',
15 Linux supports all variants of compliant SMP boards, including ones with
20 usually worked around by the kernel. If your MP-compliant SMP board does
|
| /Linux-v6.1/drivers/usb/cdns3/ |
| D | Kconfig | 47 Host controller is compliant with XHCI so it will use
119 Host controller is compliant with XHCI so it uses
|
| /Linux-v6.1/drivers/pci/ |
| D | ecam.c | 44 /* ECAM-compliant platforms need not supply ops->bus_shift */ in pci_ecam_create()
212 /* ECAM ops for 32-bit access only (non-compliant) */
223 /* ECAM ops for 32-bit read only (non-compliant) */
|
| /Linux-v6.1/drivers/hwmon/pmbus/ |
| D | fsp-3y.c | 113 * Inject an exponent for non-compliant YH5151-E. in fsp3y_read_byte_data()
164 * Handle YH-5151E non-compliant linear11 vout voltage. in fsp3y_read_word_data()
265 * device is compliant and uses linear16. in fsp3y_probe()
|
| /Linux-v6.1/drivers/phy/qualcomm/ |
| D | Kconfig | 78 Support for the USB high-speed ULPI compliant phy on Qualcomm
96 Support for the USB HSIC ULPI compliant PHY on QCOM chipsets.
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-devices-soc | 29 On many of ARM based silicon with SMCCC v1.2+ compliant firmware
67 On many of ARM based silicon with SMCCC v1.2+ compliant firmware
|
| /Linux-v6.1/Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 8 Basically all FireWire controllers which are in use today are compliant
100 CardBus and even some Express cards which are fully compliant to OHCI-1394
103 compliant, they are based on TI PCILynx chips and require drivers for Windows
|
| /Linux-v6.1/Documentation/driver-api/media/drivers/ccs/ |
| D | ccs.rst | 9 <https://www.mipi.org/specifications/camera-command-set>`_ compliant
20 as analogue crop functionality present in many compliant devices. The analogue
|
12345678910>>...21
