Searched +full:interface +full:- +full:node (Results 1 – 25 of 451) sorted by relevance
12345678910>>...19
| /Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | gamecube.txt | 5 1) The "flipper" node
7 This node represents the multi-function "Flipper" chip, which packages
12 - compatible : Should be "nintendo,flipper"
14 1.a) The Video Interface (VI) node
16 Represents the interface between the graphics processor and a external
21 - compatible : should be "nintendo,flipper-vi"
22 - reg : should contain the VI registers location and length
23 - interrupts : should contain the VI interrupt
25 1.b) The Processor Interface (PI) node
27 Represents the data and control interface between the main processor
[all …]
|
| D | wii.txt | 5 0) The root node
7 This node represents the Nintendo Wii video game console.
11 - model : Should be "nintendo,wii"
12 - compatible : Should be "nintendo,wii"
14 1) The "hollywood" node
16 This node represents the multi-function "Hollywood" chip, which packages
21 - compatible : Should be "nintendo,hollywood"
23 1.a) The Video Interface (VI) node
25 Represents the interface between the graphics processor and a external
30 - compatible : should be "nintendo,hollywood-vi","nintendo,flipper-vi"
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-device.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/usb-device.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
15 http://www.devicetree.org/open-firmware/bindings/usb/usb-1_0.ps
17 Four types of device-tree nodes are defined: "host-controller nodes"
19 "interface nodes" representing USB interfaces and "combined nodes"
22 A combined node shall be used instead of a device node and an interface node
24 interface.
[all …]
|
| D | omap-usb.txt | 4 - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
5 - ti,hwmods : must be "usb_otg_hs"
6 - multipoint : Should be "1" indicating the musb controller supports
7 multipoint. This is a MUSB configuration-specific setting.
8 - num-eps : Specifies the number of endpoints. This is also a
9 MUSB configuration-specific setting. Should be set to "16"
10 - ram-bits : Specifies the ram address size. Should be set to "12"
11 - interface-type : This is a board specific setting to describe the type of
12 interface between the controller and the phy. It should be "0" or "1"
14 - mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
[all …]
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | akebono.txt | 7 0) The root node
11 - model : "ibm,akebono".
12 - compatible : "ibm,akebono" , "ibm,476gtr".
14 1.a) The Secure Digital Host Controller Interface (SDHCI) node
20 - compatible : should be "ibm,476gtr-sdhci","generic-sdhci".
21 - reg : should contain the SDHCI registers location and length.
22 - interrupts : should contain the SDHCI interrupt.
24 1.b) The Advanced Host Controller Interface (AHCI) SATA node
26 Represents the advanced host controller SATA interface.
30 - compatible : should be "ibm,476gtr-ahci".
[all …]
|
| /Documentation/admin-guide/media/ |
| D | fimc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
11 SoC Application Processors is an integrated camera host interface, color
17 drivers/media/platform/samsung/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-types.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _media-controller-types:
10 .. _media-entity-functions:
11 .. _MEDIA-ENT-F-UNKNOWN:
12 .. _MEDIA-ENT-F-V4L2-SUBDEV-UNKNOWN:
13 .. _MEDIA-ENT-F-IO-V4L:
14 .. _MEDIA-ENT-F-IO-VBI:
15 .. _MEDIA-ENT-F-IO-SWRADIO:
16 .. _MEDIA-ENT-F-IO-DTV:
17 .. _MEDIA-ENT-F-DTV-DEMOD:
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | ti-am437x-vpfe.txt | 2 --------------------------------------
5 applications. The capture module provides the system interface and the
6 processing capability to connect RAW image-sensor modules and video decoders
10 - compatible: must be "ti,am437x-vpfe"
11 - reg: physical base address and length of the registers set for the device;
12 - interrupts: should contain IRQ line for the VPFE;
13 - ti,am437x-vpfe-interface: can be one of the following,
14 0 - Raw Bayer Interface.
15 1 - 8 Bit BT656 Interface.
16 2 - 10 Bit BT656 Interface.
[all …]
|
| D | cdns,csi2rx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Cadence MIPI-CSI2 RX controller
10 - Maxime Ripard <mripard@kernel.org>
13 The Cadence MIPI-CSI2 RX controller is a CSI-2 bridge supporting up to 4 CSI
19 - enum:
20 - starfive,jh7110-csi2rx
21 - ti,j721e-csi2rx
22 - const: cdns,csi2rx
[all …]
|
| D | microchip,csi2dc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Eugen Hristev <eugen.hristev@microchip.com>
13 CSI2DC - Camera Serial Interface 2 Demux Controller
16 IDI interface or from a parallel bus interface.
19 clock domain towards a parallel interface that can be read by a sensor
21 IDI interface is Synopsys proprietary.
23 a parallel interface.
29 CSI2DC supports a single 'port' node as a sink port with either Synopsys
[all …]
|
| D | imx.txt | 4 Video Media Controller node
5 ---------------------------
7 This is the media controller node for video capture support. It is a
8 virtual device that lists the camera serial interface nodes that the
12 - compatible : "fsl,imx-capture-subsystem";
13 - ports : Should contain a list of phandles pointing to camera
14 sensor interface ports of IPU devices
18 capture-subsystem {
19 compatible = "fsl,imx-capture-subsystem";
24 mipi_csi2 node
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | adi,axi-dmac.txt | 1 Analog Devices AXI-DMAC DMA controller
4 - compatible: Must be "adi,axi-dmac-1.00.a".
5 - reg: Specification for the controllers memory mapped register map.
6 - interrupts: Specification for the controllers interrupt.
7 - clocks: Phandle and specifier to the controllers AXI interface clock
8 - #dma-cells: Must be 1.
10 Required sub-nodes:
11 - adi,channels: This sub-node must contain a sub-node for each DMA channel. For
12 the channel sub-nodes the following bindings apply. They must match the
15 Required properties for adi,channels sub-node:
[all …]
|
| /Documentation/devicetree/bindings/display/ |
| D | multi-inno,mi0283qt.txt | 1 Multi-Inno MI0283QT display panel
4 - compatible: "multi-inno,mi0283qt".
6 The node for this driver must be a child node of a SPI controller, hence
7 all mandatory properties described in ../spi/spi-bus.txt must be specified.
10 - dc-gpios: D/C pin. The presence/absence of this GPIO determines
11 the panel interface mode (IM[3:0] pins):
12 - present: IM=x110 4-wire 8-bit data serial interface
13 - absent: IM=x101 3-wire 9-bit data serial interface
14 - reset-gpios: Reset pin
15 - power-supply: A regulator node for the supply voltage.
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,versatile.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 The ARM Versatile boards are two variants of ARM926EJ-S evaluation boards
14 with various pluggable interface boards, in essence the Versatile PB version
17 The root node in the Versatile platforms must contain a core module child
18 node. They are always at physical address 0x10000000 in all the Versatile
21 When fitted with the IB2 Interface Board, the Versatile AB will present an
22 optional system controller node which controls the extra peripherals on the
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | zii,rave-sp.txt | 4 expected that its Device Tree node is specified as a child of a node
9 - compatible: Should be one of:
10 - "zii,rave-sp-niu"
11 - "zii,rave-sp-mezz"
12 - "zii,rave-sp-esb"
13 - "zii,rave-sp-rdu1"
14 - "zii,rave-sp-rdu2"
16 - current-speed: Should be set to baud rate SP device is using
18 RAVE SP consists of the following sub-devices:
21 ------ -----------
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | atmel-hsmci.txt | 1 * Atmel High Speed MultiMedia Card Interface
3 This controller on atmel products provides an interface for MMC, SD and SDIO
7 by mmc.txt and the properties used by the atmel-mci driver.
9 1) MCI node
12 - compatible: should be "atmel,hsmci"
13 - #address-cells: should be one. The cell is the slot id.
14 - #size-cells: should be zero.
15 - at least one slot node
16 - clock-names: tuple listing input clock names.
18 - clocks: phandles to input clocks.
[all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | mt9m001.txt | 1 MT9M001: 1/2-Inch Megapixel Digital Image Sensor
3 The MT9M001 is an SXGA-format with a 1/2-inch CMOS active-pixel digital
4 image sensor. It is programmable through I2C interface.
8 - compatible: shall be "onnn,mt9m001".
9 - clocks: reference to the master clock into sensor
13 - reset-gpios: GPIO handle which is connected to the reset pin of the chip.
15 - standby-gpios: GPIO handle which is connected to the standby pin of the chip.
18 The device node must contain one 'port' child node with one 'endpoint' child
19 sub-node for its digital output video port, in accordance with the video
20 interface bindings defined in:
[all …]
|
| D | mt9m111.txt | 4 array size of 1280H x 1024V. It is programmable through a simple two-wire serial
5 interface.
8 - compatible: value should be "micron,mt9m111"
9 - clocks: reference to the master clock.
10 - clock-names: shall be "mclk".
12 The device node must contain one 'port' child node with one 'endpoint' child
13 sub-node for its digital output video port, in accordance with the video
14 interface bindings defined in:
15 Documentation/devicetree/bindings/media/video-interfaces.txt
18 - pclk-sample: For information see ../video-interfaces.txt. The value is set to
[all …]
|
| /Documentation/hwmon/ |
| D | scpi-hwmon.rst | 1 Kernel driver scpi-hwmon
6 * Chips based on ARM System Control Processor Interface
8 Addresses scanned: -
15 -----------
19 Processor Interface (SCPI). The following sensor types are supported
27 The SCP interface provides an API to query the available sensors and
31 -----------
33 The driver relies on device tree node to indicate the presence of SCPI
36 devicetree node.
|
| /Documentation/devicetree/bindings/firmware/xilinx/ |
| D | xlnx,zynqmp-firmware.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nava kishore Manne <nava.kishore.manne@amd.com>
12 description: The zynqmp-firmware node describes the interface to platform
13 firmware. ZynqMP has an interface to communicate with secure firmware.
14 Firmware driver provides an interface to firmware APIs. Interface APIs
23 - description: For implementations complying for Zynq Ultrascale+ MPSoC.
24 const: xlnx,zynqmp-firmware
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-mempolicy-weighted-interleave | 3 Contact: Linux memory management mailing list <linux-mm@kvack.org>
4 Description: Configuration Interface for the Weighted Interleave policy
8 Contact: Linux memory management mailing list <linux-mm@kvack.org>
9 Description: Weight configuration interface for nodeN
11 The interleave weight for a memory node (N). These weights are
18 The minimum weight for a node is always 1.
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | sdei.txt | 1 * Software Delegated Exception Interface (SDEI)
4 ARM DEN 0054A ("Software Delegated Exception Interface") can be used by
6 firmware-first error handling, or from an IRQ that has been promoted to
7 a firmware-assisted NMI.
9 The interface provides a number of API functions for registering callbacks
15 r0 => 32-bit Function ID / return value
16 {r1 - r3} => Parameters
24 The sdei node should be a child node of '/firmware' and have required
27 - compatible : should contain:
28 * "arm,sdei-1.0" : For implementations complying to SDEI version 1.x.
[all …]
|
| /Documentation/devicetree/bindings/ata/ |
| D | intel,ixp4xx-compact-flash.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/ata/intel,ixp4xx-compact-flash.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 The IXP4xx network processors have a CompactFlash interface that presents
17 node must be placed inside a chip select node on the IXP4xx expansion bus.
21 const: intel,ixp4xx-compact-flash
25 - description: Command interface registers
26 - description: Control interface registers
[all …]
|
| /Documentation/firmware-guide/acpi/dsd/ |
| D | graph.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 _DSD (Device Specific Data) [dsd-guide] is a predefined ACPI device
14 for graphs: property [dsd-guide] and hierarchical data extensions. The
15 property extension provides generic key-value pairs whereas the
19 a tree-like structure with zero or more properties (key-value pairs)
20 in each node of the tree.
25 Fwnode represents a generic firmware node object. It is independent on
39 [devicetree, graph-bindings]. A port represents an interface in a device, and
40 an endpoint represents a connection to that interface. Also see [data-node-ref]
41 for generic data node references.
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | sysfs.rst | 1 GPIO Sysfs Interface for Userspace
6 been moved to Documentation/ABI/obsolete/sysfs-gpio.
12 This interface will continue to be maintained for the migration period,
16 ----------------------
18 configure a sysfs user interface to GPIOs. This is different from the
19 debugfs interface, since it provides control over GPIO direction and
27 then changing its output state, then updating the code before re-enabling
38 Please read Documentation/driver-api/gpio/drivers-on-gpio.rst
44 --------------
47 - Control interfaces used to get userspace control over GPIOs;
[all …]
|
12345678910>>...19