Home
last modified time | relevance | path

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

12345678910>>...27

/linux-6.14.4/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 …]
/linux-6.14.4/drivers/media/pci/bt8xx/
Dbttv-gpio.c1 // 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 ([email protected]-koeln.de)
11 & Marcus Metzler ([email protected]-koeln.de)
12 (c) 1999-2003 Gerd Knorr <[email protected]>
28 /* ----------------------------------------------------------------------- */
29 /* internal: the bttv "bus" */
33 const 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-6.14.4/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 <[email protected]>
11 - Krzysztof Kozlowski <[email protected]>
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 …]
/linux-6.14.4/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 <[email protected]>
11 - Gustavo Pimentel <[email protected]>
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 …]
/linux-6.14.4/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 …]
/linux-6.14.4/drivers/gpu/drm/display/
Ddrm_dp_aux_bus.c1 // 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 device on the far side of the bus is referred to as an
9 * There is only one device connected to the DP AUX bus: an eDP panel.
11 * platform devices, putting them under the DP AUX bus allows the panel driver
12 * to perform transactions on that bus.
31 * dp_aux_ep_match() - The match function for the dp_aux_bus.
41 return !!of_match_device(drv->of_match_table, dev); in dp_aux_ep_match()
45 * dp_aux_ep_probe() - The probe function for the dp_aux_bus.
54 struct dp_aux_ep_driver *aux_ep_drv = to_dp_aux_ep_drv(dev->driver); in dp_aux_ep_probe()
[all …]
/linux-6.14.4/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 …]
/linux-6.14.4/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 <[email protected]>
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
23 - st,stm32mp25-sai
[all …]
/linux-6.14.4/Documentation/ABI/testing/
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 …]
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 …]
/linux-6.14.4/drivers/media/platform/ti/am437x/
Dam437x-vpfe.h1 /* 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-6.14.4/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 …]
/linux-6.14.4/drivers/base/
Dauxiliary.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (c) 2019-2020 Intel Corporation
5 * Please see Documentation/driver-api/auxiliary_bus.rst for more information.
28 * Virtual Function management). A split of the functionality into child-
29 * devices representing sub-domains of functionality makes it possible to
30 * compartmentalize, layer, and distribute domain-specific concerns via a Linux
31 * device-driver model.
38 * and focused on hardware-specific control and communication.
42 * an auxiliary_device within other domain-specific structures and the use of
43 * .ops callbacks. Devices on the auxiliary bus do not share any structures and
[all …]
/linux-6.14.4/drivers/cdx/
Dcdx.h1 /* SPDX-License-Identifier: GPL-2.0
3 * Header file for the CDX Bus
5 * Copyright (C) 2022-2023, Advanced Micro Devices, Inc.
14 * struct cdx_dev_params - CDX device parameters
16 * @parent: Associated CDX Bus device
19 * @subsys_vendor: Sub vendor ID for CDX device
20 * @subsys_device: Sub device ID for CDX device
21 * @bus_num: Bus number for this CDX device
50 * cdx_register_controller - Register a CDX controller and its ports
51 * on the CDX bus.
[all …]
/linux-6.14.4/include/linux/mfd/
Drsmu.h1 /* SPDX-License-Identifier: GPL-2.0+ */
23 * struct rsmu_ddata - device data structure for sub devices.
26 * @regmap: i2c/spi bus access.
27 * @lock: mutex used by sub devices to make sure a series of
28 * bus access requests are not interrupted.
30 * @page: i2c/spi bus driver internal use only.
/linux-6.14.4/Documentation/devicetree/bindings/dma/
Dadi,axi-dmac.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/adi,axi-dmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Analog Devices AXI-DMAC DMA controller
10 FPGA-based DMA controller designed for use with high-speed converter hardware.
15 - Nuno Sa <[email protected]>
21 const: adi,axi-dmac-1.00.a
32 "#dma-cells":
39 This sub-node must contain a sub-node for each DMA channel. This node is
[all …]
/linux-6.14.4/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 …]
/linux-6.14.4/include/media/
Dv4l2-subdev.h1 /* 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>
44 * struct v4l2_decode_vbi_line - used to decode_vbi_line
[all …]
/linux-6.14.4/drivers/usb/core/
Ddevices.c1 // SPDX-License-Identifier: GPL-2.0+
14 * I considered using /dev/bus/usb/device# for each device
16 * reason -- maybe it's just too deep of a directory structure.
24 * this in any plug-and-play environment.)
26 * 1999-12-16: Thomas Sailer <[email protected]>
29 * into one page, only the device list for one bus.
32 * 2000-01-04: Thomas Sailer <[email protected]>
34 * 2000-07-05: Ashley Montanaro <[email protected]>
36 * per device, not per bus
54 /* T: Bus=dd Lev=dd Prnt=dd Port=dd Cnt=dd Dev#=ddd Spd=dddd MxCh=dd */
[all …]
/linux-6.14.4/Documentation/driver-api/usb/
Dusb.rst1 .. _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 …]
/linux-6.14.4/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 …]
/linux-6.14.4/Documentation/devicetree/bindings/remoteproc/
Dti,k3-r5f-rproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-r5f-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-[email protected]>
13 The TI K3 family of SoCs usually have one or more dual-core Arm Cortex R5F
20 AM64x SoCs do not support LockStep mode, but rather a new non-safety mode
21 called "Single-CPU" mode, where only Core0 is used, but with ability to use
27 Each Dual-Core R5F sub-system is represented as a single DTS node
40 - ti,am62-r5fss
[all …]

12345678910>>...27