| /linux/drivers/media/pci/bt8xx/ |
| H A 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 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/Documentation/devicetree/bindings/interconnect/ |
| H A D | samsung,exynos-bus.yaml | 1 # 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 …]
|
| /linux/Documentation/devicetree/bindings/pci/ |
| H A D | snps,dw-pcie-common.yaml | 1 # 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 …]
|
| H A 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/Documentation/devicetree/bindings/leds/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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 …]
|
| H A 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/Documentation/userspace-api/media/ |
| H A D | glossary.rst | 1 .. 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/drivers/media/platform/ti/am437x/ |
| H A 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/Documentation/usb/ |
| H A 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/drivers/cdx/ |
| H A D | cdx.h | 1 /* 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/Documentation/userspace-api/media/v4l/ |
| H A 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 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 …]
|
| H A D | vidioc-subdev-enum-mbus-code.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_ENUM_MBUS_CODE - Enumerate media bus formats
35 of media bus formats for the selected pad.
42 Therefore, to enumerate media bus formats available at a given sub-device pad,
57 Available media bus formats may depend on the current 'try' formats at
58 other pads of the sub-device, as well as on the current active links.
66 .. flat-table:: struct v4l2_subdev_mbus_code_enum
67 :header-rows: 0
68 :stub-columns: 0
71 * - __u32
[all …]
|
| /linux/include/linux/mfd/ |
| H A D | rsmu.h | 1 /* 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/drivers/usb/core/ |
| H A D | devices.c | 1 // 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 <sailer@ife.ee.ethz.ch>
29 * into one page, only the device list for one bus.
32 * 2000-01-04: Thomas Sailer <sailer@ife.ee.ethz.ch>
34 * 2000-07-05: Ashley Montanaro <ashley@compsoc.man.ac.uk>
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/Documentation/driver-api/media/ |
| H A 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/Documentation/devicetree/bindings/remoteproc/ |
| H A D | ti,k3-r5f-rproc.yaml | 1 # 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-anna@ti.com>
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 …]
|
| H A D | ti,k3-dsp-rproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-dsp-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The TI K3 family of SoCs usually have one or more TI DSP Core sub-systems
14 that are used to offload some of the processor-intensive tasks or algorithms,
17 These processor sub-systems usually contain additional sub-modules like
23 Each DSP Core sub-system is represented as a single DT node. Each node has a
31 - ti,am62a-c7xv-dsp
[all …]
|
| /linux/Documentation/devicetree/bindings/reset/ |
| H A 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/Documentation/devicetree/bindings/mtd/ |
| H A 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/Documentation/ABI/stable/ |
| H A D | sysfs-bus-usb | 1 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 …]
|
| /linux/arch/mips/pci/ |
| H A D | pcie-octeon.c | 17 #include <asm/octeon/cvmx-npei-defs.h>
18 #include <asm/octeon/cvmx-pciercx-defs.h>
19 #include <asm/octeon/cvmx-pescx-defs.h>
20 #include <asm/octeon/cvmx-pexp-defs.h>
21 #include <asm/octeon/cvmx-pemx-defs.h>
22 #include <asm/octeon/cvmx-dpi-defs.h>
23 #include <asm/octeon/cvmx-sli-defs.h>
24 #include <asm/octeon/cvmx-sriox-defs.h>
25 #include <asm/octeon/cvmx-helper-errata.h>
26 #include <asm/octeon/pci-octeon.h>
[all …]
|
| /linux/arch/arm64/boot/dts/renesas/ |
| H A D | white-hawk-csi-dsi.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 * Device Tree Source for the White Hawk CSI/DSI sub-board
8 #include <dt-bindings/media/video-interfaces.h>
14 #address-cells = <1>;
15 #size-cells = <0>;
21 bus-type = <MEDIA_BUS_TYPE_CSI2_CPHY>;
22 clock-lanes = <0>;
23 data-lanes = <1 2 3>;
24 line-orders = <MEDIA_BUS_CSI2_CPHY_LINE_ORDER_ABC
27 remote-endpoint = <&max96712_out0>;
[all …]
|
| /linux/Documentation/devicetree/bindings/soc/dove/ |
| H A D | pmu.txt | 4 - 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 …]
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | img,pistachio-pinctrl.txt | 8 each. The GPIO banks are represented as sub-nodes of the pad controller node.
10 Please refer to pinctrl-bindings.txt, ../gpio/gpio.txt, and
11 ../interrupt-controller/interrupts.txt for generic information regarding
15 --------------------------------------------
16 - compatible: "img,pistachio-system-pinctrl".
17 - reg: Address range of the pinctrl registers.
19 Required properties for GPIO bank sub-nodes:
20 --------------------------------------------
21 - interrupts: Interrupt line for the GPIO bank.
22 - gpio-controller: Indicates the device is a GPIO controller.
[all …]
|