Searched +full:sub +full:- +full:devices (Results 1 – 25 of 1049) sorted by relevance
12345678910>>...42
| /kernel/linux/linux-6.6/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
11 Usually these are I2C devices, but not necessarily. In order to provide the
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
[all …]
|
| D | v4l2-intro.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------
7 hardware: most devices have multiple ICs, export multiple device nodes in
8 /dev, and create also non-V4L2 devices such as DVB, ALSA, FB, I2C and input
9 (IR) devices.
14 more I2C buses, but other buses can also be used. Such devices are
15 called 'sub-devices'.
22 connecting to sub-devices themselves. Some of this is quite complicated
32 A good example to look at as a reference is the v4l2-pci-skeleton.c
38 -------------------------
[all …]
|
| /kernel/linux/linux-5.10/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
11 Usually these are I2C devices, but not necessarily. In order to provide the
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
[all …]
|
| D | v4l2-intro.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------
7 hardware: most devices have multiple ICs, export multiple device nodes in
8 /dev, and create also non-V4L2 devices such as DVB, ALSA, FB, I2C and input
9 (IR) devices.
14 more I2C buses, but other buses can also be used. Such devices are
15 called 'sub-devices'.
22 connecting to sub-devices themselves. Some of this is quite complicated
32 A good example to look at as a reference is the v4l2-pci-skeleton.c
38 -------------------------
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | dev-subdev.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
6 Sub-device Interface
9 The complex nature of V4L2 devices, where hardware is often made of
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
[all …]
|
| D | open.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
7 Opening and Closing Devices
16 devices or peripherals, each of which have their own driver.
22 the hardware, which may also expose device nodes, called V4L2 sub-devices.
24 When such V4L2 sub-devices are exposed, they allow controlling those
25 other hardware components - usually connected via a serial bus (like
26 I²C, SMBus or SPI). Depending on the bridge driver, those sub-devices
29 :ref:`V4L2 sub-devices <subdev>`.
31 The devices that require the use of the
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
[all …]
|
| D | pixfmt-rgb.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _pixfmt-rgb:
21 the device type and hardware operation. :ref:`Capture <capture>` devices
22 (including capture queues of mem-to-mem devices) fill the alpha component in
25 but can set the alpha bit to a user-configurable value, the
26 :ref:`V4L2_CID_ALPHA_COMPONENT <v4l2-alpha-component>` control is used to
31 :ref:`Output <output>` devices (including output queues of mem-to-mem devices
32 and :ref:`video output overlay <osd>` devices) read the alpha component from
40 devices and drivers, for both :ref:`capture` and :ref:`output` devices.
44 - In all the tables that follow, bit 7 is the most significant bit in a byte.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | qcom_camss.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 ------------
25 ----------------------------------
30 - 2 / 3 CSIPHY modules. They handle the Physical layer of the CSI2 receivers.
32 - 2 / 4 CSID (CSI Decoder) modules. They handle the Protocol and Application
36 - ISPIF (ISP Interface) module. Handles the routing of the data streams from
38 - 1 / 2 VFE (Video Front End) module(s). Contain a pipeline of image processing
48 -----------------------
52 - Input from camera sensor via CSIPHY;
53 - Generation of test input data by the TG in CSID;
[all …]
|
| D | fimc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/media/ |
| D | qcom_camss.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 ------------
25 ----------------------------------
30 - 2 / 3 CSIPHY modules. They handle the Physical layer of the CSI2 receivers.
32 - 2 / 4 CSID (CSI Decoder) modules. They handle the Protocol and Application
36 - ISPIF (ISP Interface) module. Handles the routing of the data streams from
38 - 1 / 2 VFE (Video Front End) module(s). Contain a pipeline of image processing
48 -----------------------
52 - Input from camera sensor via CSIPHY;
53 - Generation of test input data by the TG in CSID;
[all …]
|
| D | fimc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/samsung/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-subdev.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
6 Sub-device Interface
9 The complex nature of V4L2 devices, where hardware is often made of
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
[all …]
|
| D | open.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
7 Opening and Closing Devices
16 devices or peripherals, each of which have their own driver.
22 the hardware, which may also expose device nodes, called V4L2 sub-devices.
24 When such V4L2 sub-devices are exposed, they allow controlling those
25 other hardware components - usually connected via a serial bus (like
26 I²C, SMBus or SPI). Depending on the bridge driver, those sub-devices
29 :ref:`V4L2 sub-devices <subdev>`.
31 The devices that require the use of the
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
[all …]
|
| D | pixfmt-rgb.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _pixfmt-rgb:
14 These are all packed-pixel formats, meaning all the data for a pixel lie
26 .. flat-table:: RGB Image Formats
27 :header-rows: 2
28 :stub-columns: 0
30 * - Identifier
31 - Code
32 - :cspan:`7` Byte 0 in memory
33 - :cspan:`7` Byte 1
[all …]
|
| /kernel/linux/linux-5.10/include/media/ |
| D | v4l2-device.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
12 #include <media/media-device.h>
13 #include <media/v4l2-subdev.h>
14 #include <media/v4l2-dev.h>
21 * struct v4l2_device - main struct to for V4L2 device drivers
29 * @notify: notify operation called by some sub-devices.
37 * either stand-alone or embedded in a larger struct.
39 * It allows easy access to sub-devices (see v4l2-subdev.h) and provides
40 * basic V4L2 device-level support.
44 * #) @dev->driver_data points to this struct.
[all …]
|
| D | v4l2-async.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
5 * Copyright (C) 2012-2013, Guennadi Liakhovetski <g.liakhovetski@gmx.de>
21 * enum v4l2_async_match_type - type of asynchronous subdevice logic to be used
30 * This enum is used by the asyncrhronous sub-device logic to define the
41 * struct v4l2_async_subdev - sub-device descriptor, as known to a bridge
44 * @match: union of per-bus type matching data sets
62 * Driver-specific match criteria.
65 * Driver-specific match function to be used if
68 * Driver-specific private struct with match parameters
73 * probed, to a notifier->waiting list
[all …]
|
| 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
48 * struct v4l2_fwnode_bus_parallel - parallel data bus data structure
60 * struct v4l2_fwnode_bus_mipi_csi1 - CSI-1/CCP2 data bus structure
62 * false - not inverted, true - inverted
63 * @strobe: false - data/clock, true - data/strobe
78 * struct v4l2_fwnode_endpoint - the endpoint data structure
112 * V4L2_FWNODE_PROPERTY_UNSET - identify a non initialized property
[all …]
|
| /kernel/linux/linux-6.6/include/media/ |
| D | v4l2-device.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
12 #include <media/media-device.h>
13 #include <media/v4l2-subdev.h>
14 #include <media/v4l2-dev.h>
21 * struct v4l2_device - main struct to for V4L2 device drivers
29 * @notify: notify operation called by some sub-devices.
37 * either stand-alone or embedded in a larger struct.
39 * It allows easy access to sub-devices (see v4l2-subdev.h) and provides
40 * basic V4L2 device-level support.
44 * #) @dev->driver_data points to this struct.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/sound/designs/ |
| D | procfile.rst | 15 card-specific files are stored in the ``card*`` subdirectories.
31 devices
39 Lists the currently available hwdep devices in format of
40 ``<card>-<device>: <name>``
43 Lists the currently available PCM devices in format of
44 ``<card>-<device>: <id>: <name> : <sub-streams>``
47 Lists the currently available timer devices
50 oss/devices
61 The card-specific files are found in ``/proc/asound/card*`` directories.
66 When PCM devices are available on this card, you can see directories
[all …]
|
| /kernel/linux/linux-5.10/Documentation/sound/designs/ |
| D | procfile.rst | 15 card-specific files are stored in the ``card*`` subdirectories.
31 devices
39 Lists the currently available hwdep devices in format of
40 ``<card>-<device>: <name>``
43 Lists the currently available PCM devices in format of
44 ``<card>-<device>: <id>: <name> : <sub-streams>``
47 Lists the currently available timer devices
50 oss/devices
61 The card-specific files are found in ``/proc/asound/card*`` directories.
66 When PCM devices are available on this card, you can see directories
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/media/drivers/ccs/ |
| D | ccs.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause
9 <https://www.mipi.org/specifications/camera-command-set>`_ compliant
10 camera sensors. It exposes three sub-devices representing the pixel array,
13 As the capabilities of individual devices vary, the driver exposes
16 Pixel Array sub-device
17 ----------------------
19 The pixel array sub-device represents the camera sensor's pixel matrix, as well
20 as analogue crop functionality present in many compliant devices. The analogue
26 ------
28 The binner sub-device represents the binning functionality on the sensor. For
[all …]
|
| /kernel/linux/linux-6.6/drivers/mfd/ |
| D | simple-mfd-i2c.h | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Simple MFD - I2C
8 * shared by all sub-devices. Children can use their parent's device structure
12 * shared by all sub-devices. Children can use their parent's device structure
15 * Once the register map has been successfully initialised, any sub-devices
|
| /kernel/linux/linux-6.6/Documentation/leds/ |
| D | leds-class-flash.rst | 5 Some LED devices provide two modes - torch and flash. In the LED subsystem
6 those modes are supported by LED class (see Documentation/leds/leds-class.rst)
15 Following sysfs attributes are exposed for controlling flash LED devices:
16 (see Documentation/ABI/testing/sysfs-class-led-flash)
18 - flash_brightness
19 - max_flash_brightness
20 - flash_timeout
21 - max_flash_timeout
22 - flash_strobe
23 - flash_fault
[all …]
|
| /kernel/linux/linux-5.10/Documentation/leds/ |
| D | leds-class-flash.rst | 5 Some LED devices provide two modes - torch and flash. In the LED subsystem
6 those modes are supported by LED class (see Documentation/leds/leds-class.rst)
15 Following sysfs attributes are exposed for controlling flash LED devices:
16 (see Documentation/ABI/testing/sysfs-class-led-flash)
18 - flash_brightness
19 - max_flash_brightness
20 - flash_timeout
21 - max_flash_timeout
22 - flash_strobe
23 - flash_fault
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/drivers/ |
| D | ccs.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
9 <https://www.mipi.org/specifications/camera-command-set>`_ compliant
10 camera sensors. It exposes three sub-devices representing the pixel array,
13 As the capabilities of individual devices vary, the driver exposes
16 Pixel Array sub-device
17 ----------------------
19 The pixel array sub-device represents the camera sensor's pixel matrix, as well
20 as analogue crop functionality present in many compliant devices. The analogue
26 ------
28 The binner sub-device represents the binning functionality on the sensor. For
[all …]
|
12345678910>>...42