Searched +full:multi +full:- +full:functional (Results 1 – 25 of 28) sorted by relevance
12
| /Documentation/devicetree/bindings/usb/ |
| D | mediatek,mt6370-tcpc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/mediatek,mt6370-tcpc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MediatTek MT6370 Type-C Port Switch and Power Delivery controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 MediaTek MT6370 is a multi-functional device.
16 This document only describes MT6370 Type-C Port Switch and
22 - mediatek,mt6370-tcpc
29 $ref: /schemas/connector/usb-connector.yaml#
[all …]
|
| D | mediatek,mt6360-tcpc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/mediatek,mt6360-tcpc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Mediatek MT6360 Type-C Port Switch and Power Delivery controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 Mediatek MT6360 is a multi-functional device. It integrates charger, ADC, flash, RGB indicators,
15 This document only describes MT6360 Type-C Port Switch and Power Delivery controller.
20 - mediatek,mt6360-tcpc
25 interrupt-names:
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | hi6421.txt | 1 * HI6421 Multi-Functional Device (MFD), by HiSilicon Ltd.
4 - compatible : One of the following chip-specific strings:
5 "hisilicon,hi6421-pmic";
6 "hisilicon,hi6421v530-pmic";
7 - reg : register range space of hi6421;
9 Supported Hi6421 sub-devices include:
12 ------ --------- ------------ -----------
20 compatible = "hisilicon,hi6421-pmic";
26 regulator-name = "VOUT0";
27 regulator-min-microvolt = <2850000>;
[all …]
|
| D | cirrus,madera.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Cirrus Logic Madera class audio CODECs Multi-Functional Device
10 - patches@opensource.cirrus.com
23 - $ref: /schemas/pinctrl/cirrus,madera.yaml#
24 - $ref: /schemas/regulator/wlf,arizona.yaml#
25 - $ref: /schemas/sound/cirrus,madera.yaml#
26 - if:
31 - cirrus,cs47l85
[all …]
|
| /Documentation/arch/arm/ |
| D | marvell.rst | 13 ------------
16 - 88F5082
17 - 88F5181 a.k.a Orion-1
18 - 88F5181L a.k.a Orion-VoIP
19 - 88F5182 a.k.a Orion-NAS
21 …- Datasheet: https://web.archive.org/web/20210124231420/http://csclub.uwaterloo.ca/~board/ts7800/M…
22 …- Programmer's User Guide: https://web.archive.org/web/20210124231536/http://csclub.uwaterloo.ca/~…
23 …- User Manual: https://web.archive.org/web/20210124231631/http://csclub.uwaterloo.ca/~board/ts7800…
24 …- Functional Errata: https://web.archive.org/web/20210704165540/https://www.digriz.org.uk/ts78xx/8…
25 - 88F5281 a.k.a Orion-2
[all …]
|
| /Documentation/driver-api/ |
| D | slimbus.rst | 9 ----------------
12 configuration, and is a 2-wire multi-drop implementation (clock, and data).
15 (System-on-Chip) and peripheral components (typically codec). SLIMbus uses
16 Time-Division-Multiplexing to accommodate multiple data channels, and
24 A data channel is used for data-transfer between 2 SLIMbus devices. Data
28 ---------------------
36 Framer device is responsible for clocking the bus, and transmitting frame-sync
49 responsible to select the active-framer for clocking the bus.
55 Each device has a 6-byte enumeration-address and the manager assigns every
56 device with a 1-byte logical address after the devices report presence on the
[all …]
|
| D | men-chameleon-bus.rst | 31 ----------------------
38 -----------------------------------------
44 - Multi-resource MCB devices like the VME Controller or M-Module carrier.
45 - MCB devices that need another MCB device, like SRAM for a DMA Controller's
47 - A per-carrier IRQ domain for carrier devices that have one (or more) IRQs
48 per MCB device like PCIe based carriers with MSI or MSI-X support.
53 MCB is divided into 3 functional blocks:
55 - The MEN Chameleon Bus itself,
56 - drivers for MCB Carrier Devices and
57 - the parser for the Chameleon table.
[all …]
|
| D | interconnect.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 ------------
12 latency and priority between multiple interconnected devices or functional
19 components or functional blocks in chipsets. There can be multiple interconnects
20 on an SoC that can be multi-tiered.
22 Below is a simplified diagram of a real-world SoC interconnect bus topology.
26 +----------------+ +----------------+
27 | HW Accelerator |--->| M NoC |<---------------+
28 +----------------+ +----------------+ |
29 | | +------------+
[all …]
|
| D | vfio.rst | 2 VFIO - "Virtual Function I/O" [1]_
7 allotted. This includes x86 hardware with AMD-Vi and Intel VT-d,
12 safe [2]_, non-privileged, userspace drivers.
19 bare-metal device drivers [3]_.
22 field, also benefit from low-overhead, direct device access from
23 userspace. Examples include network adapters (often non-TCP/IP based)
36 ---------------------------
42 as allowing a device read-write access to system memory imposes the
55 For instance, an individual device may be part of a larger multi-
59 could be anything from a multi-function PCI device with backdoors
[all …]
|
| /Documentation/userspace-api/media/ |
| 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 …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | renesas,rsnd.txt | 1 Renesas R-Car sound
7 Renesas R-Car and RZ/G sound is constructed from below modules
11 - SRC : Sampling Rate Converter
12 - CMD
13 - CTU : Channel Transfer Unit
14 - MIX : Mixer
15 - DVC : Digital Volume and Mute Function
22 * Multi channel
25 Multi channel is supported by Multi-SSI, or TDM-SSI.
27 Multi-SSI : 6ch case, you can use stereo x 3 SSI
[all …]
|
| /Documentation/devicetree/bindings/thermal/ |
| D | samsung,exynos-thermal.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/thermal/samsung,exynos-thermal.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
13 For multi-instance tmu each instance should have an alias correctly numbered
19 - samsung,exynos3250-tmu
20 - samsung,exynos4412-tmu
21 - samsung,exynos4210-tmu
22 - samsung,exynos5250-tmu
[all …]
|
| /Documentation/networking/ |
| D | iso15765-2.rst | 1 .. SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause)
4 ISO 15765-2 (ISO-TP)
10 ISO 15765-2, also known as ISO-TP, is a transport protocol specifically defined
12 industry, for example as the transport protocol for UDSonCAN (ISO 14229-3) or
13 emission-related diagnostic services (ISO 15031-5).
15 ISO-TP can be used both on CAN CC (aka Classical CAN) and CAN FD (CAN with
21 -------------------
23 * ISO 15765-2:2024 : Road vehicles - Diagnostic communication over Controller
27 ----------
29 In its simplest form, ISO-TP is based on two kinds of addressing modes for the
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | richtek,rtq2208.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Alina Yu <alina_yu@richtek.com>
13 RTQ2208 is a highly integrated power converter that offers functional safety dual
14 multi-configurable synchronous buck converters and two LDOs.
16 Bucks support "regulator-allowed-modes" and "regulator-mode". The former defines the permitted
25 0 - Auto mode for power saving, which reducing the switching frequency at light load condition
27 …1 - FCCM to meet the strict voltage regulation accuracy, which keeping constant switching frequenc…
35 - richtek,rtq2208
[all …]
|
| /Documentation/driver-api/rapidio/ |
| D | rio_cm.rst | 19 This driver (RIO_CM) provides to user-space applications shared access to
23 messaging mailboxes in case of multi-packet message (up to 4KB) and
24 up to 64 mailboxes if single-packet messages (up to 256 B) are used. In addition
30 capability to large number of user-space processes by introducing socket-like
39 Following ioctl commands are available to user-space applications:
41 - RIO_CM_MPORT_GET_LIST:
46 - RIO_CM_EP_GET_LIST_SIZE:
49 - RIO_CM_EP_GET_LIST:
53 - RIO_CM_CHAN_CREATE:
56 - RIO_CM_CHAN_BIND:
[all …]
|
| /Documentation/PCI/ |
| D | pci-error-recovery.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 :Authors: - Linas Vepstas <linasvepstas@gmail.com>
9 - Richard Lary <rlary@us.ibm.com>
10 - Mike Mason <mmlnx@us.ibm.com>
16 chipsets are able to deal with these errors; these include PCI-E chipsets,
17 and the PCI-host bridges found on IBM Power4, Power5 and Power6-based
32 including multiple instances of a device driver on multi-function
34 waiting for some i/o-space register to change, when it never will.
39 is forced by the need to handle multi-function devices, that is,
42 of reset it desires, the choices being a simple re-enabling of I/O
[all …]
|
| /Documentation/networking/devlink/ |
| D | mlx5.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 - Validation
18 * - ``enable_roce``
19 - driverinit
20 - Type: Boolean
26 * - ``io_eq_size``
27 - driverinit
[all …]
|
| /Documentation/hwmon/ |
| D | submitting-patches.rst | 10 ----------
14 - Documentation/process/submit-checklist.rst
15 - Documentation/process/submitting-patches.rst
16 - Documentation/process/coding-style.rst
18 * Please run your patch through 'checkpatch --strict'. There should be no
22 * Please use the standard multi-line comment style. Do not mix C and C++
34 hardware. In such cases, you should test-build the code on at least one
35 architecture. If run-time testing was not achieved, it should be written
43 -------------------------------------------
54 * Never mix bug fixes, cleanup, and functional enhancements in a single patch.
[all …]
|
| /Documentation/userspace-api/ |
| D | iommufd.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
20 I/O page tables for all IOMMUs, with room in the design to add non-generic
31 --------------------
35 - IOMMUFD_OBJ_IOAS, representing an I/O address space (IOAS), allowing map/unmap
38 The IOAS is a functional replacement for the VFIO container, and like the VFIO
41 - IOMMUFD_OBJ_DEVICE, representing a device that is bound to iommufd by an
44 - IOMMUFD_OBJ_HW_PAGETABLE, representing an actual hardware I/O page table
50 All user-visible objects are destroyed via the IOMMU_DESTROY uAPI.
52 The diagram below shows relationship between user-visible objects and kernel
68 | | IOAS |<--| |<------| | |
[all …]
|
| /Documentation/mhi/ |
| D | mhi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
26 ----
45 debugging information like performance, functional, and stability to the host.
48 ---------------
74 --------
82 bidirectional data pipe, which can be used by the upper-layer protocols to
88 --------------
95 [Read Pointer (RP)] ----------->[Ring Element] } TD
96 [Write Pointer (WP)]- [Ring Element]
97 - [Ring Element]
[all …]
|
| /Documentation/fpga/ |
| D | dfl.rst | 7 - Enno Luebbers <enno.luebbers@intel.com>
8 - Xiao Guangrong <guangrong.xiao@linux.intel.com>
9 - Wu Hao <hao.wu@intel.com>
10 - Xu Yilun <yilun.xu@intel.com>
29 +----------+ +-->+----------+ +-->+----------+ +-->+----------+
32 +----------+ | | Feature | | | Feature | | | Feature |
33 | Next_DFH |--+ +----------+ | +----------+ | +----------+
34 +----------+ | Next_DFH |--+ | Next_DFH |--+ | Next_DFH |--> NULL
35 | ID | +----------+ +----------+ +----------+
36 +----------+ | ID | | ID | | ID |
[all …]
|
| /Documentation/accel/qaic/ |
| D | aic100.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
10 The Qualcomm Cloud AI 100/AIC100 family of products (including SA9000P - part of
20 performance. AIC100 cards are multi-user capable and able to execute workloads
26 An AIC100 card consists of an AIC100 SoC, on-card DDR, and a set of misc
39 AIC100 implements MSI but does not implement MSI-X. AIC100 prefers 17 MSIs to
44 hardware. AIC100 provides 3, 64-bit BARs.
54 From the host perspective, AIC100 has several key hardware components -
63 ---
71 ---
74 firmware of the card and performs on-card management tasks. It also
[all …]
|
| /Documentation/dev-tools/ |
| D | checkpatch.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
27 - -q, --quiet
31 - -v, --verbose
35 - --no-tree
39 - --no-signoff
41 Disable the 'Signed-off-by' line check. The sign-off is a simple line at
43 or otherwise have the right to pass it on as an open-source patch.
47 Signed-off-by: Random J Developer <random@developer.example.org>
49 Setting this flag effectively stops a message for a missing signed-off-by
52 - --patch
[all …]
|
| /Documentation/networking/device_drivers/can/ctu/ |
| D | ctucanfd-driver.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
10 ------------------------
19 `Vivado integration <https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top>`_
20 and Intel Cyclone V 5CSEMA4U23C6 based DE0-Nano-SoC Terasic board
21 `QSys integration <https://gitlab.fel.cvut.cz/canbus/intel-soc-ctucanfd>`_
23 `PCIe integration <https://gitlab.fel.cvut.cz/canbus/pcie-ctucanfd>`_ of the core.
30 The basic functional model of the CTU CAN FD peripheral has been
33 version of emulation support can be cloned from ctu-canfd branch of QEMU local
34 development `repository <https://gitlab.fel.cvut.cz/canbus/qemu-canbus>`_.
38 ---------------
[all …]
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
42 by implementing various role-specific suspend and resume methods to
[all …]
|
12