Home
last modified time | relevance | path

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

12345678910>>...12

/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 …]
Dv4l2-device.rst1 .. SPDX-License-Identifier: GPL-2.0
4 --------------------
13 (dev, :c:type:`v4l2_dev <v4l2_device>`).
15 Registration will initialize the :c:type:`v4l2_device` struct. If the
16 dev->driver_data field is ``NULL``, it will be linked to
17 :c:type:`v4l2_dev <v4l2_device>` argument.
20 dev->driver_data manually to point to the driver-specific device structure
24 properly initialized and registered :c:type:`media_device` instance.
26 If :c:type:`v4l2_dev <v4l2_device>`\ ->name is empty then it will be set to a
30 :c:type:`v4l2_dev <v4l2_device>`\ ->name before calling
[all …]
/Documentation/userspace-api/netlink/
Dnetlink-raw.rst1 .. SPDX-License-Identifier: BSD-3-Clause
8 families such as ``NETLINK_ROUTE`` which use the ``netlink-raw`` protocol
14 The netlink-raw schema extends the :doc:`genetlink-legacy <genetlink-legacy>`
17 information. The raw netlink families also make use of type-specific
18 sub-messages.
21 -------
29 .. code-block:: yaml
31 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
33 name: rt-addr
34 protocol: netlink-raw
[all …]
Dgenetlink-legacy.rst1 .. SPDX-License-Identifier: BSD-3-Clause
9 the ``genetlink-legacy`` protocol level.
15 -------
28 Attribute type nests
29 --------------------
31 New Netlink families should use ``multi-attr`` to define arrays.
33 define array types reusing attribute type to carry information.
35 For reference the ``multi-attr`` array may look like this::
37 [ARRAY-ATTR]
41 [SOME-OTHER-ATTR]
[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/netlink/
Dnetlink-raw.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/netlink-raw.yaml#
5 $schema: https://json-schema.org/draft-07/schema
10 type: integer
12 len-or-define:
13 type: [ string, integer ]
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
20 type: object
21 required: [ name, doc, attribute-sets, operations ]
[all …]
/Documentation/userspace-api/media/v4l/
Dvidioc-subdev-querycap.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_QUERYCAP - Query sub-device capabilities
29 Pointer to struct :c:type:`v4l2_subdev_capability`.
34 All V4L2 sub-devices support the ``VIDIOC_SUBDEV_QUERYCAP`` ioctl. It is used to
37 a struct :c:type:`v4l2_subdev_capability` which is filled by the driver. When
43 .. c:type:: v4l2_subdev_capability
45 .. flat-table:: struct v4l2_subdev_capability
46 :header-rows: 0
47 :stub-columns: 0
50 * - __u32
[all …]
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
29 Pointer to struct :c:type:`v4l2_subdev_frame_interval_enum`.
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
46 :c:type:`v4l2_subdev_frame_interval_enum`
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.
62 .. c:type:: v4l2_subdev_frame_interval_enum
[all …]
Dvidioc-subdev-g-fmt.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_G_FMT - VIDIOC_SUBDEV_S_FMT - Get or set the data format on a subdev pad
33 Pointer to struct :c:type:`v4l2_subdev_format`.
42 struct :c:type:`v4l2_subdev_format` to the desired
53 :c:type:`v4l2_subdev_format` contains the current
59 and stored in the sub-device file handle. Two applications querying the
60 same sub-device would thus not interact with each other.
62 For instance, to try a format at the output pad of a sub-device,
63 applications would first set the try format at the sub-device input with
70 current links configuration or sub-device controls value. For instance,
[all …]
Dvidioc-dbg-g-register.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_DBG_G_REGISTER - VIDIOC_DBG_S_REGISTER - Read or write hardware registers
33 Pointer to struct :c:type:`v4l2_dbg_register`.
53 :c:type:`v4l2_dbg_register` except for ``size`` and
55 ``match.type`` and ``match.addr`` or ``match.name`` fields select a chip
59 To read a register applications must initialize the ``match.type``,
65 When ``match.type`` is ``V4L2_CHIP_MATCH_BRIDGE``, ``match.addr``
66 selects the nth non-sub-device chip on the TV card. The number zero
71 When ``match.type`` is ``V4L2_CHIP_MATCH_SUBDEV``, ``match.addr``
72 selects the nth sub-device.
[all …]
Dvidioc-dbg-g-chip-info.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_DBG_G_CHIP_INFO - Identify the chips on a TV card
29 Pointer to struct :c:type:`v4l2_dbg_chip_info`.
42 contact the linux-media mailing list
49 To query the driver applications must initialize the ``match.type`` and
51 :c:type:`v4l2_dbg_chip_info` and call
56 When ``match.type`` is ``V4L2_CHIP_MATCH_BRIDGE``, ``match.addr``
61 the PCI or USB bus. Non-zero numbers identify specific parts of the
64 When ``match.type`` is ``V4L2_CHIP_MATCH_SUBDEV``, ``match.addr``
65 selects the nth sub-device. This allows you to enumerate over all
[all …]
Dvidioc-subdev-g-frame-interval.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_G_FRAME_INTERVAL - VIDIOC_SUBDEV_S_FRAME_INTERVAL - Get or set the frame interval on …
33 Pointer to struct :c:type:`v4l2_subdev_frame_interval`.
40 for sub-devices that can control the frame period on their own. This
41 includes, for instance, image sensors and TV tuners. Sub-devices that
46 :c:type:`v4l2_subdev_frame_interval` to
57 :c:type:`v4l2_subdev_frame_interval`
61 If the subdev device node has been registered in read-only mode, calls to
64 variable is set to ``-EPERM``.
74 Sub-devices that support the frame interval ioctls should implement them
[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
29 Pointer to struct :c:type:`v4l2_subdev_frame_size_enum`.
35 supported by a sub-device on the specified pad
42 of the struct :c:type:`v4l2_subdev_frame_size_enum`.
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
76 .. c:type:: v4l2_subdev_frame_size_enum
[all …]
Dsubdev-formats.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _v4l2-mbus-format:
8 .. c:type:: v4l2_mbus_framefmt
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 …]
/Documentation/devicetree/bindings/powerpc/fsl/
Dsrio-rmu.txt5 node is composed of three types of sub-nodes ("fsl-srio-msg-unit",
6 "fsl-srio-dbell-unit" and "fsl-srio-port-write-unit").
10 - compatible
12 Value type: <string>
13 Definition: Must include "fsl,srio-rmu-vX.Y", "fsl,srio-rmu".
18 - reg
20 Value type: <prop-encoded-array>
25 - fsl,liodn
26 Usage: optional-but-recommended (for devices with PAMU)
27 Value type: <prop-encoded-array>
[all …]
/Documentation/devicetree/bindings/remoteproc/
Dqcom,q6v5.txt6 - compatible:
8 Value type: <string>
10 "qcom,ipq8074-wcss-pil"
11 "qcom,qcs404-wcss-pil"
13 - reg:
15 Value type: <prop-encoded-array>
19 - reg-names:
21 Value type: <stringlist>
24 - interrupts-extended:
26 Value type: <prop-encoded-array>
[all …]
/Documentation/ABI/testing/
Dconfigfs-most9 # mount -t configfs none /sys/kernel/config/
22 configure the sub-buffer size for this channel
31 configure type of data that will travel over
60 configuration, the creation is post-poned until
77 configure the sub-buffer size for this channel
86 configure type of data that will travel over
115 configuration, the creation is post-poned until
132 configure the sub-buffer size for this channel
141 configure type of data that will travel over
170 configuration, the creation is post-poned until
[all …]
Dsysfs-kernel-iommu_groups5 Description: /sys/kernel/iommu_groups/ contains a number of sub-
7 name of the sub-directory matches the iommu_group_id()
23 output direct-mapped, MSI, non mappable regions. Each
26 field describes the type of the region.
29 USB devices it is now exposed as "direct-relaxable" instead
33 What: /sys/kernel/iommu_groups/<grp_id>/type
37 Description: /sys/kernel/iommu_groups/<grp_id>/type shows the type of default
40 change the group type by writing to this file. Valid write values:
45 DMA-FQ As above, but using batched invalidation to lazily
51 auto Change to the type the device was booted with.
[all …]
/Documentation/devicetree/bindings/sound/
Dsamsung,midas-audio.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/samsung,midas-audio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sylwester Nawrocki <s.nawrocki@samsung.com>
13 - $ref: sound-card-common.yaml#
17 const: samsung,midas-audio
20 type: object
23 sound-dai:
27 - sound-dai
[all …]
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/firmware-guide/acpi/
DDSD-properties-rules.rst1 .. SPDX-License-Identifier: GPL-2.0
11 allows any type of device configuration data to be provided via the ACPI
20 specific type) associated with it.
22 In the ACPI _DSD context it is an element of the sub-package following the
24 section titled "Well-Known _DSD UUIDs and Data Structure Formats" sub-section
28 It also may be regarded as the definition of a key and the associated data type
29 that can be returned by _DSD in the Device Properties UUID sub-package for a
34 can be returned in the Device Properties UUID sub-package for the device in
41 section titled "Well-Known _DSD UUIDs and Data Structure Formats" sub-section
63 -------------------------
[all …]
/Documentation/netlink/specs/
Dnlctrl.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: genetlink-legacy
5 uapi-header: linux/genetlink.h
8 genetlink meta-family that exposes information about all genetlink
12 -
13 name: op-flags
14 type: flags
15 enum-name:
17 - admin-perm
18 - cmd-cap-do
[all …]
Dtc.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: netlink-raw
12 -
14 type: struct
16 -
18 type: u8
19 -
21 type: pad
23 -
25 type: s32
[all …]
/Documentation/devicetree/bindings/pinctrl/
Dcanaan,k210-fpioa.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/canaan,k210-fpioa.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Damien Le Moal <dlemoal@kernel.org>
16 a per-pin basis.
20 const: canaan,k210-fpioa
29 - description: Controller reference clock source
30 - description: APB interface clock source
32 clock-names:
[all …]
/Documentation/devicetree/bindings/soc/ti/
Dti,pruss.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 TI Programmable Real-Time Unit and Industrial Communication Subsystem
11 - Suman Anna <s-anna@ti.com>
15 The Programmable Real-Time Unit and Industrial Communication Subsystem
16 (PRU-ICSS a.k.a. PRUSS) is present on various TI SoCs such as AM335x, AM437x,
17 Keystone 66AK2G, OMAP-L138/DA850 etc. A PRUSS consists of dual 32-bit RISC
18 cores (Programmable Real-Time Units, or PRUs), shared RAM, data and
23 peripheral interfaces, fast real-time responses, or specialized data handling.
[all …]

12345678910>>...12