Searched full:compliant (Results 1 – 25 of 1030) sorted by relevance
12345678910>>...42
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/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
62 The MIPI CCS driver supports CCS static data for all compliant devices,
63 including not just those compliant with CCS 1.1 but also CCS 1.0 and SMIA(++).
69 For SMIA++ compliant devices the corresponding file names are
74 For SMIA (non-++) compliant devices the static data file name is
|
| /kernel/linux/linux-6.6/drivers/hid/ |
| D | Kconfig | 217 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
449 Support for Keytouch HID devices not fully compliant with
456 Support for KYE/Genius devices not fully compliant with HID standard:
511 Support for ITE devices not fully compliant with HID standard.
558 Support for IBM/Lenovo devices that are not fully compliant with HID standard.
561 Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
588 Support for Logitech devices that are not fully compliant with HID standard.
598 Logitech receivers are capable of pairing multiple Logitech compliant
[all …]
|
| /kernel/linux/linux-5.10/drivers/hid/ |
| D | Kconfig | 219 Support for Corsair devices that are not fully compliant with the
230 Support for Cougar devices that are not fully compliant with the
240 Support for Macally devices that are not fully compliant with the
427 Support for Keytouch HID devices not fully compliant with
435 Support for KYE/Genius devices not fully compliant with HID standard:
479 Support for ITE devices not fully compliant with HID standard.
532 Support for IBM/Lenovo devices that are not fully compliant with HID standard.
535 Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
548 Support for Logitech devices that are not fully compliant with HID standard.
558 Logitech receivers are capable of pairing multiple Logitech compliant
[all …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-6.6/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,
|
| /kernel/linux/linux-5.10/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
82 If you have a TPM security chip that is compliant with the
102 If you have a TPM security chip that is compliant with the
172 If you have a TPM security chip that is compliant with the
|
| /kernel/linux/linux-6.6/Documentation/arch/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/ |
| D | sbs,sbs-battery.yaml | 7 title: SBS compliant battery
52 SBS batteries by default send broadcast messages to SBS compliant chargers to
54 compliant charger it should be disabled via this property to avoid blocking
|
| /kernel/linux/linux-6.6/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 ARM SMC/HVC transport
41 - description: SCMI compliant firmware with SCMI Virtio transport.
45 - description: SCMI compliant firmware with OP-TEE transport
61 Specifies the mailboxes used to communicate with SCMI compliant
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/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 */
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/ti/omap/ |
| 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 */
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/ |
| D | omap-mcbsp.txt | 14 <OCP compliant irq>,
28 interrupts = <0 17 0x4>, /* OCP compliant interrupt */
|
| /kernel/linux/linux-6.6/Documentation/trace/coresight/ |
| D | coresight-trbe.rst | 18 The TRBE is not compliant to CoreSight architecture specifications, but is
20 CoreSight compliant) integration.
|
| /kernel/linux/linux-6.6/include/linux/platform_data/ |
| D | i2c-gpio.h | 21 * @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.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | omap-mcbsp.txt | 14 <OCP compliant irq>,
28 interrupts = <0 17 0x4>, /* OCP compliant interrupt */
|
12345678910>>...42