Searched +full:sub +full:- +full:modules (Results 1 – 25 of 60) sorted by relevance
123
| /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 …]
|
| D | building.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 distribution-specific source file or via the Kernel's main git tree\ [1]_. 12 - you're a braveheart and want to experiment with new stuff; 13 - if you want to report a bug; 14 - if you're developing new patches 23 https://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers 50 Device Drivers ---> 51 <M> Remote Controller support ---> 54 [*] HDMI CEC drivers ---> 55 <*> Multimedia support ---> [all …]
|
| D | ipu6-isys.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 Copyright |copy| 2023--2024 Intel Corporation 26 Intel IPU6 is made up of two components - Input System (ISYS) and Processing 29 The Input System mainly works as MIPI CSI-2 receiver which receives and 32 There are 2 driver modules - intel-ipu6 and intel-ipu6-isys. intel-ipu6 is an 34 firmware authentication, DMA mapping and IPU-MMU (internal Memory mapping Unit) 36 sub-device interfaces. The IPU6 ISYS driver supports camera sensors connected 37 to the IPU6 ISYS through V4L2 sub-device sensor drivers. 39 .. Note:: See Documentation/driver-api/media/drivers/ipu6.rst for more 45 The Input System driver mainly configures CSI-2 D-PHY, constructs the firmware [all …]
|
| /Documentation/devicetree/bindings/net/ |
| 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 …]
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,davinci-rproc.txt | 4 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that 5 is used to offload some of the processor-intensive tasks or algorithms, for 8 The processor cores in the sub-system usually contain additional sub-modules 15 Each DSP Core sub-system is represented as a single DT node. 18 -------------------- 21 - compatible: Should be one of the following, 22 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs 24 - reg: Should contain an entry for each value in 'reg-names'. 27 the parent node's '#address-cells' and '#size-cells' values. 29 - reg-names: Should contain strings with the following names, each [all …]
|
| 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 …]
|
| 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 …]
|
| D | ti,keystone-rproc.txt | 5 sub-systems that are used to offload some of the processor-intensive tasks or 8 These processor sub-systems usually contain additional sub-modules like L1 15 Each DSP Core sub-system is represented as a single DT node, and should also 22 -------------------- 25 - compatible: Should be one of the following, 26 "ti,k2hk-dsp" for DSPs on Keystone 2 66AK2H/K SoCs 27 "ti,k2l-dsp" for DSPs on Keystone 2 66AK2L SoCs 28 "ti,k2e-dsp" for DSPs on Keystone 2 66AK2E SoCs 29 "ti,k2g-dsp" for DSPs on Keystone 2 66AK2G SoCs 31 - reg: Should contain an entry for each value in 'reg-names'. [all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | sprd,gpio-eic.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/gpio/sprd,gpio-eic.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Orson Zhai <orsonzhai@gmail.com> 12 - Baolin Wang <baolin.wang7@gmail.com> 13 - Chunyan Zhang <zhang.lyra@gmail.com> 19 controller contains 4 sub-modules, i.e. EIC-debounce, EIC-latch, EIC-async and 20 EIC-sync. But the PMIC EIC controller contains only one EIC-debounce sub- 23 The EIC-debounce sub-module provides up to 8 source input signal [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/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 19 instruction RAMs, some internal peripheral modules to facilitate industrial [all …]
|
| /Documentation/userspace-api/netlink/ |
| D | netlink-raw.rst | 1 .. 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 …]
|
| /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 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 { 24 compatible = "fsl,vf610-mscm-ir"; [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 …]
|
| D | max77650.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: MAX77650 ultra low-power PMIC from Maxim Integrated. 10 - Bartosz Golaszewski <bgolaszewski@baylibre.com> 13 MAX77650 is an ultra-low power PMIC providing battery charging and power 14 supply for low-power IoT and wearable applications. 16 The GPIO-controller module is represented as part of the top-level PMIC 19 For device-tree bindings of other sub-modules (regulator, power supply, 21 sub-system directories. [all …]
|
| D | max77620.txt | 4 ------------------- 5 - compatible: Must be one of 9 - reg: I2C device address. 12 ------------------- 13 - interrupts: The interrupt on the parent the controller is 15 - interrupt-controller: Marks the device node as an interrupt controller. 16 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells 17 variant of <../interrupt-controller/interrupts.txt> 19 are defined at dt-bindings/mfd/max77620.h. 21 - system-power-controller: Indicates that this PMIC is controlling the [all …]
|
| D | mediatek,mt6357.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Flora Fu <flora.fu@mediatek.com> 11 - Alexandre Mergnat <amergnat@baylibre.com> 18 This is a multifunction device with the following sub modules: 19 - Regulator 20 - RTC 21 - Keys 35 interrupt-controller: true [all …]
|
| /Documentation/sound/designs/ |
| D | procfile.rst | 15 card-specific files are stored in the ``card*`` subdirectories. 28 modules 40 ``<card>-<device>: <name>`` 44 ``<card>-<device>: <id>: <name> : <sub-streams>`` 61 The card-specific files are found in ``/proc/asound/card*`` directories. 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`` 127 The current status of this PCM sub-stream, elapsed time, [all …]
|
| /Documentation/usb/ |
| 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 40 - 3Com OfficeConnect 56k 41 - 3Com Voice FaxModem Pro 42 - 3Com Sportster 43 - MultiTech MultiModem 56k 44 - Zoom 2986L FaxModem 45 - Compaq 56k FaxModem 46 - ELSA Microlink 56k [all …]
|
| D | gadget_configfs.rst | 50 http://www.spinics.net/lists/linux-usb/msg76388.html) 55 $ mount none $CONFIGFS_HOME -t configfs 60 ----------------------- 104 ------------------------------ 134 ------------------------- 150 Each function provides its specific set of attributes, with either read-only 151 or read-write access. Where applicable they need to be written to as 153 Please refer to Documentation/ABI/testing/configfs-usb-gadget for more information. 156 ------------------------------------------------------ 164 $ ln -s functions/<name>.<instance name> configs/<name>.<number> [all …]
|
| D | gadget_serial.rst | 7 (updated 8-May-2008 for v2.3) 11 ---------------------- 25 MA 02111-1307 USA. 35 ------------- 45 gadget and usb drivers as modules. 55 -------- 65 -------------------------------------- 66 | Host-Side CDC ACM USB Host | 68 | System | Generic USB | Driver |-------- 71 -------------------------------------- | [all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | cnxt,cx92755-pinctrl.txt | 4 modules in the Conexant Digicolor CX92755 SoCs. The CX92755 in one of the 11 - compatible: Must be "cnxt,cx92755-pinctrl" 12 - reg: Base address of the General Purpose Pin Mapping register block and the 14 - gpio-controller: Marks the device node as a GPIO controller. 15 - #gpio-cells: Must be <2>. The first cell is the pin number and the 16 second cell is used to specify flags. See include/dt-bindings/gpio/gpio.h 22 compatible = "cnxt,cx92755-pinctrl"; 24 gpio-controller; 25 #gpio-cells = <2>; 36 Each pin configuration node is a sub-node of the pin controller node and is a [all …]
|
| /Documentation/filesystems/ |
| D | relay.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 to userspace via user-defined 'relay channels'. 11 A 'relay channel' is a kernel->user data relay mechanism implemented 12 as a set of per-cpu kernel buffers ('channel buffers'), each 25 filtering - this also is left to the kernel client. The purpose is to 30 functions in the relay interface code - please see that for details. 36 sub-buffers. Messages are written to the first sub-buffer until it is 38 the next (if available). Messages are never split across sub-buffers. 40 sub-buffer, while the kernel continues writing to the next. 42 When notified that a sub-buffer is full, the kernel knows how many [all …]
|
| /Documentation/devicetree/bindings/soc/mediatek/ |
| D | mediatek,mutex.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Chun-Kuang Hu <chunkuang.hu@kernel.org> 11 - Philipp Zabel <p.zabel@pengutronix.de> 15 Start Of Frame (SOF) / End Of Frame (EOF) to each sub-modules on the display 27 - mediatek,mt2701-disp-mutex 28 - mediatek,mt2712-disp-mutex 29 - mediatek,mt6795-disp-mutex 30 - mediatek,mt8167-disp-mutex [all …]
|
123