| /linux/drivers/staging/nvec/ |
| H A 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/Documentation/driver-api/media/drivers/ccs/ |
| H A D | ccs.rst | 11 <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/Documentation/hwmon/ |
| H A D | spd5118.rst | 8 * 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,
|
| H A 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,
|
| H A D | pxe1610.rst | 37 and compliant to
46 PXM1310 is a Multi-rail Controller and it is compliant to
|
| /linux/drivers/char/tpm/ |
| H A D | Kconfig | 66 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/arch/powerpc/kernel/ |
| H A D | cpu_specs_book3s_64.h | 179 { /* 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/Documentation/devicetree/bindings/power/supply/ |
| H A 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/Documentation/devicetree/bindings/firmware/ |
| H A D | arm,scmi.yaml | 34 - 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/Documentation/fb/ |
| H A 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/Documentation/userspace-api/media/drivers/ |
| H A D | ccs.rst | 11 <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/drivers/mtd/chips/ |
| H A 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/arch/arm/boot/dts/ti/omap/ |
| H A 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/Documentation/devicetree/bindings/sound/ |
| H A D | omap-mcbsp.txt | 14 <OCP compliant irq>,
28 interrupts = <0 17 0x4>, /* OCP compliant interrupt */
|
| /linux/Documentation/trace/coresight/ |
| H A D | coresight-trbe.rst | 18 The TRBE is not compliant to CoreSight architecture specifications, but is
20 CoreSight compliant) integration.
|
| /linux/include/linux/platform_data/ |
| H A 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.
|
| /linux/arch/arm/mach-omap2/ |
| H A 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/drivers/hid/ |
| H A D | hid-keytouch.c | 3 * 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/Documentation/arch/x86/i386/ |
| H A 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/Documentation/devicetree/bindings/pci/ |
| H A 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/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | intel,ce4100-lapic.yaml | 46 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/drivers/hwmon/pmbus/ |
| H A 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()
264 * device is compliant and uses linear16. in fsp3y_probe()
|
| /linux/drivers/pci/ |
| H A D | ecam.c | 44 /* ECAM-compliant platforms need not supply ops->bus_shift */ in pci_ecam_create()
214 /* ECAM ops for 32-bit access only (non-compliant) */
225 /* ECAM ops for 32-bit read only (non-compliant) */
|
| /linux/drivers/usb/cdns3/ |
| H A D | Kconfig | 47 Host controller is compliant with XHCI so it will use
130 Host controller is compliant with XHCI so it uses
|
| /linux/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-gpio.yaml | 72 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.
|