Home
last modified time | relevance | path

Searched +full:non +full:- +full:compliant (Results 1 – 25 of 203) sorted by relevance

123456789

/Linux-v5.15/drivers/hid/
DKconfig1 # 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 …]
/Linux-v5.15/Documentation/x86/i386/
DIO-APIC.rst1 .. 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 …]
/Linux-v5.15/drivers/mtd/chips/
DKconfig1 # 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 …]
/Linux-v5.15/Documentation/devicetree/bindings/pci/
Dhost-generic-pci.yaml1 # 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 …]
/Linux-v5.15/drivers/char/tpm/
DKconfig1 # 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 2.0 Interface (I2C - CR50)"
99 tristate "TPM Interface Specification 1.2 Interface (I2C - Atmel)"
108 tristate "TPM Interface Specification 1.2 Interface (I2C - Infineon)"
[all …]
/Linux-v5.15/drivers/pci/
Decam.c1 // 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
31 unsigned int bus_shift = ops->bus_shift; in pci_ecam_create()
37 if (busr->start > busr->end) in pci_ecam_create()
38 return ERR_PTR(-EINVAL); in pci_ecam_create()
[all …]
/Linux-v5.15/drivers/hwmon/pmbus/
Dfsp-3y.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Hardware monitoring driver for FSP 3Y-Power PSUs
56 return -EINVAL; in page_log_to_page_real()
66 return -EINVAL; in page_log_to_page_real()
69 return -EINVAL; in page_log_to_page_real()
82 page_real = page_log_to_page_real(page_log, data->chip); in set_page()
86 if (data->page != page_real) { in set_page()
91 data->page = page_real; in set_page()
113 * Inject an exponent for non-compliant YH5151-E. in fsp3y_read_byte_data()
115 if (data->vout_linear_11 && reg == PMBUS_VOUT_MODE) in fsp3y_read_byte_data()
[all …]
/Linux-v5.15/Documentation/fb/
Duvesafb.rst2 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 …]
/Linux-v5.15/Documentation/devicetree/bindings/interrupt-controller/
Dopencores,or1k-pic.txt5 - 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 …]
/Linux-v5.15/LICENSES/exceptions/
DGCC-exception-2.01 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:
DLinux-syscall-note1 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
/Linux-v5.15/sound/usb/
Dcard.h1 /* 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 */
66 int opened; /* open refcount; protect with chip->mutex */
128 bool need_setup; /* (re-)need for configure? */
155 unsigned int txfr_quirk:1; /* allow sub-frame alignment */
157 unsigned int fmt_type; /* USB audio format type (1-3) */
158 …unsigned int pkt_offset_adj; /* Bytes to drop from beginning of packets (for non-compliant devices…
159 …unsigned int stream_offset_adj; /* Bytes to drop from beginning of stream (for non-compliant devic…
165 unsigned int inflight_bytes; /* in-flight data bytes on buffer (for playback) */
[all …]
/Linux-v5.15/drivers/uio/
Duio_pci_generic.c1 // 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 …]
/Linux-v5.15/Documentation/core-api/
Ddebugging-via-ohci1394.rst2 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 …]
/Linux-v5.15/Documentation/filesystems/
Doverlayfs.rst1 .. SPDX-License-Identifier: GPL-2.0
10 overlay-filesystem functionality in Linux (sometimes referred to as
11 union-filesystems). An overlay-filesystem tries to present a
17 ---------------
25 While directories will report an st_dev from the overlay-filesystem,
26 non-directory objects may report an st_dev from the lower filesystem or
29 over the lifetime of a non-directory object. Many applications and
35 make the overlay mount more compliant with filesystem scanners and
40 underlying filesystem, the same compliant behavior could be achieved
46 filesystem will fall back to the non xino behavior for that inode.
[all …]
/Linux-v5.15/arch/arm/
DKconfig-nommu1 # 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'
/Linux-v5.15/Documentation/devicetree/bindings/firmware/
Darm,scpi.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Sudeep Holla <sudeep.holla@arm.com>
29 SCPI compliant firmware complying to SCPI v1.0 and above OR
30 SCPI compliant firmware complying to all unversioned releases
33 - const: arm,scpi # SCPI v1.0 and above
34 - const: arm,scpi-pre-1.0 # Unversioned SCPI before v1.0
35 - items:
36 - enum:
[all …]
/Linux-v5.15/Documentation/hwmon/
Dlineage-pem.rst1 Kernel driver lineage-pem
8 Prefix: 'lineage-pem'
10 Addresses scanned: -
16 Author: Guenter Roeck <linux@roeck-us.net>
20 -----------
25 Lineage CPL power entry modules are nominally PMBus compliant. However, most
27 and status reporting commands are non-standard. For this reason, a standard
32 -----------
41 $ modprobe lineage-pem
42 $ echo lineage-pem 0x40 > /sys/bus/i2c/devices/i2c-1/new_device
[all …]
/Linux-v5.15/include/linux/
Dio.h1 /* SPDX-License-Identifier: GPL-2.0-only */
76 * Posting") mandate non-posted configuration transactions. This default
80 * support non-posted accesses should implement ioremap_np() instead, which
81 * this default implementation can then use to return mappings compliant with
106 * end up write-combining. This facility should be used in conjunction
107 * with pgprot_writecombine, ioremap-wc, or set_memory_wc, since it has
108 * no effect if the per-page mechanisms are functional.
129 return -1; in arch_phys_wc_index()
136 /* See memremap() kernel-doc for usage description... */
150 * all the in-kernel mapping APIs (ioremap*), but where the user
/Linux-v5.15/drivers/pci/hotplug/
Drpaphp_pci.c1 // SPDX-License-Identifier: GPL-2.0+
3 * PCI Hot Plug Controller Driver for RPA-compliant PPC64 platform.
14 #include <asm/pci-bridge.h>
26 rc = rtas_get_sensor(DR_ENTITY_SENSE, slot->index, state); in rpaphp_get_sensor_state()
29 if (rc == -EFAULT || rc == -EEXIST) { in rpaphp_get_sensor_state()
30 dbg("%s: slot must be power up to get sensor-state\n", in rpaphp_get_sensor_state()
34 * before get-sensor will succeed. in rpaphp_get_sensor_state()
36 rc = rtas_set_power_level(slot->power_domain, POWER_ON, in rpaphp_get_sensor_state()
40 __func__, slot->name, rc); in rpaphp_get_sensor_state()
43 slot->index, state); in rpaphp_get_sensor_state()
[all …]
/Linux-v5.15/drivers/platform/x86/intel/wmi/
Dsbl-fw-update.c1 // SPDX-License-Identifier: GPL-2.0
5 * Slim Bootloader is a small, open-source, non UEFI compliant, boot firmware
8 * SBL exposes an ACPI-WMI device via /sys/bus/wmi/devices/<INTEL_WMI_SBL_GUID>.
14 * https://slimbootloader.github.io/security/firmware-update.html
24 #define INTEL_WMI_SBL_GUID "44FADEB1-B204-40F2-8581-394BBDC1B651"
35 return -ENODEV; in get_fwu_request()
39 if (!obj || obj->type != ACPI_TYPE_INTEGER) { in get_fwu_request()
42 return -EINVAL; in get_fwu_request()
45 *out = obj->integer.value; in get_fwu_request()
64 return -ENODEV; in set_fwu_request()
[all …]
/Linux-v5.15/arch/powerpc/include/asm/nohash/
Dpte-book3e.h1 /* SPDX-License-Identifier: GPL-2.0 */
6 /* PTE bit definitions for processors compliant to the Book3E
48 #define _PAGE_WRITETHRU 0x800000 /* W: cache write-through */
69 /* On 32-bit, we never clear the top part of the PTE */
82 * cacheable kernel and user pages) and one for non cacheable
/Linux-v5.15/Documentation/hid/
Dhiddev.rst18 normalised event interface - see Documentation/input/input.rst
24 usb.c ---> hid-core.c ----> hid-input.c ----> [keyboard/mouse/joystick/event]
27 --> hiddev.c ----> POWER / MONITOR CONTROL
57 So you point your hiddev compliant user-space program at the correct
60 Assuming that you have a hiddev compliant user-space program, of
69 conveniently linked of http://www.linux-usb.org.
75 each of which can have one or more "usages". In the hid-core,
76 each one of these usages has a single signed 32-bit value.
79 -------
83 the changed value. The hid-core.c module parses the report, and
[all …]
/Linux-v5.15/Documentation/devicetree/bindings/dma/ti/
Dk3-udma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
5 ---
6 $id: http://devicetree.org/schemas/dma/ti/k3-udma.yaml#
7 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 - Peter Ujfalusi <peter.ujfalusi@gmail.com>
15 The UDMA-P is intended to perform similar (but significantly upgraded)
16 functions as the packet-oriented DMA used on previous SoC devices. The UDMA-P
18 The UDMA-P architecture facilitates the segmentation and reassembly of SoC DMA
19 data structure compliant packets to/from smaller data blocks that are natively
29 on the Rx PSI-L interface.
[all …]
/Linux-v5.15/lib/raid6/
DMakefile1 # SPDX-License-Identifier: GPL-2.0
2 obj-$(CONFIG_RAID6_PQ) += raid6_pq.o
4 raid6_pq-y += algos.o recov.o tables.o int1.o int2.o int4.o \
7 raid6_pq-$(CONFIG_X86) += recov_ssse3.o recov_avx2.o mmx.o sse1.o sse2.o avx2.o avx512.o recov_avx5…
8 raid6_pq-$(CONFIG_ALTIVEC) += altivec1.o altivec2.o altivec4.o altivec8.o \
10 raid6_pq-$(CONFIG_KERNEL_MODE_NEON) += neon.o neon1.o neon2.o neon4.o neon8.o recov_neon.o recov_ne…
11 raid6_pq-$(CONFIG_S390) += s390vx8.o recov_s390xc.o
16 altivec_flags := -maltivec $(call cc-option,-mabi=altivec)
19 # clang ppc port does not yet support -maltivec when -msoft-float is
22 CFLAGS_REMOVE_altivec1.o += -msoft-float
[all …]

123456789