Home
last modified time | relevance | path

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

123456789

/Linux-v6.6/drivers/hid/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
22 most commonly used to refer to the USB-HID specification, but other
27 removed from the HID bus by the transport-layer drivers, such as
58 to work on raw hid events when they want to, and avoid using transport-specific
64 tristate "User-space I/O driver support for HID subsystem"
67 Say Y here if you want to provide HID I/O Drivers from user-space.
68 This allows to write I/O drivers in user-space and feed the data from
71 user-space device.
73 This driver cannot be used to parse HID-reports in user-space and write
74 special HID-drivers. You should use hidraw for that.
[all …]
/Linux-v6.6/include/linux/platform_data/
Di2c-gpio.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * i2c-gpio interface to platform code
11 * struct i2c_gpio_platform_data - Platform-dependent data for i2c-gpio
21 * @sda_has_no_pullup: SDA is used in a non-compliant way and has no pull-up.
22 * Therefore disable open-drain.
26 * @scl_has_no_pullup: SCL is used in a non-compliant way and has no pull-up.
27 * Therefore disable open-drain.
/Linux-v6.6/Documentation/driver-api/media/drivers/ccs/
Dccs.rst1 .. SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause
9 <https://www.mipi.org/specifications/camera-command-set>`_ compliant
10 camera sensors. It exposes three sub-devices representing the pixel array,
16 Pixel Array sub-device
17 ----------------------
19 The pixel array sub-device represents the camera sensor's pixel matrix, as well
20 as analogue crop functionality present in many compliant devices. The analogue
26 ------
28 The binner sub-device represents the binning functionality on the sensor. For
37 ------
[all …]
/Linux-v6.6/Documentation/arch/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-v6.6/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.
85 bool "Support 8-bit buswidth" if MTD_CFI_GEOMETRY
92 bool "Support 16-bit buswidth" if MTD_CFI_GEOMETRY
99 bool "Support 32-bit buswidth" if MTD_CFI_GEOMETRY
[all …]
/Linux-v6.6/Documentation/devicetree/bindings/i2c/
Di2c-gpio.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Wolfram Sang <wsa@kernel.org>
13 - $ref: /schemas/i2c/i2c-controller.yaml#
18 - const: i2c-gpio
20 sda-gpios:
24 from <dt-bindings/gpio/gpio.h> since the signal is by definition
28 scl-gpios:
[all …]
/Linux-v6.6/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-v6.6/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.3 Interface / TPM 2.0 FIFO Interface - (I2C - generic)"
83 If you have a TPM security chip, compliant with the TCG TPM PTP
90 tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface (MMIO - SynQuacer)"
94 If you have a TPM security chip that is compliant with the
102 tristate "TPM Interface Specification 2.0 Interface (I2C - CR50)"
[all …]
/Linux-v6.6/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-v6.6/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-v6.6/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-v6.6/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-v6.6/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-v6.6/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 */
68 int opened; /* open refcount; protect with chip->mutex */
131 bool lowlatency_playback; /* low-latency playback mode */
132 bool need_setup; /* (re-)need for hw_params? */
133 bool need_prepare; /* (re-)need for prepare? */
161 unsigned int txfr_quirk:1; /* allow sub-frame alignment */
163 unsigned int fmt_type; /* USB audio format type (1-3) */
164 …unsigned int pkt_offset_adj; /* Bytes to drop from beginning of packets (for non-compliant devices…
[all …]
/Linux-v6.6/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-v6.6/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-v6.6/Documentation/ABI/testing/
Dsysfs-bus-spi-devices-spi-nor1 What: /sys/bus/spi/devices/.../spi-nor/jedec_id
4 Contact: linux-mtd@lists.infradead.org
10 non-JEDEC compliant flashes.
12 What: /sys/bus/spi/devices/.../spi-nor/manufacturer
15 Contact: linux-mtd@lists.infradead.org
22 What: /sys/bus/spi/devices/.../spi-nor/partname
25 Contact: linux-mtd@lists.infradead.org
29 What: /sys/bus/spi/devices/.../spi-nor/sfdp
32 Contact: linux-mtd@lists.infradead.org
/Linux-v6.6/drivers/staging/media/deprecated/atmel/
DTODO1 The Atmel ISC driver is not compliant with media controller specification.
20 media-controller configurable, and will not propagate the formats down to
24 Atmel ISC to staging as-is, to keep the Kconfig symbols and the users
25 to the driver in staging. Thus, all the existing users of the non
26 media-controller paradigm will continue to be happy and use the old config
/Linux-v6.6/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-v6.6/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-v6.6/Documentation/devicetree/bindings/arm/
Darm,coresight-static-funnel.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/arm/arm,coresight-static-funnel.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Mathieu Poirier <mathieu.poirier@linaro.org>
11 - Mike Leach <mike.leach@linaro.org>
12 - Leo Yan <leo.yan@linaro.org>
13 - Suzuki K Poulose <suzuki.poulose@arm.com>
16 CoreSight components are compliant with the ARM CoreSight architecture
23 The Coresight static funnel merges 2-8 trace sources into a single trace
[all …]
Darm,coresight-static-replicator.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/arm/arm,coresight-static-replicator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Mathieu Poirier <mathieu.poirier@linaro.org>
11 - Mike Leach <mike.leach@linaro.org>
12 - Leo Yan <leo.yan@linaro.org>
13 - Suzuki K Poulose <suzuki.poulose@arm.com>
16 CoreSight components are compliant with the ARM CoreSight architecture
28 const: arm,coresight-static-replicator
[all …]
/Linux-v6.6/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-v6.6/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 …]

123456789