| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| D | subdev-formats.rst | 1 .. 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 …]
|
| D | dev-subdev.rst | 1 .. 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 …]
|
| D | vidioc-subdev-enum-frame-size.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_ENUM_FRAME_SIZE - Enumerate media bus frame sizes
35 a sub-device on the given pad for the given media bus format. Supported
47 Sub-devices that only support discrete frame sizes (such as most
52 supported. For instance, a scaler that uses a fixed-point scaling ratio
56 sub-device for an exact supported frame size.
59 pads of the sub-device, as well as on the current active links and the
68 .. flat-table:: struct v4l2_subdev_frame_size_enum
69 :header-rows: 0
70 :stub-columns: 0
[all …]
|
| /Linux-v5.15/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 …]
|
| /Linux-v5.15/drivers/media/pci/bt8xx/ |
| D | bttv-gpio.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
4 bttv-gpio.c -- gpio sub drivers
6 sysfs-based sub driver interface for bttv
10 Copyright (C) 1996,97,98 Ralph Metzler (rjkm@thp.uni-koeln.de)
11 & Marcus Metzler (mocm@thp.uni-koeln.de)
12 (c) 1999-2003 Gerd Knorr <kraxel@bytesex.org>
28 /* ----------------------------------------------------------------------- */
29 /* internal: the bttv "bus" */
33 struct bttv_sub_driver *sub = to_bttv_sub_drv(drv); in bttv_sub_bus_match() local
34 int len = strlen(sub->wanted); in bttv_sub_bus_match()
[all …]
|
| /Linux-v5.15/include/media/ |
| D | v4l2-fwnode.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
8 * Copyright (C) 2012 - 2013 Samsung Electronics Co., Ltd.
22 #include <media/v4l2-mediabus.h>
31 * struct v4l2_fwnode_bus_mipi_csi2 - MIPI CSI-2 bus data structure
32 * @flags: media bus (V4L2_MBUS_*) flags
48 * struct v4l2_fwnode_bus_parallel - parallel data bus data structure
49 * @flags: media bus (V4L2_MBUS_*) flags
50 * @bus_width: bus width in bits
60 * struct v4l2_fwnode_bus_mipi_csi1 - CSI-1/CCP2 data bus structure
62 * false - not inverted, true - inverted
[all …]
|
| D | v4l2-subdev.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * V4L2 sub-device support header.
12 #include <linux/v4l2-subdev.h>
13 #include <media/media-entity.h>
14 #include <media/v4l2-async.h>
15 #include <media/v4l2-common.h>
16 #include <media/v4l2-dev.h>
17 #include <media/v4l2-fh.h>
18 #include <media/v4l2-mediabus.h>
43 * struct v4l2_decode_vbi_line - used to decode_vbi_line
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,q6v5.txt | 6 - compatible:
10 "qcom,q6v5-pil",
11 "qcom,ipq8074-wcss-pil"
12 "qcom,qcs404-wcss-pil"
13 "qcom,msm8916-mss-pil",
14 "qcom,msm8974-mss-pil"
15 "qcom,msm8996-mss-pil"
16 "qcom,msm8998-mss-pil"
17 "qcom,sc7180-mss-pil"
18 "qcom,sdm845-mss-pil"
[all …]
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | auxiliary_bus.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
6 Auxiliary Bus
14 export Virtual Function management). A split of the functionality into child-
15 devices representing sub-domains of functionality makes it possible to
16 compartmentalize, layer, and distribute domain-specific concerns via a Linux
17 device-driver model.
23 allows for the audio core device to be minimal and focused on hardware-specific
28 auxiliary_device within other domain-specific structures and the use of .ops
29 callbacks. Devices on the auxiliary bus do not share any structures and the use
30 of a communication channel with the parent is domain-specific.
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/devfreq/ |
| D | exynos-bus.txt | 1 * Generic Exynos Bus frequency device
4 and sub-blocks in SoC. Most Exynos SoCs share the common architecture
5 for buses. Generally, each bus of Exynos SoC includes a source clock
7 of the bus in runtime. To monitor the usage of each bus in runtime,
9 is able to measure the current load of sub-blocks.
11 The Exynos SoC includes the various sub-blocks which have the each AXI bus.
12 The each AXI bus has the owned source clock but, has not the only owned
13 power line. The power line might be shared among one more sub-blocks.
14 So, we can divide into two type of device as the role of each sub-block.
15 There are two type of bus devices as following:
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/leds/ |
| D | leds-netxbig.txt | 1 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 …]
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-bus-nfit | 5 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 …]
|
| D | configfs-most | 9 # 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 …]
|
| /Linux-v5.15/drivers/media/platform/am437x/ |
| D | am437x-vpfe.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copyright (C) 2013 - 2014 Texas Instruments, Inc.
12 #include <linux/am437x-vpfe.h>
20 #include <media/v4l2-dev.h>
21 #include <media/v4l2-device.h>
22 #include <media/v4l2-ioctl.h>
23 #include <media/videobuf2-v4l2.h>
24 #include <media/videobuf2-dma-contig.h>
26 #include "am437x-vpfe_regs.h"
36 /* BT656 - 8 bit */
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/pci/ |
| D | ralink,rt3883-pci.txt | 7 - 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 …]
|
| /Linux-v5.15/Documentation/usb/ |
| D | acm.rst | 23 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 …]
|
| /Linux-v5.15/Documentation/userspace-api/media/ |
| D | glossary.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
51 **Field-programmable Gate Array**
56 See https://en.wikipedia.org/wiki/Field-programmable_gate_array.
65 together make a larger user-facing functional peripheral. For
73 **Inter-Integrated Circuit**
75 A multi-master, multi-slave, packet switched, single-ended,
76 serial computer bus used to control some hardware components
77 like sub-device hardware components.
79 See http://www.nxp.com/docs/en/user-guide/UM10204.pdf.
113 - :term:`CEC API`;
[all …]
|
| /Linux-v5.15/include/media/davinci/ |
| D | vpfe_capture.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * Copyright (C) 2008-2009 Texas Instruments Inc
12 #include <media/v4l2-dev.h>
16 #include <media/v4l2-fh.h>
17 #include <media/v4l2-ioctl.h>
18 #include <media/v4l2-device.h>
19 #include <media/videobuf-dma-contig.h>
32 #define CAPTURE_DRV_NAME "vpfe-capture"
53 /* Sub device name */
55 /* Sub device group id */
[all …]
|
| /Linux-v5.15/drivers/gpu/drm/ |
| D | drm_dp_aux_bus.c | 1 // SPDX-License-Identifier: GPL-2.0
5 * The DP AUX bus is used for devices that are connected over a DisplayPort
6 * AUX bus. The devices on the far side of the bus are referred to as
9 * Commonly there is only one device connected to the DP AUX bus: a panel.
11 * platform devices, putting them under the DP AUX bus allows the panel driver
12 * to perform transactions on that bus.
26 * dp_aux_ep_match() - The match function for the dp_aux_bus.
36 return !!of_match_device(drv->of_match_table, dev); in dp_aux_ep_match()
40 * dp_aux_ep_probe() - The probe function for the dp_aux_bus.
49 struct dp_aux_ep_driver *aux_ep_drv = to_dp_aux_ep_drv(dev->driver); in dp_aux_ep_probe()
[all …]
|
| /Linux-v5.15/Documentation/driver-api/media/ |
| D | v4l2-subdev.rst | 1 .. 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 …]
|
| /Linux-v5.15/include/linux/mfd/ |
| D | rsmu.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
20 * struct rsmu_ddata - device data structure for sub devices.
23 * @regmap: i2c/spi bus access.
24 * @lock: mutex used by sub devices to make sure a series of
25 * bus access requests are not interrupted.
27 * @page: i2c/spi bus driver internal use only.
|
| /Linux-v5.15/drivers/staging/mt7621-pci/ |
| D | mediatek,mt7621-pci.txt | 4 - compatible: "mediatek,mt7621-pci"
5 - device_type: Must be "pci"
6 - reg: Base addresses and lengths of the PCIe subsys and root ports.
7 - bus-range: Range of bus numbers associated with this controller.
8 - #address-cells: Address representation for root ports (must be 3)
9 - pinctrl-names : The pin control state names.
10 - pinctrl-0: The "default" pinctrl state.
11 - #size-cells: Size representation for root ports (must be 2)
12 - ranges: Ranges for the PCI memory and I/O regions.
13 - #interrupt-cells: Must be 1
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 10 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 …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/mtd/ |
| D | gpio-control-nand.txt | 8 - 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 …]
|
| /Linux-v5.15/Documentation/driver-api/usb/ |
| D | usb.rst | 1 .. _usb-hostside-api:
4 The Linux-USB Host Side API
10 A Universal Serial Bus (USB) is used to connect a host, such as a PC or
18 That master/slave asymmetry was designed-in for a number of reasons, one
22 distributed auto-configuration since the pre-designated master node
37 USB Host-Side API Model
40 Host-side drivers for USB devices talk to the "usbcore" APIs. There are
41 two. One is intended for *general-purpose* drivers (exposed through
49 - USB supports four kinds of data transfers (control, bulk, interrupt,
54 - The device description model includes one or more "configurations"
[all …]
|
