Searched +full:non +full:- +full:compliant (Results 1 – 25 of 54) sorted by relevance
123
| /Documentation/driver-api/media/drivers/ccs/ |
| D | ccs.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause
5 .. _media-ccs-driver:
11 <https://www.mipi.org/specifications/camera-command-set>`_ compliant
14 Also see :ref:`the CCS driver UAPI documentation <media-ccs-uapi>`.
17 ---------------
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(++).
23 ccs/ccs-sensor-vvvv-mmmm-rrrr.fw (sensor) and
24 ccs/ccs-module-vvvv-mmmm-rrrr.fw (module).
26 For SMIA++ compliant devices the corresponding file names are
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-gpio.yaml | 1 # 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 …]
|
| /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 …]
|
| /Documentation/arch/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 …]
|
| /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 …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-spi-devices-spi-nor | 1 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
32 What: /sys/bus/spi/devices/.../spi-nor/sfdp
35 Contact: linux-mtd@lists.infradead.org
|
| /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 …]
|
| D | vesafb.rst | 20 * You can run XF68_FBDev on top of /dev/fb0 (=> non-accelerated X11
21 support for every VBE 2.0 compliant graphics board).
22 * Most important: boot logo :-)
33 Documentation/admin-guide/svga.rst for details.
81 "vga=mode-number" you have to transform the numbers to decimal.
88 XF68_FBDev should work just fine, but it is non-accelerated. Running
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
90 It depends on X-Server and graphics board.
92 The X-Server must restore the video mode correctly, else you end up
103 * configure and load the DOS-Tools for the graphics board (if
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-static-funnel.yaml | 1 # 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 …]
|
| D | arm,coresight-static-replicator.yaml | 1 # 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 …]
|
| D | arm,coresight-catu.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/arm/arm,coresight-catu.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
27 non-contiguous Physical Addresses (PAs) that are intended for system memory.
[all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | arm,scmi.yaml | 1 # 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>
26 - $ref: /schemas/firmware/nxp,imx95-scmi.yaml
34 - description: SCMI compliant firmware with mailbox transport
36 - const: arm,scmi
37 - description: SCMI compliant firmware with ARM SMC/HVC transport
39 - const: arm,scmi-smc
40 - description: SCMI compliant firmware with ARM SMC/HVC transport
[all …]
|
| D | arm,scpi.yaml | 1 # 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 …]
|
| /Documentation/hwmon/ |
| D | lineage-pem.rst | 1 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 …]
|
| D | pmbus-core.rst | 9 power-management protocol with a fully defined command language that facilitates
11 protocol is implemented over the industry-standard SMBus serial interface and
12 enables programming, control, and real-time monitoring of compliant power
18 promoted by the PMBus Implementers Forum (PMBus-IF), comprising 30+ adopters
22 commands, and manufacturers can add as many non-standard commands as they like.
23 Also, different PMBUs devices act differently if non-supported commands are
43 PMBus device capabilities auto-detection
46 For generic PMBus devices, code in pmbus.c attempts to auto-detect all supported
47 PMBus commands. Auto-detection is somewhat limited, since there are simply too
50 pages (see the PMBus specification for details on multi-page PMBus devices).
[all …]
|
| /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 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 …]
|
| /Documentation/arch/arm/ |
| D | uefi.rst | 7 maintained by the UEFI Forum - http://www.uefi.org/.
16 Booting on a platform with firmware compliant with the UEFI specification
19 - UEFI Runtime Services
20 - Retrieving various configuration information through the standardised
25 - CONFIG_EFI=y
26 - CONFIG_EFIVAR_FS=y or m
29 in a Flattened Device Tree (FDT) - so is only available with CONFIG_OF.
39 booting in non-UEFI environments.
55 linux,uefi-system-table 64-bit Physical address of the UEFI System Table.
57 linux,uefi-mmap-start 64-bit Physical address of the UEFI memory map,
[all …]
|
| D | kernel_mode_neon.rst | 6 -------------
10 '-march=armv7-a -mfpu=neon -mfloat-abi=softfp'
18 ------------
25 non-preemptible section for reasons outlined below.
29 -------------------------
50 ----------------------------
67 --------------------
69 like IEEE-754 compliant underflow handling etc. When the VFP unit needs such
80 ---------------------------------------
84 instructions of its own at -O3 level if -mfpu=neon is selected, and even if the
[all …]
|
| /Documentation/filesystems/ |
| D | overlayfs.rst | 1 .. 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 …]
|
| /Documentation/devicetree/bindings/dma/ti/ |
| D | k3-udma.yaml | 1 # 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 …]
|
| /Documentation/hid/ |
| D | hiddev.rst | 18 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 …]
|
| /Documentation/process/ |
| D | embargoed-hardware-issues.rst | 7 -----
23 -------
31 Linux kernel security team (:ref:`Documentation/admin-guide/
34 The team can be contacted by email at <hardware-security@kernel.org>. This
43 - PGP: https://www.kernel.org/static/files/hardware-security.asc
44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
55 - Linus Torvalds (Linux Foundation Fellow)
56 - Greg Kroah-Hartman (Linux Foundation Fellow)
57 - Thomas Gleixner (Linux Foundation Fellow)
59 Operation of mailing-lists
[all …]
|
| /Documentation/translations/it_IT/process/ |
| D | license-rules.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 .. include:: ../disclaimer-ita.rst
5 :Original: :ref:`Documentation/process/license-rules.rst <kernel_licensing>`
14 versione della licenza *GNU General Public License* (GPL-2.0), di cui una
15 copia è disponibile nel file LICENSES/preferred/GPL-2.0; a questo si
17 LICENSES/exceptions/Linux-syscall-note; tutto ciò è descritto nel file COPYING.
20 debba essere licenziato per far si che sia chiaro e non ambiguo. Questo non
25 devono essere compatibili con la GPL-2.0::
27 GPL-1.0+ : GNU General Public License v1.0 o successiva
28 GPL-2.0+ : GNU General Public License v2.0 o successiva
[all …]
|
| /Documentation/dev-tools/ |
| D | ktap.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 (KTAP) format is specified to extend and alter TAP to support these use-cases.
17 can have subtests), each of which can contain both diagnostic data -- e.g., log
18 lines -- and a final result. The test structure and results are
19 machine-readable, whereas the diagnostic data is unstructured and is there to
23 - Version lines
24 - Plan lines
25 - Test case result lines
26 - Diagnostic lines
35 -------------
[all …]
|
| /Documentation/leds/ |
| D | leds-class.rst | 8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
9 brightness support so will just be turned on for non-zero brightness settings.
14 existing subsystems with minimal additional code. Examples are the disk-activity,
15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
48 - devicename:
57 - color:
59 include/dt-bindings/leds/common.h.
61 - function:
63 include/dt-bindings/leds/common.h.
66 to linux-leds@vger.kernel.org.
[all …]
|
123