Home
last modified time | relevance | path

Searched +full:sub +full:- +full:bus (Results 1 – 25 of 177) sorted by relevance

12345678

/Documentation/userspace-api/media/v4l/
Dsubdev-formats.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _v4l2-mbus-format:
5 Media Bus Formats
14 .. flat-table:: struct v4l2_mbus_framefmt
15 :header-rows: 0
16 :stub-columns: 0
19 * - __u32
20 - ``width``
21 - Image width in pixels.
22 * - __u32
[all …]
Ddev-subdev.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
6 Sub-device Interface
13 components as software blocks called sub-devices.
15 V4L2 sub-devices are usually kernel-only objects. If the V4L2 driver
17 media entities. Applications will be able to enumerate the sub-devices
21 In addition to make sub-devices discoverable, drivers can also choose to
23 sub-device driver and the V4L2 device driver support this, sub-devices
26 - query, read and write sub-devices controls
28 - subscribe and unsubscribe to events and retrieve them
30 - negotiate image formats on individual pads
[all …]
Dvidioc-subdev-enum-frame-size.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_ENUM_FRAME_SIZE - Enumerate media bus frame sizes
35 supported by a sub-device on the specified pad
36 for the specified media bus format.
59 Sub-devices that only support discrete frame sizes (such as most
64 supported. For instance, a scaler that uses a fixed-point scaling ratio
68 sub-device for an exact supported frame size.
71 pads of the sub-device, as well as on the current active links and the
80 .. flat-table:: struct v4l2_subdev_frame_size_enum
81 :header-rows: 0
[all …]
Dselections-common.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _v4l2-selections-common:
8 While the :ref:`V4L2 selection API <selection-api>` and
9 :ref:`V4L2 subdev selection APIs <v4l2-subdev-selections>` are very
11 sub-device API, the selection rectangle refers to the media bus format,
12 and is bound to a sub-device's pad. On the V4L2 interface the selection
13 rectangles refer to the in-memory pixel format.
22 v4l2-selection-targets
23 v4l2-selection-flags
Dvidioc-subdev-enum-frame-interval.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL - Enumerate frame intervals
35 given sub-device pad. Frame intervals only makes sense for sub-devices
40 on the sub-device output pad depend on the frame format and size on the
54 other pads of the sub-device, as well as on the current active links.
58 Sub-devices that support the frame interval enumeration ioctl should
60 multiple pads of the same sub-device is not defined.
66 .. flat-table:: struct v4l2_subdev_frame_interval_enum
67 :header-rows: 0
68 :stub-columns: 0
[all …]
/Documentation/devicetree/bindings/dma/
Dadi,axi-dmac.txt1 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/leds/
Dleds-netxbig.txt1 Binding for the CPLD LEDs (GPIO extension bus) found on some LaCie/Seagate
5 - compatible: "lacie,netxbig-leds".
6 - gpio-ext: Phandle for the gpio-ext bus.
9 - timers: Timer array. Each timer entry is represented by three integers:
10 Mode (gpio-ext bus), delay_on and delay_off.
12 Each LED is represented as a sub-node of the netxbig-leds device.
14 Required sub-node properties:
15 - mode-addr: Mode register address on gpio-ext bus.
16 - mode-val: Mode to value mapping. Each entry is represented by two integers:
17 A mode and the corresponding value on the gpio-ext bus.
[all …]
Dleds-spi-byte.txt4 - one LED is controlled by a single byte on MOSI
5 - the value of the byte gives the brightness between two values (lowest to
7 - no return value is necessary (no MISO signal)
16 configured in a sub-node in the device node.
19 - compatible: should be one of
20 * "ubnt,acb-spi-led" microcontroller (SONiX 8F26E611LA) based device
23 Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt
26 LED sub-node properties:
27 - label:
29 - default-state:
[all …]
/Documentation/devicetree/bindings/interconnect/
Dsamsung,exynos-bus.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/interconnect/samsung,exynos-bus.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung Exynos SoC Bus and Interconnect
10 - Chanwoo Choi <cw00.choi@samsung.com>
11 - Krzysztof Kozlowski <krzk@kernel.org>
15 sub-blocks in SoC. Most Exynos SoCs share the common architecture for buses.
16 Generally, each bus of Exynos SoC includes a source clock and a power line,
17 which are able to change the clock frequency of the bus in runtime. To
[all …]
/Documentation/devicetree/bindings/pci/
Dsnps,dw-pcie-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
22 DWC PCIe CSR space is normally accessed over the dedicated Data Bus
23 Interface - DBI. In accordance with the reference manual the register
24 configuration space belongs to the Configuration-Dependent Module (CDM)
25 and is split up into several sub-parts Standard PCIe configuration
[all …]
Dralink,rt3883-pci.txt7 - compatible: must be "ralink,rt3883-pci"
9 - reg: specifies the physical base address of the controller and
12 - #address-cells: specifies the number of cells needed to encode an
15 - #size-cells: specifies the number of cells used to represent the size
18 - ranges: specifies the translation between child address space and parent
23 - status: indicates the operational status of the device.
28 The main node must have two child nodes which describes the built-in
35 - interrupt-controller: identifies the node as an interrupt controller
37 - #address-cells: specifies the number of cells needed to encode an
38 address. The value must be 0. As such, 'interrupt-map' nodes do not
[all …]
Daardvark-pci.txt8 - compatible: Should be "marvell,armada-3700-pcie"
9 - reg: range of registers for the PCIe controller
10 - interrupts: the interrupt line of the PCIe controller
11 - #address-cells: set to <3>
12 - #size-cells: set to <2>
13 - device_type: set to "pci"
14 - ranges: ranges for the PCI memory and I/O regions
15 - #interrupt-cells: set to <1>
16 - msi-controller: indicates that the PCIe controller can itself
18 - msi-parent: pointer to the MSI controller to be used
[all …]
/Documentation/userspace-api/media/
Dglossary.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
30 Unit of data transported by a bus. On parallel buses, the data unit
58 **Field-programmable Gate Array**
63 See https://en.wikipedia.org/wiki/Field-programmable_gate_array.
72 together make a larger user-facing functional peripheral. For
80 **Inter-Integrated Circuit**
82 A multi-master, multi-slave, packet switched, single-ended,
83 serial computer bus used to control some hardware components
84 like sub-device hardware components.
86 See http://www.nxp.com/docs/en/user-guide/UM10204.pdf.
[all …]
/Documentation/ABI/testing/
Dconfigfs-most9 # mount -t configfs none /sys/kernel/config/
22 configure the sub-buffer size for this channel
60 configuration, the creation is post-poned until
61 a physical device is being attached to the bus.
77 configure the sub-buffer size for this channel
115 configuration, the creation is post-poned until
116 a physical device is being attached to the bus.
132 configure the sub-buffer size for this channel
170 configuration, the creation is post-poned until
171 a physical device is being attached to the bus.
[all …]
Dsysfs-bus-nfit5 What: /sys/bus/nd/devices/nmemX/nfit/serial
10 (RO) Serial number of the NVDIMM (non-volatile dual in-line
14 What: /sys/bus/nd/devices/nmemX/nfit/handle
20 parent bus of the NVDIMM device containing the NVDIMM region.
23 What: /sys/bus/nd/devices/nmemX/nfit/device
31 What: /sys/bus/nd/devices/nmemX/nfit/rev_id
39 What: /sys/bus/nd/devices/nmemX/nfit/phys_id
49 What: /sys/bus/nd/devices/nmemX/nfit/flags
54 (RO) The flags in the NFIT memory device sub-structure indicate
66 What: /sys/bus/nd/devices/nmemX/nfit/format
[all …]
/Documentation/usb/
Dacm.rst23 Temple Place, Suite 330, Boston, MA 02111-1307 USA
25 Should you need to contact me, the author, you can do so either by e-mail -
34 The drivers/usb/class/cdc-acm.c drivers works with USB modems and USB ISDN terminal
35 adapters that conform to the Universal Serial Bus Communication Device Class
40 - 3Com OfficeConnect 56k
41 - 3Com Voice FaxModem Pro
42 - 3Com Sportster
43 - MultiTech MultiModem 56k
44 - Zoom 2986L FaxModem
45 - Compaq 56k FaxModem
[all …]
/Documentation/devicetree/bindings/mtd/
Dgpio-control-nand.txt8 - compatible : "gpio-control-nand"
9 - reg : should specify localbus chip select and size used for the chip. The
10 resource describes the data bus connected to the NAND flash and all accesses
12 - #address-cells, #size-cells : Must be present if the device has sub-nodes
14 - gpios : Specifies the GPIO pins to control the NAND device. The order of
18 - bank-width : Width (in bytes) of the device. If not present, the width
20 - chip-delay : chip dependent delay for transferring data from array to
22 - gpio-control-nand,io-sync-reg : A 64-bit physical address for a read
23 location used to guard against bus reordering with regards to accesses to
24 the GPIO's and the NAND flash data bus. If present, then after changing
[all …]
Dflctl-nand.txt4 - compatible : "renesas,shmobile-flctl-sh7372"
5 - reg : Address range of the FLCTL
6 - interrupts : flste IRQ number
7 - nand-bus-width : bus width to NAND chip
10 - dmas: DMA specifier(s)
11 - dma-names: name for each DMA specifier. Valid names are
17 The device tree may optionally contain sub-nodes describing partitions of the
23 #address-cells = <1>;
24 #size-cells = <1>;
25 compatible = "renesas,shmobile-flctl-sh7372";
[all …]
/Documentation/devicetree/bindings/rng/
Dsamsung,exynos5250-trng.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/rng/samsung,exynos5250-trng.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
11 - Łukasz Stelmach <l.stelmach@samsung.com>
16 - samsung,exynos5250-trng
17 - samsung,exynos850-trng
23 clock-names:
31 - compatible
[all …]
/Documentation/devicetree/bindings/reset/
Dreset.txt10 reset consumer (the module being reset, or a module managing when a sub-
15 specifier - a list of DT cells that represents the reset signal within the
25 where it makes most sense to control it; this may be a bus node if all
26 children of the bus are affected by the reset signal, or an individual HW
35 #reset-cells: Number of cells in a reset specifier; Typically 0 for nodes
41 rst: reset-controller {
42 #reset-cells = <1>;
51 #reset-cells, then only the phandle portion of the pair will
55 reset-names: List of reset signal name strings sorted in the same order as
56 the resets property. Consumers drivers will use reset-names to
[all …]
/Documentation/devicetree/bindings/soc/dove/
Dpmu.txt4 - compatible: value should be "marvell,dove-pmu".
5 May also include "simple-bus" if there are child devices, in which
7 - reg: two base addresses and sizes of the PM controller and PMU.
8 - interrupts: single interrupt number for the PMU interrupt
9 - interrupt-controller: must be specified as the PMU itself is an
11 - #interrupt-cells: must be 1.
12 - #reset-cells: must be 1.
13 - domains: sub-node containing domain descriptions
16 - ranges: defines the address mapping for child devices, as per the
18 "simple-bus".
[all …]
/Documentation/devicetree/bindings/sound/
Dst,stm32-sai.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/st,stm32-sai.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Olivier Moysan <olivier.moysan@foss.st.com>
14 protocols as I2S standards, LSB or MSB-justified, PCM/DSP, TDM, and AC'97.
15 The SAI contains two independent audio sub-blocks. Each sub-block has
21 - st,stm32f4-sai
22 - st,stm32h7-sai
26 - description: Base address and size of SAI common register set.
[all …]
/Documentation/driver-api/media/
Dv4l2-subdev.rst1 .. SPDX-License-Identifier: GPL-2.0
3 V4L2 sub-devices
4 ----------------
6 Many drivers need to communicate with sub-devices. These devices can do all
8 encoding or decoding. For webcams common sub-devices are sensors and camera
12 driver with a consistent interface to these sub-devices the
13 :c:type:`v4l2_subdev` struct (v4l2-subdev.h) was created.
15 Each sub-device driver must have a :c:type:`v4l2_subdev` struct. This struct
16 can be stand-alone for simple sub-devices or it might be embedded in a larger
18 low-level device struct (e.g. ``i2c_client``) that contains the device data as
[all …]
/Documentation/devicetree/bindings/w1/
Dw1.txt4 Onewire busses are described through nodes of their master bus controller.
5 Slave devices are listed as sub-nodes of such master devices. For now, only
6 one slave is allowed per bus master.
12 compatible = "gpio-charger";
13 charger-type = "mains";
18 compatible = "w1-gpio";
23 power-supplies = <&charger>;
/Documentation/ABI/stable/
Dsysfs-bus-usb1 What: /sys/bus/usb/devices/.../power/persist
8 not the "USB-Persist" facility is enabled for the device. For
12 For more information, see Documentation/driver-api/usb/persist.rst.
14 What: /sys/bus/usb/devices/.../power/autosuspend
27 The autosuspend delay for newly-created devices is set to
30 What: /sys/bus/usb/device/.../power/connected_duration
37 connected to the machine. This file is read-only.
42 What: /sys/bus/usb/device/.../power/active_duration
49 active, i.e. not in a suspended state. This file is read-only.
63 What: /sys/bus/usb/devices/<busnum>-<port[.port]>...:<config num>-<interface num>/supports_autosus…
[all …]

12345678