Home
last modified time | relevance | path

Searched full:compliant (Results 1 – 25 of 567) sorted by relevance

12345678910>>...23

/linux-6.12.1/drivers/staging/nvec/
DKconfig7 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-6.12.1/Documentation/driver-api/media/drivers/ccs/
Dccs.rst11 <https://www.mipi.org/specifications/camera-command-set>`_ compliant
19 The MIPI CCS driver supports CCS static data for all compliant devices,
20 including not just those compliant with CCS 1.1 but also CCS 1.0 and SMIA(++).
26 For SMIA++ compliant devices the corresponding file names are
31 For SMIA (non-++) compliant devices the static data file name is
/linux-6.12.1/Documentation/hwmon/
Dspd5118.rst8 * SPD5118 (JEDEC JESD300) compliant temperature sensor chips
26 This driver implements support for SPD5118 (JEDEC JESD300) compliant temperature
30 The driver auto-detects SPD5118 compliant chips, but can also be instantiated
33 A SPD5118 compliant chip supports a single temperature sensor. Critical minimum,
Djc42.rst88 * 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,
Dpxe1610.rst37 and compliant to
46 PXM1310 is a Multi-rail Controller and it is compliant to
/linux-6.12.1/drivers/hid/
DKconfig217 Support for Corsair devices that are not fully compliant with the
227 Support for Cougar devices that are not fully compliant with the
236 Support for Macally devices that are not fully compliant with the
455 Support for Keytouch HID devices not fully compliant with
462 Support for KYE/Genius devices not fully compliant with HID standard:
517 Support for ITE devices not fully compliant with HID standard.
564 Support for IBM/Lenovo devices that are not fully compliant with HID standard.
567 Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
594 Support for Logitech devices that are not fully compliant with HID standard.
604 Logitech receivers are capable of pairing multiple Logitech compliant
[all …]
Dhid-keytouch.c3 * HID driver for Keytouch devices not fully compliant with HID standard
49 MODULE_DESCRIPTION("HID driver for Keytouch devices not fully compliant with HID standard");
/linux-6.12.1/drivers/char/tpm/
DKconfig66 If you have a TPM security chip that is compliant with the
78 non-tcg SPI master (i.e. most embedded platforms) that is compliant with the
97 If you have a TPM security chip, compliant with the TCG TPM PTP
108 If you have a TPM security chip that is compliant with the
137 If you have a TPM security chip that is compliant with the
208 If you have a TPM security chip that is compliant with the
/linux-6.12.1/Documentation/devicetree/bindings/power/supply/
Dsbs,sbs-battery.yaml7 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-6.12.1/arch/powerpc/kernel/
Dcpu_specs_book3s_64.h179 { /* POWER6 in P5+ mode; 2.04-compliant processor */
203 { /* 2.05-compliant processor, i.e. Power6 "architected" mode */
214 { /* 2.06-compliant processor, i.e. Power7 "architected" mode */
229 { /* 2.07-compliant processor, i.e. Power8 "architected" mode */
244 { /* 2.07-compliant processor, HeXin C2000 processor */
259 { /* 3.00-compliant processor, i.e. Power9 "architected" mode */
273 { /* 3.1-compliant processor, i.e. Power10 "architected" mode */
287 { /* 3.1-compliant processor, i.e. Power11 "architected" mode */
/linux-6.12.1/Documentation/devicetree/bindings/firmware/
Darm,scmi.yaml34 - description: SCMI compliant firmware with mailbox transport
37 - description: SCMI compliant firmware with ARM SMC/HVC transport
40 - description: SCMI compliant firmware with ARM SMC/HVC transport
44 - description: SCMI compliant firmware with Qualcomm SMC/HVC transport
47 - description: SCMI compliant firmware with SCMI Virtio transport.
51 - description: SCMI compliant firmware with OP-TEE transport
67 Specifies the mailboxes used to communicate with SCMI compliant
/linux-6.12.1/Documentation/fb/
Duvesafb.rst2 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-6.12.1/Documentation/userspace-api/media/drivers/
Dccs.rst11 <https://www.mipi.org/specifications/camera-command-set>`_ compliant
24 as analogue crop functionality present in many compliant devices. The analogue
67 ``V4L2_CID_USER_BASE_CCS`` to control the MIPI CCS compliant camera sensors.
/linux-6.12.1/drivers/mtd/chips/
DKconfig13 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-6.12.1/arch/arm/boot/dts/ti/omap/
Domap2430.dtsi179 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-6.12.1/Documentation/trace/coresight/
Dcoresight-trbe.rst18 The TRBE is not compliant to CoreSight architecture specifications, but is
20 CoreSight compliant) integration.
/linux-6.12.1/Documentation/devicetree/bindings/sound/
Domap-mcbsp.txt14 <OCP compliant irq>,
28 interrupts = <0 17 0x4>, /* OCP compliant interrupt */
/linux-6.12.1/include/linux/platform_data/
Di2c-gpio.h21 * @sda_has_no_pullup: SDA is used in a non-compliant way and has no pull-up.
26 * @scl_has_no_pullup: SCL is used in a non-compliant way and has no pull-up.
/linux-6.12.1/arch/arm/mach-omap2/
Domap_hwmod_common_data.c27 * 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-6.12.1/Documentation/devicetree/bindings/pci/
Dhost-generic-pci.yaml62 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-6.12.1/Documentation/arch/x86/i386/
DIO-APIC.rst9 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-6.12.1/Documentation/devicetree/bindings/interrupt-controller/
Dintel,ce4100-lapic.yaml46 PIC Mode - Legacy external 8259 compliant PIC interrupt controller.
48 For ACPI or MPS spec compliant systems, it is figured out by some read
/linux-6.12.1/drivers/usb/cdns3/
DKconfig47 Host controller is compliant with XHCI so it will use
130 Host controller is compliant with XHCI so it uses
/linux-6.12.1/Documentation/devicetree/bindings/i2c/
Di2c-gpio.yaml72 description: sda is used in a non-compliant way and has no pull-up.
78 description: scl is used in a non-compliant way and has no pull-up.
/linux-6.12.1/drivers/hwmon/pmbus/
Dfsp-3y.c113 * 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()
264 * device is compliant and uses linear16. in fsp3y_probe()

12345678910>>...23