Searched +full:sub +full:- +full:module (Results 1 – 25 of 92) sorted by relevance
1234
| /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.
31 A separate camera sensor can be connected to each of the CSIPHY module;
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
41 processing pipeline contains also a scale and crop module at the end. Three
48 -----------------------
[all …]
|
| D | davinci-vpbe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 -----------------------
20 in the VENC or external sub devices. It also provides
22 using sub device ops. The connection of external encoders to VENC LCD
29 board specific settings (specified in board-xxx-evm.c). This allows
36 3. VENC subdevice module
43 venc using non-standard timing mode.
49 output name to board-xxx-evm.c). A table of timings for various LCDs
55 4. OSD module
57 OSD module implements all OSD layer management and hardware specific
[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 …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-eic-sprd.txt | 6 controller contains 4 sub-modules: EIC-debounce, EIC-latch, EIC-async and
7 EIC-sync. But the PMIC EIC controller contains only one EIC-debounce sub-
8 module.
10 The EIC-debounce sub-module provides up to 8 source input signal
12 stable status (millisecond resolution) and a single-trigger mechanism
13 is introduced into this sub-module to enhance the input event detection
14 reliability. In addition, this sub-module's clock can be shut off
19 The EIC-latch sub-module is used to latch some special power down signals
20 and generate interrupts, since the EIC-latch does not depend on the APB
23 The EIC-async sub-module uses a 32kHz clock to capture the short signals
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | keystone-netcp.txt | 6 switch sub-module to send and receive packets. NetCP also includes a packet
7 accelerator (PA) module to perform packet classification operations such as
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 -----------------------------
[all …]
|
| /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
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 …]
|
| /Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 9 a reset provider (e.g. power management or clock module) and received by a
10 reset consumer (the module being reset, or a module managing when a sub-
11 ordinate module is reset). This binding exists to represent the provider and
15 specifier - a list of DT cells that represents the reset signal within the
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 …]
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | ti,pruss.yaml | 1 # 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 …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | omap-usb.txt | 4 - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
5 - ti,hwmods : must be "usb_otg_hs"
6 - multipoint : Should be "1" indicating the musb controller supports
7 multipoint. This is a MUSB configuration-specific setting.
8 - num-eps : Specifies the number of endpoints. This is also a
9 MUSB configuration-specific setting. Should be set to "16"
10 - ram-bits : Specifies the ram address size. Should be set to "12"
11 - interface-type : This is a board specific setting to describe the type of
14 - mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
16 - power : Should be "50". This signifies the controller can supply up to
[all …]
|
| /Documentation/sound/designs/ |
| D | procfile.rst | 15 card-specific files are stored in the ``card*`` subdirectories.
29 Lists the module of each card
40 ``<card>-<device>: <name>``
44 ``<card>-<device>: <id>: <name> : <sub-streams>``
61 The card-specific files are found in ``/proc/asound/card*`` directories.
78 When the OSS mixer emulation is enabled (and the module is loaded),
81 mapping by writing to this device. Read OSS-Emulation.txt for
123 ``card*/pcm*/sub*/info``
124 The general information of this PCM sub-stream.
126 ``card*/pcm*/sub*/status``
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | open.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
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>`.
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
34 are called **video-node-centric**.
36 Userspace can check if a V4L2 hardware peripheral is MC-centric by
38 :ref:`device_caps field <device-capabilities>`.
[all …]
|
| /Documentation/hwmon/ |
| D | ibmpowernv.rst | 11 -----------
22 the DT maps to an attribute file in 'sysfs'. The node exports unique 'sensor-id'
26 -----------
28 CONFIG_SENSORS_IBMPOWERNV. It can also be built as module 'ibmpowernv'.
31 ----------------
36 fanX_fault - 0: No fail condition
37 - 1: Failing fan
44 sub-group. In POWER9, this attribute corresponds to
48 - 1: Enable
49 - 0: Disable
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-nfit | 8 Contact: linux-nvdimm@lists.01.org
10 (RO) Serial number of the NVDIMM (non-volatile dual in-line
11 memory module), assigned by the module vendor.
17 Contact: linux-nvdimm@lists.01.org
26 Contact: linux-nvdimm@lists.01.org
28 (RO) Device id for the NVDIMM, assigned by the module vendor.
34 Contact: linux-nvdimm@lists.01.org
36 (RO) Revision of the NVDIMM, assigned by the module vendor.
42 Contact: linux-nvdimm@lists.01.org
52 Contact: linux-nvdimm@lists.01.org
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | max77650-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/max77650-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bartosz Golaszewski <bgolaszewski@baylibre.com>
13 This module is part of the MAX77650 MFD device. For more details
16 The regulator controller is represented as a sub-node of the PMIC node
19 The device has a single LDO regulator and a SIMO buck-boost regulator with
24 const: maxim,max77650-regulator
27 "^regulator-(ldo|sbb[0-2])$":
[all …]
|
| D | rohm,bd9576-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/regulator/rohm,bd9576-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
13 This module is part of the ROHM BD9576 MFD device. For more details
14 see Documentation/devicetree/bindings/mfd/rohm,bd9576-pmic.yaml.
16 The regulator controller is represented as a sub-node of the PMIC node
20 regulator-vd50, regulator-vd18, regulator-vdddr, regulator-vd10,
21 regulator-voutl1, regulator-vouts1
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | brcm,bcm2835-gpio.txt | 3 The BCM2835 GPIO module is a combined GPIO controller, (GPIO) interrupt
7 - compatible: "brcm,bcm2835-gpio"
8 - compatible: should be one of:
9 "brcm,bcm2835-gpio" - BCM2835 compatible pinctrl
10 "brcm,bcm7211-gpio" - BCM7211 compatible pinctrl
11 "brcm,bcm2711-gpio" - BCM2711 compatible pinctrl
12 "brcm,bcm7211-gpio" - BCM7211 compatible pinctrl
13 - reg: Should contain the physical address of the GPIO module's registers.
14 - gpio-controller: Marks the device node as a GPIO controller.
15 - #gpio-cells : Should be two. The first cell is the pin number and the
[all …]
|
| /Documentation/input/devices/ |
| D | xpad.rst | 2 xpad - Linux USB driver for Xbox compatible controllers
5 This driver exposes all first-party and third-party Xbox compatible
25 - if you are using a known controller
26 - if you are using a known dance pad
27 - if using an unknown device (one not listed below), what you set in the
28 module configuration for "Map D-PAD to buttons rather than axes for unknown
29 pads" (module option dpad_to_buttons)
33 If you said Y it will map the d-pad to buttons, which is needed for dance
43 ------------------
46 The jstest-program from joystick-1.2.15 (jstest-version 2.1.0) will report 8
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | max77650-charger.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/supply/max77650-charger.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bartosz Golaszewski <bgolaszewski@baylibre.com>
13 This module is part of the MAX77650 MFD device. For more details
16 The charger is represented as a sub-node of the PMIC node on the device tree.
20 const: maxim,max77650-charger
22 input-voltage-min-microvolt:
28 input-current-limit-microamp:
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | max77650-onkey.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/input/max77650-onkey.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bartosz Golaszewski <bgolaszewski@baylibre.com>
13 This module is part of the MAX77650 MFD device. For more details
16 The onkey controller is represented as a sub-node of the PMIC node on
21 const: maxim,max77650-onkey
26 The key-code to be reported when the key is pressed. Defaults
29 maxim,onkey-slide:
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-max77650.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-max77650.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bartosz Golaszewski <bgolaszewski@baylibre.com>
13 This module is part of the MAX77650 MFD device. For more details
16 The LED controller is represented as a sub-node of the PMIC node on
23 const: maxim,max77650-led
25 "#address-cells":
28 "#size-cells":
[all …]
|
| D | rohm,bd71828-leds.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/rohm,bd71828-leds.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
13 This module is part of the ROHM BD71828 MFD device. For more details
14 see Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml.
16 The LED controller is represented as a sub-node of the PMIC node on the device
19 The device has two LED outputs referred as GRNLED and AMBLED in data-sheet.
25 const: rohm,bd71828-leds
[all …]
|
| /Documentation/devicetree/bindings/arm/freescale/ |
| D | fsl,vf610-mscm-ir.txt | 1 Freescale Vybrid Miscellaneous System Control - Interrupt Router
3 The MSCM IP contains multiple sub modules, this binding describes the second
6 it controls the directed processor interrupts. The module is available in all
8 which comes with a Cortex-A5/Cortex-M4 combination).
11 - compatible: "fsl,vf610-mscm-ir"
12 - reg: the register range of the MSCM Interrupt Router
13 - fsl,cpucfg: The handle to the MSCM CPU configuration node, required
15 - interrupt-controller: Identifies the node as an interrupt controller
16 - #interrupt-cells: Two cells, interrupt number and cells.
23 mscm_ir: interrupt-controller@40001800 {
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | mt6397.txt | 3 MT6397/MT6323 is a multifunction device with the following sub modules:
4 - Regulator
5 - RTC
6 - Audio codec
7 - GPIO
8 - Clock
9 - LED
10 - Keys
11 - Power controller
18 This document describes the binding for MFD device and its sub module.
[all …]
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,omap-remoteproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The OMAP family of SoCs usually have one or more slave processor sub-systems
14 that are used to offload some of the processor-intensive tasks, or to manage
17 The processor cores in the sub-system are usually behind an IOMMU, and may
18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
[all …]
|
| /Documentation/devicetree/bindings/hsi/ |
| D | omap-ssi.txt | 9 - compatible: Should include "ti,omap3-ssi" or "ti,omap4-hsi"
10 - reg-names: Contains the values "sys" and "gdd" (in this order).
11 - reg: Contains a matching register specifier for each entry
12 in reg-names.
13 - interrupt-names: Contains the value "gdd_mpu".
14 - interrupts: Contains matching interrupt information for each entry
15 in interrupt-names.
16 - ranges: Represents the bus address mapping between the main
18 - clock-names: Must include the following entries:
22 - clocks: Contains a matching clock specifier for each entry in
[all …]
|
1234