| /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
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 …]
|
| H A 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 …]
|
| /linux/Documentation/admin-guide/media/ |
| H A 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 …]
|
| H A 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 …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A 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 …]
|
| H A 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 …]
|
| H A D | vidioc-subdev-querycap.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_QUERYCAP - Query sub-device capabilities
34 All V4L2 sub-devices support the ``VIDIOC_SUBDEV_QUERYCAP`` ioctl. It is used to
35 identify kernel devices compatible with this specification and to obtain
45 .. flat-table:: struct v4l2_subdev_capability
46 :header-rows: 0
47 :stub-columns: 0
50 * - __u32
51 - ``version``
52 - Version number of the driver.
[all …]
|
| H A D | metafmt-generic.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
8 Generic line-based metadata formats
14 These generic line-based metadata formats define the memory layout of the data
17 .. _v4l2-meta-fmt-generic-8:
20 -----------------------
22 The V4L2_META_FMT_GENERIC_8 format is a plain 8-bit metadata format. This format
23 is used on CSI-2 for 8 bits per :term:`Data Unit`.
26 packed into one 16-bit Data Unit. Otherwise the 16 bits per pixel dataformat is
27 :ref:`V4L2_META_FMT_GENERIC_CSI2_16 <v4l2-meta-fmt-generic-csi2-16>`.
34 .. flat-table:: Sample 4x2 Metadata Frame
[all …]
|
| H A D | vidioc-subdev-enum-frame-interval.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL - Enumerate frame intervals
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
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.
66 .. flat-table:: struct v4l2_subdev_frame_interval_enum
67 :header-rows: 0
68 :stub-columns: 0
[all …]
|
| /linux/include/media/ |
| H A 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>
19 * struct v4l2_device - main struct to for V4L2 device drivers
27 * @notify: notify operation called by some sub-devices.
35 * either stand-alone or embedded in a larger struct.
37 * It allows easy access to sub-devices (see v4l2-subdev.h) and provides
38 * basic V4L2 device-level support.
42 * #) @dev->driver_data points to this struct.
[all …]
|
| H A D | v4l2-async.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
5 * Copyright (C) 2012-2013, Guennadi Liakhovetski <g.liakhovetski@gmx.de>
22 * enum v4l2_async_match_type - type of asynchronous subdevice logic to be used
37 * struct v4l2_async_match_desc - async connection match information
65 * struct v4l2_async_connection - sub-device connection descriptor, as known to
68 * @match: struct of match type and per-bus type matching data sets
73 * @sd: the related sub-device
88 * struct v4l2_async_notifier_operations - Asynchronous V4L2 notifier operations
89 * @bound: a sub-device has been bound by the given connection
107 * struct v4l2_async_notifier - v4l2_device notifier data
[all …]
|
| /linux/Documentation/sound/designs/ |
| H A 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 …]
|
| /linux/Documentation/leds/ |
| H A 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 …]
|
| /linux/Documentation/userspace-api/media/drivers/ |
| H A D | ccs.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
5 .. _media-ccs-uapi:
11 <https://www.mipi.org/specifications/camera-command-set>`_ compliant
12 camera sensors. It exposes three sub-devices representing the pixel array,
15 As the capabilities of individual devices vary, the driver exposes
18 Also see :ref:`the CCS driver kernel documentation <media-ccs-driver>`.
20 Pixel Array sub-device
21 ----------------------
23 The pixel array sub-device represents the camera sensor's pixel matrix, as well
24 as analogue crop functionality present in many compliant devices. The analogue
[all …]
|
| H A D | camera-sensor.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 This section describes common practices for how the V4L2 sub-device interface is
14 ----------
23 processing pipeline as one or more sub-devices with different cropping and
41 ----------------------------
61 large variety of devices beyond camera sensors. Devices that have no analogue
68 sub-device. The unit of that control is pixels per second.
70 Register list based drivers need to implement read-only sub-device nodes for the
71 purpose. Devices that are not register list based need these to configure the
79 USB cameras etc. devices
[all …]
|
| /linux/drivers/mfd/ |
| H A 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
|
| /linux/drivers/media/v4l2-core/ |
| H A D | v4l2-async.c | 1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright (C) 2012-2013, Guennadi Liakhovetski <g.liakhovetski@gmx.de>
22 #include <media/v4l2-async.h>
23 #include <media/v4l2-device.h>
24 #include <media/v4l2-fwnode.h>
25 #include <media/v4l2-subdev.h>
27 #include "v4l2-subdev-priv.h"
33 if (!n->ops || !n->ops->bound) in v4l2_async_nf_call_bound()
36 return n->ops->bound(n, subdev, asc); in v4l2_async_nf_call_bound()
43 if (!n->ops || !n->ops->unbind) in v4l2_async_nf_call_unbind()
[all …]
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | keystone-netcp.txt | 6 switch sub-module to send and receive packets. NetCP also includes a packet
13 includes a 3-port Ethernet switch sub-module capable of 10Gb/s and 1Gb/s rates
16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP
17 sub-modules exist as a loadable kernel module which plug in to the netcp core.
18 These sub-modules are represented as "netcp-devices" in the dts bindings. It is
19 mandatory to have the ethernet switch sub-module for the ethernet interface to
20 be operational. Any other sub-module like the PA is optional.
24 -----------------------------
26 -----------------------------
28 |-> NetCP Devices -> |
[all …]
|
| /linux/Documentation/admin-guide/perf/ |
| H A D | alibaba_pmu.rst | 2 Alibaba's T-Head SoC Uncore Performance Monitoring Unit (PMU)
5 The Yitian 710, custom-built by Alibaba Group's chip development business,
6 T-Head, implements uncore PMU for performance and functional debugging to
9 DDR Sub-System Driveway (DRW) PMU Driver
14 channel is split into two independent sub-channels. The DDR Sub-System Driveway
15 implements separate PMUs for each sub-channel to monitor various performance
18 The Driveway PMU devices are named as ali_drw_<sys_base_addr> with perf.
19 For example, ali_drw_21000 and ali_drw_21080 are two PMU devices for two
20 sub-channels of the same channel in die 0. And the PMU device of die 1 is
23 Each sub-channel has 36 PMU counters in total, which is classified into
[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
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
67 What: /sys/bus/nd/devices/nmemX/nfit/format1
[all …]
|
| /linux/Documentation/devicetree/bindings/opp/ |
| H A D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
16 applicable across wide range of devices. For illustration purpose, this document
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
31 Missing property means devices have independent clock/voltage/current
[all …]
|
| /linux/Documentation/filesystems/ |
| H A D | zonefs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ZoneFS - Zone filesystem for Zoned block devices
11 as a file. Unlike a regular POSIX-compliant file system with native zoned block
13 constraint of zoned block devices to the user. Files representing sequential
18 than to a full-featured POSIX file system. The goal of zonefs is to simplify
22 example of this approach is the implementation of LSM (log-structured merge)
23 tree structures (such as used in RocksDB and LevelDB) on zoned block devices
30 Zoned block devices
31 -------------------
33 Zoned storage devices belong to a class of storage devices with an address
[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
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,
84 like sub-device hardware components.
86 See http://www.nxp.com/docs/en/user-guide/UM10204.pdf.
120 - :term:`CEC API`;
121 - :term:`Digital TV API`;
[all …]
|
| /linux/scripts/ |
| H A D | leaking_addresses.pl | 2 # SPDX-License-Identifier: GPL-2.0-only
7 # - Scans dmesg output.
8 # - Walks directory tree and parses each file (for each directory in @DIRS).
10 # Use --debug to output path before parsing, this is useful to find files that
42 # Kernel addresses vary by architecture. We can only auto-detect the following
43 # architectures (using `uname -m`). (flag --32-bit overrides auto-detection.)
57 my $opt_32bit = 0; # Scan 32-bit kernel.
58 my $page_offset_32bit = 0; # Page offset for 32-bit kernel.
65 '/proc/device-tree',
85 sub help
[all …]
|
| /linux/include/linux/mfd/ |
| H A D | rsmu.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Core interface for Renesas Synchronization Management Unit (SMU) devices.
14 /* The supported devices are ClockMatrix, Sabre and SnowLotus */
23 * struct rsmu_ddata - device data structure for sub devices.
27 * @lock: mutex used by sub devices to make sure a series of
|