Searched +full:non +full:- +full:compliant (Results 1 – 25 of 381) sorted by relevance
12345678910>>...16
| /kernel/linux/linux-5.10/drivers/hid/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
15 most commonly used to refer to the USB-HID specification, but other
20 removed from the HID bus by the transport-layer drivers, such as
53 to work on raw hid events when they want to, and avoid using transport-specific
59 tristate "User-space I/O driver support for HID subsystem"
63 Say Y here if you want to provide HID I/O Drivers from user-space.
64 This allows to write I/O drivers in user-space and feed the data from
67 user-space device.
69 This driver cannot be used to parse HID-reports in user-space and write
70 special HID-drivers. You should use hidraw for that.
[all …]
|
| /kernel/linux/linux-4.19/drivers/hid/ |
| D | Kconfig | 11 ---help---
14 most commonly used to refer to the USB-HID specification, but other
19 removed from the HID bus by the transport-layer drivers, such as
33 ---help---
41 ---help---
52 to work on raw hid events when they want to, and avoid using transport-specific
58 tristate "User-space I/O driver support for HID subsystem"
61 ---help---
62 Say Y here if you want to provide HID I/O Drivers from user-space.
63 This allows to write I/O drivers in user-space and feed the data from
[all …]
|
| /kernel/linux/linux-4.19/Documentation/x86/i386/ |
| D | IO-APIC.txt | 1 Most (all) Intel-MP compliant SMP boards have the so-called 'IO-APIC',
4 IO-APIC, interrupts from hardware will be delivered only to the
7 Linux supports all variants of compliant SMP boards, including ones with
8 multiple IO-APICs. Multiple IO-APICs are used in high-end servers to
12 usually worked around by the kernel. If your MP-compliant SMP board does
13 not boot Linux, then consult the linux-smp mailing list archives first.
15 If your box boots fine with enabled IO-APIC IRQs, then your
18 ---------------------------->
21 0: 1360293 IO-APIC-edge timer
22 1: 4 IO-APIC-edge keyboard
[all …]
|
| /kernel/linux/linux-5.10/Documentation/x86/i386/ |
| D | IO-APIC.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 IO-APIC
9 Most (all) Intel-MP compliant SMP boards have the so-called 'IO-APIC',
12 IO-APIC, interrupts from hardware will be delivered only to the
15 Linux supports all variants of compliant SMP boards, including ones with
16 multiple IO-APICs. Multiple IO-APICs are used in high-end servers to
20 usually worked around by the kernel. If your MP-compliant SMP board does
21 not boot Linux, then consult the linux-smp mailing list archives first.
23 If your box boots fine with enabled IO-APIC IRQs, then your
28 0: 1360293 IO-APIC-edge timer
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/chips/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 support any device that is CFI-compliant, you need to enable this
18 tristate "Detect non-CFI AMD/JEDEC-compatible flash chips"
22 This option enables JEDEC-style probing of flash chips which are not
24 CFI-targeted flash drivers for any chips which are identified which
26 covers most AMD/Fujitsu-compatible chips and also non-CFI
53 are expected to be wired to the CPU in 'host-endian' form.
83 bool "Support 8-bit buswidth" if MTD_CFI_GEOMETRY
90 bool "Support 16-bit buswidth" if MTD_CFI_GEOMETRY
97 bool "Support 32-bit buswidth" if MTD_CFI_GEOMETRY
[all …]
|
| /kernel/linux/linux-4.19/drivers/mtd/chips/ |
| D | Kconfig | 12 support any device that is CFI-compliant, you need to enable this
17 tristate "Detect non-CFI AMD/JEDEC-compatible flash chips"
21 This option enables JEDEC-style probing of flash chips which are not
23 CFI-targeted flash drivers for any chips which are identified which
25 covers most AMD/Fujitsu-compatible chips and also non-CFI
52 are expected to be wired to the CPU in 'host-endian' form.
82 bool "Support 8-bit buswidth" if MTD_CFI_GEOMETRY
89 bool "Support 16-bit buswidth" if MTD_CFI_GEOMETRY
96 bool "Support 32-bit buswidth" if MTD_CFI_GEOMETRY
103 bool "Support 64-bit buswidth" if MTD_CFI_GEOMETRY
[all …]
|
| /kernel/linux/linux-5.10/drivers/char/tpm/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
26 which is required to validate the PCR 0-7 values.
52 If you have a TPM security chip that is compliant with the
59 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (SPI)"
64 non-tcg SPI master (i.e. most embedded platforms) that is compliant with the
78 tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface (MMIO - SynQuacer)"
82 If you have a TPM security chip that is compliant with the
90 tristate "TPM Interface Specification 1.2 Interface (I2C - Atmel)"
99 tristate "TPM Interface Specification 1.2 Interface (I2C - Infineon)"
102 If you have a TPM security chip that is compliant with the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/ |
| D | host-generic-pci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/host-generic-pci.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Will Deacon <will@kernel.org>
13 Firmware-initialised PCI host controllers and PCI emulations, such as the
14 virtio-pci implementations found in kvmtool and other para-virtualised
21 Configuration Space is assumed to be memory-mapped (as opposed to being
26 For CAM, this 24-bit offset is:
41 - description:
[all …]
|
| /kernel/linux/linux-4.19/Documentation/fb/ |
| D | uvesafb.txt | 2 uvesafb - A Generic Driver for VBE2+ compliant video cards
6 ---------------
8 uvesafb should work with any video card that has a Video BIOS compliant
30 --------------------------
36 - Lack of any type of acceleration.
37 - A strict and limited set of supported video modes. Often the native
42 ratio, which is what most BIOS-es are limited to.
43 - Adjusting the refresh rate is only possible with a VBE 3.0 compliant
44 Video BIOS. Note that many nVidia Video BIOS-es claim to be VBE 3.0
45 compliant, while they simply ignore any refresh rate settings.
[all …]
|
| /kernel/linux/linux-4.19/drivers/char/tpm/ |
| D | Kconfig | 11 ---help---
25 which is required to validate the PCR 0-7 values.
33 ---help---
42 ---help---
50 ---help---
51 If you have a TPM security chip that is compliant with the
58 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (SPI)"
61 ---help---
63 non-tcg SPI master (i.e. most embedded platforms) that is compliant with the
70 tristate "TPM Interface Specification 1.2 Interface (I2C - Atmel)"
[all …]
|
| /kernel/linux/linux-5.10/drivers/pci/ |
| D | ecam.c | 1 // SPDX-License-Identifier: GPL-2.0
11 #include <linux/pci-ecam.h>
15 * On 64-bit systems, we do a single ioremap for the whole config space
16 * since we have enough virtual address range available. On 32-bit, we
23 * - reserve mem region
24 * - alloc struct pci_config_window with space for all mappings
25 * - ioremap the config space
36 if (busr->start > busr->end) in pci_ecam_create()
37 return ERR_PTR(-EINVAL); in pci_ecam_create()
41 return ERR_PTR(-ENOMEM); in pci_ecam_create()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| D | uvesafb.rst | 2 uvesafb - A Generic Driver for VBE2+ compliant video cards
6 ---------------
8 uvesafb should work with any video card that has a Video BIOS compliant
30 --------------------------
36 - Lack of any type of acceleration.
37 - A strict and limited set of supported video modes. Often the native
42 ratio, which is what most BIOS-es are limited to.
43 - Adjusting the refresh rate is only possible with a VBE 3.0 compliant
44 Video BIOS. Note that many nVidia Video BIOS-es claim to be VBE 3.0
45 compliant, while they simply ignore any refresh rate settings.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 5 - compatible : should be "opencores,or1k-pic-level" for variants with
6 level triggered interrupt lines, "opencores,or1k-pic-edge" for variants with
7 edge triggered interrupt lines or "opencores,or1200-pic" for machines
8 with the non-spec compliant or1200 type implementation.
10 "opencores,or1k-pic" is also provided as an alias to "opencores,or1200-pic",
13 - interrupt-controller : Identifies the node as an interrupt controller
14 - #interrupt-cells : Specifies the number of cells needed to encode an
19 intc: interrupt-controller {
20 compatible = "opencores,or1k-pic-level";
21 interrupt-controller;
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 5 - compatible : should be "opencores,or1k-pic-level" for variants with
6 level triggered interrupt lines, "opencores,or1k-pic-edge" for variants with
7 edge triggered interrupt lines or "opencores,or1200-pic" for machines
8 with the non-spec compliant or1200 type implementation.
10 "opencores,or1k-pic" is also provided as an alias to "opencores,or1200-pic",
13 - interrupt-controller : Identifies the node as an interrupt controller
14 - #interrupt-cells : Specifies the number of cells needed to encode an
19 intc: interrupt-controller {
20 compatible = "opencores,or1k-pic-level";
21 interrupt-controller;
[all …]
|
| /kernel/linux/linux-4.19/sound/usb/ |
| D | card.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
16 unsigned int fmt_type; /* USB audio format type (1-3) */
17 unsigned int frame_size; /* samples per frame for non-audio */
128 unsigned int txfr_quirk:1; /* allow sub-frame alignment */
130 unsigned int fmt_type; /* USB audio format type (1-3) */
131 …unsigned int pkt_offset_adj; /* Bytes to drop from beginning of packets (for non-compliant devices…
132 …unsigned int stream_offset_adj; /* Bytes to drop from beginning of stream (for non-compliant devic…
171 unsigned int fmt_type; /* USB audio format type (1-3) */
|
| /kernel/linux/linux-5.10/LICENSES/exceptions/ |
| D | GCC-exception-2.0 | 1 SPDX-Exception-Identifier: GCC-exception-2.0
2 SPDX-URL: https://spdx.org/licenses/GCC-exception-2.0.html
3 SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-2.0-only, GPL-2.0-or-later
4 Usage-Guide:
5 This exception is used together with one of the above SPDX-Licenses to
6 allow linking the compiled version of code to non GPL compliant code.
8 identifiers in the SPDX-Licenses tag:
9 SPDX-License-Identifier: <SPDX-License> WITH GCC-exception-2.0
10 License-Text:
|
| D | Linux-syscall-note | 1 SPDX-Exception-Identifier: Linux-syscall-note
2 SPDX-URL: https://spdx.org/licenses/Linux-syscall-note.html
3 SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-1.0+, LGPL-2.0, LGPL-2.0+, LGPL-2.1, LGPL-2.1+, GPL-2.0-only,…
4 Usage-Guide:
5 This exception is used together with one of the above SPDX-Licenses
7 into non GPL compliant user space application code.
9 identifiers in the SPDX-Licenses tag:
10 SPDX-License-Identifier: <SPDX-License> WITH Linux-syscall-note
11 License-Text:
14 services by normal system calls - this is merely considered normal use
|
| /kernel/linux/linux-5.10/drivers/uio/ |
| D | uio_pci_generic.c | 1 // SPDX-License-Identifier: GPL-2.0
2 /* uio_pci_generic - generic UIO driver for PCI 2.3 devices
11 * # echo -n 0000:00:19.0 > /sys/bus/pci/drivers/e1000e/unbind
12 * # echo -n 0000:00:19.0 > /sys/bus/pci/drivers/uio_pci_generic/bind
13 * # ls -l /sys/bus/pci/devices/0000:00:19.0/driver
14 * .../0000:00:19.0/driver -> ../../../bus/pci/drivers/uio_pci_generic
17 * in the command register. All devices compliant to PCI 2.3 (circa 2002) and
18 * all compliant PCI Express devices should support this bit.
51 * Note that there's a non-zero chance doing this will wedge the device in release()
54 pci_clear_master(gdev->pdev); in release()
[all …]
|
| /kernel/linux/linux-5.10/sound/usb/ |
| D | card.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
16 unsigned int fmt_type; /* USB audio format type (1-3) */
18 unsigned int frame_size; /* samples per frame for non-audio */
136 unsigned int txfr_quirk:1; /* allow sub-frame alignment */
138 unsigned int fmt_type; /* USB audio format type (1-3) */
139 …unsigned int pkt_offset_adj; /* Bytes to drop from beginning of packets (for non-compliant devices…
140 …unsigned int stream_offset_adj; /* Bytes to drop from beginning of stream (for non-compliant devic…
180 unsigned int fmt_type; /* USB audio format type (1-3) */
|
| /kernel/linux/linux-4.19/LICENSES/exceptions/ |
| D | Linux-syscall-note | 1 SPDX-Exception-Identifier: Linux-syscall-note
2 SPDX-URL: https://spdx.org/licenses/Linux-syscall-note.html
3 SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-1.0+, LGPL-2.0, LGPL-2.0+, LGPL-2.1, LGPL-2.1+, GPL-2.0-only,…
4 Usage-Guide:
5 This exception is used together with one of the above SPDX-Licenses
7 into non GPL compliant user space application code.
9 identifiers in the SPDX-Licenses tag:
10 SPDX-License-Identifier: <SPDX-License> WITH Linux-syscall-note
11 License-Text:
14 services by normal system calls - this is merely considered normal use
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
6 ------------
8 Basically all FireWire controllers which are in use today are compliant
9 to the OHCI-1394 specification which defines the controller to be a PCI
12 PCI-Bus master DMA after applying filters defined by the OHCI-1394 driver.
15 ask the OHCI-1394 controller to perform read and write requests on
28 more common hardware such as x86, x86-64 and PowerPC.
34 Together with a early initialization of the OHCI-1394 controller for debugging,
41 -------
43 The firewire-ohci driver in drivers/firewire uses filtered physical
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | debugging-via-ohci1394.txt | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
6 ------------
8 Basically all FireWire controllers which are in use today are compliant
9 to the OHCI-1394 specification which defines the controller to be a PCI
12 PCI-Bus master DMA after applying filters defined by the OHCI-1394 driver.
15 ask the OHCI-1394 controller to perform read and write requests on
28 more common hardware such as x86, x86-64 and PowerPC.
34 Together with a early initialization of the OHCI-1394 controller for debugging,
41 -------
43 The firewire-ohci driver in drivers/firewire uses filtered physical
[all …]
|
| /kernel/linux/linux-4.19/Documentation/filesystems/ |
| D | overlayfs.txt | 8 overlay-filesystem functionality in Linux (sometimes referred to as
9 union-filesystems). An overlay-filesystem tries to present a
15 ---------------
23 While directories will report an st_dev from the overlay-filesystem,
24 non-directory objects may report an st_dev from the lower filesystem or
27 over the lifetime of a non-directory object. Many applications and
33 make the overlay mount more compliant with filesystem scanners and
38 underlying filesystem, the same compliant behavior could be achieved
45 feature with the "-o xino=on" overlay mount option. That is useful for the
51 ---------------
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/ |
| D | Kconfig-nommu | 1 # SPDX-License-Identifier: GPL-2.0
3 # Kconfig for uClinux(non-paged MM) depend configurations
37 used instead of the auto-probing which utilizes the register.
45 occupied by read-only memory depending on H/W design.
47 If the region contains read-write memory, say 'n' here.
57 bool 'Use the ARM v7 PMSA Compliant MPU'
|
| /kernel/linux/linux-4.19/arch/arm/ |
| D | Kconfig-nommu | 1 # SPDX-License-Identifier: GPL-2.0
3 # Kconfig for uClinux(non-paged MM) depend configurations
35 used instead of the auto-probing which utilizes the register.
43 occupied by read-only memory depending on H/W design.
45 If the region contains read-write memory, say 'n' here.
55 bool 'Use the ARM v7 PMSA Compliant MPU'
|
12345678910>>...16