Searched +full:multi +full:- +full:functional (Results 1 – 25 of 183) sorted by relevance
12345678
| /kernel/linux/linux-6.6/drivers/usb/typec/tcpm/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Port Controller Manager"
9 The Type-C Port Controller Manager provides a USB PD and USB Type-C
10 state machine for use with Type-C Port Controllers.
15 tristate "Type-C Port Controller Interface driver"
19 Type-C Port Controller driver for TCPCI-compliant controller.
24 tristate "Richtek RT1711H Type-C chip driver"
26 Richtek RT1711H Type-C chip driver that works with
27 Type-C Port Controller Manager to provide USB PD and USB
28 Type-C functionalities.
[all …]
|
| /kernel/linux/linux-5.10/drivers/clk/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
76 These multi-function devices have two fixed-rate oscillators, clocked at 32KHz each.
86 multi-function device has one fixed-rate oscillator, clocked
117 be pre-programmed to support other configurations and features not yet
166 This driver supports TI CDCE706 programmable 3-PLL clock synthesizer.
176 For example, the CDCE925 contains two PLLs with spread-spectrum
186 tristate "Clock driver for CS2000 Fractional-N Clock Synthesizer & Clock Multiplier"
229 clock. These multi-function devices have two (S2MPS14) or three
230 (S2MPS11, S5M8767) fixed-rate oscillators, clocked at 32KHz each.
233 tristate "External McPDM functional clock from twl6040"
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/ |
| D | exynos-thermal.txt | 5 - compatible : One of the following:
6 "samsung,exynos3250-tmu"
7 "samsung,exynos4412-tmu"
8 "samsung,exynos4210-tmu"
9 "samsung,exynos5250-tmu"
10 "samsung,exynos5260-tmu"
11 "samsung,exynos5420-tmu" for TMU channel 0, 1 on Exynos5420
12 "samsung,exynos5420-tmu-ext-triminfo" for TMU channels 2, 3 and 4
14 "samsung,exynos5433-tmu"
15 "samsung,exynos7-tmu"
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 | stmpe.txt | 1 * ST Microelectronics STMPE Multi-Functional Device
7 - compatible : "st,stmpe[610|801|811|1600|1601|2401|2403]"
8 - reg : I2C/SPI address of the device
11 - interrupts : The interrupt outputs from the controller
12 - interrupt-controller : Marks the device node as an interrupt controller
13 - wakeup-source : Marks the input device as wakable
14 - st,autosleep-timeout : Valid entries (ms); 4, 16, 32, 64, 128, 256, 512 and 1024
15 - irq-gpio : If present, which GPIO to use for event IRQ
18 - st,sample-time : ADC conversion time in number of clock.
19 0 -> 36 clocks 4 -> 80 clocks (recommended)
[all …]
|
| /kernel/linux/linux-6.6/drivers/clk/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
59 Low-Noise JESD204B Compliant Clock Jitter Cleaner With Dual Loop PLLs
88 These multi-function devices have two fixed-rate oscillators, clocked at 32KHz each.
98 multi-function device has one fixed-rate oscillator, clocked
129 be pre-programmed to support other configurations and features not yet
178 This driver supports TI CDCE706 programmable 3-PLL clock synthesizer.
196 For example, the CDCE925 contains two PLLs with spread-spectrum
206 tristate "Clock driver for CS2000 Fractional-N Clock Synthesizer & Clock Multiplier"
277 clock. These multi-function devices have two (S2MPS14) or three
278 (S2MPS11, S5M8767) fixed-rate oscillators, clocked at 32KHz each.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/ |
| D | v4l2-clocks.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -----------
15 the nature of the multi-functional (clock, data + synchronisation, I2C control)
|
| /kernel/linux/linux-5.10/drivers/usb/typec/tcpm/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Port Controller Manager"
9 The Type-C Port Controller Manager provides a USB PD and USB Type-C
10 state machine for use with Type-C Port Controllers.
15 tristate "Type-C Port Controller Interface driver"
19 Type-C Port Controller driver for TCPCI-compliant controller.
24 tristate "Richtek RT1711H Type-C chip driver"
26 Richtek RT1711H Type-C chip driver that works with
27 Type-C Port Controller Manager to provide USB PD and USB
28 Type-C functionalities.
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/ |
| D | renesas,mmcif.txt | 1 * Renesas Multi Media Card Interface (MMCIF) Controller
9 - compatible: should be "renesas,mmcif-<soctype>", "renesas,sh-mmcif" as a
11 - "renesas,mmcif-r7s72100" for the MMCIF found in r7s72100 SoCs
12 - "renesas,mmcif-r8a73a4" for the MMCIF found in r8a73a4 SoCs
13 - "renesas,mmcif-r8a7740" for the MMCIF found in r8a7740 SoCs
14 - "renesas,mmcif-r8a7742" for the MMCIF found in r8a7742 SoCs
15 - "renesas,mmcif-r8a7743" for the MMCIF found in r8a7743 SoCs
16 - "renesas,mmcif-r8a7744" for the MMCIF found in r8a7744 SoCs
17 - "renesas,mmcif-r8a7745" for the MMCIF found in r8a7745 SoCs
18 - "renesas,mmcif-r8a7778" for the MMCIF found in r8a7778 SoCs
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-pm8058.txt | 3 The Qualcomm PM8058 is a multi-functional device which contains
8 are more of a suggestion than a hard-wired usecase.
10 Hardware-wise the different LEDs support slightly different
17 mfd/qcom-pm8xxx.txt.
19 Each LED is represented as a sub-node of the syscon device. Each
22 LED sub-node properties:
25 - compatible: one of
26 "qcom,pm8058-led" (for the normal LEDs at 0x131, 0x132 and 0x133)
27 "qcom,pm8058-keypad-led" (for the "keypad" LED at 0x48)
28 "qcom,pm8058-flash-led" (for the "flash" LEDs at 0x49 and 0xFB)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 4 Flash devices can be partitioned into one or more functional ranges (e.g. "boot
8 flash layout set at production time. Some may use on-flash table that describes
9 the geometry and naming/purpose of each functional region. It is also possible
20 hierarchical (multi-level) layouts and should be used if there is some
30 Partitions can be represented by sub-nodes of a flash device. This can be used
32 used for what purposes, but which don't use an on-flash partition table such
37 - compatible : (required) must be "fixed-partitions"
45 #address-cells & #size-cells must both be present in the partitions subnode of the
47 <1>: for partitions that require a single 32-bit cell to represent their
49 <2>: for partitions that require two 32-bit cells to represent their
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/ |
| 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 DT bindings
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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pinctrl.txt | 4 to share one PAD to several functional blocks. The sharing is done by
10 Please refer to pinctrl-bindings.txt in this directory for details of the
18 such as pull-up, multi drive, etc.
21 - compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
22 or "atmel,sama5d3-pinctrl" or "microchip,sam9x60-pinctrl"
23 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
45 From the datasheet Table 10-2.
83 - atmel,pins: 4 integers array, represents a group of pins mux and config
90 MULTIDRIVE (1 << 1): indicate this pin needs to be configured as multi-drive.
91 Multi-drive is equivalent to open-drain type output.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pinctrl.txt | 4 to share one PAD to several functional blocks. The sharing is done by
10 Please refer to pinctrl-bindings.txt in this directory for details of the
18 such as pull-up, multi drive, etc.
21 - compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
22 or "atmel,sama5d3-pinctrl" or "microchip,sam9x60-pinctrl"
23 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
45 From the datasheet Table 10-2.
83 - atmel,pins: 4 integers array, represents a group of pins mux and config
90 MULTIDRIVE (1 << 1): indicate this pin needs to be configured as multi-drive.
91 Multi-drive is equivalent to open-drain type output.
[all …]
|
| /kernel/linux/linux-5.10/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 | 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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/drivers/phy/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
23 Generic MIPI D-PHY support.
25 Provides a number of helpers a core functions for MIPI D-PHY
47 tristate "APM X-Gene 15Gbps PHY support"
51 This option enables support for APM X-Gene SoC multi-purpose PHY.
62 interface to interact with USB GEN-II and USB 3.x PHY that is part
72 functional modes using gpios and sets the attribute max link
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/ |
| D | glossary.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
51 **Field-programmable Gate Array**
56 See https://en.wikipedia.org/wiki/Field-programmable_gate_array.
65 together make a larger user-facing functional peripheral. For
73 **Inter-Integrated Circuit**
75 A multi-master, multi-slave, packet switched, single-ended,
77 like sub-device hardware components.
79 See http://www.nxp.com/docs/en/user-guide/UM10204.pdf.
113 - :term:`CEC API`;
114 - :term:`Digital TV API`;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/ |
| D | glossary.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
51 **Field-programmable Gate Array**
56 See https://en.wikipedia.org/wiki/Field-programmable_gate_array.
65 together make a larger user-facing functional peripheral. For
73 **Inter-Integrated Circuit**
75 A multi-master, multi-slave, packet switched, single-ended,
77 like sub-device hardware components.
79 See http://www.nxp.com/docs/en/user-guide/UM10204.pdf.
113 - :term:`CEC API`;
114 - :term:`Digital TV API`;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | marvel.rst | 13 ------------
16 - 88F5082
17 - 88F5181
18 - 88F5181L
19 - 88F5182
21 … - Datasheet: http://www.embeddedarm.com/documentation/third-party/MV88F5182-datasheet.pdf
22 …- Programmer's User Guide: http://www.embeddedarm.com/documentation/third-party/MV88F5182-opensour…
23 … - User Manual: http://www.embeddedarm.com/documentation/third-party/MV88F5182-usermanual.pdf
24 - 88F5281
26 …- Datasheet: http://www.ocmodshop.com/images/reviews/networking/qnap_ts409u/marvel_88f5281_data_sh…
[all …]
|
12345678