/Linux-v6.1/drivers/gpu/drm/amd/display/dc/dml/ |
D | display_mode_vba.c | 33 * This file is gcc-parsable HW gospel, coming straight from HW engineers. 37 * remain as-is as it provides us with a guarantee from HW that it is correct. 57 bool need_recalculate = memcmp(&mode_lib->soc, &mode_lib->vba.soc, sizeof(mode_lib->vba.soc)) != 0 in dml_get_voltage_level() 58 || memcmp(&mode_lib->ip, &mode_lib->vba.ip, sizeof(mode_lib->vba.ip)) != 0 in dml_get_voltage_level() 59 || num_pipes != mode_lib->vba.cache_num_pipes in dml_get_voltage_level() 60 || memcmp(pipes, mode_lib->vba.cache_pipes, in dml_get_voltage_level() 63 mode_lib->vba.soc = mode_lib->soc; in dml_get_voltage_level() 64 mode_lib->vba.ip = mode_lib->ip; in dml_get_voltage_level() 65 memcpy(mode_lib->vba.cache_pipes, pipes, sizeof(*pipes) * num_pipes); in dml_get_voltage_level() 66 mode_lib->vba.cache_num_pipes = num_pipes; in dml_get_voltage_level() [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/sifive/ |
D | sifive-blocks-ip-versioning.txt | 1 DT compatible string versioning for SiFive open-source IP blocks 4 strings for open-source SiFive IP blocks. HDL for these IP blocks 7 https://github.com/sifive/sifive-blocks 9 IP block-specific DT compatible strings are contained within the HDL, 10 in the form "sifive,<ip-block-name><integer version number>". 14 https://github.com/sifive/sifive-blocks/blob/v1.0/src/main/scala/devices/uart/UART.scala#L43 16 Until these IP blocks (or IP integration) support version 17 auto-discovery, the maintainers of these IP blocks intend to increment 19 interface to these IP blocks changes, or when the functionality of the 20 underlying IP blocks changes in a way that software should be aware of. [all …]
|
/Linux-v6.1/drivers/usb/dwc3/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 10 USB controller based on the DesignWare USB3 IP Core. 64 AM437x use this IP for USB2/3 functionality. 69 tristate "Samsung Exynos SoC Platform" 75 IP inside, say 'Y' or 'M' if you have one such device. 78 tristate "PCIe-based Platforms" 82 If you're using the DesignWare Core IP with a PCIe (but not HAPS 86 tristate "Synopsys PCIe-based HAPS Platforms" 90 If you're using the DesignWare Core IP with a Synopsys PCIe HAPS 117 Support USB2/3 functionality in simple SoC integrations. [all …]
|
/Linux-v6.1/sound/soc/ti/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 34 Say Y or M here if you want to have support for McASP IP found in 36 - daVinci devices 37 - Sitara line of SoCs (AM335x, AM438x, etc) 38 - OMAP4 39 - DRA7x devices 40 - Keystone devices 41 - K3 devices (am654, j721e) 55 Say Y or M here if you want to have support for DMIC IP found in 63 Say Y or M here if you want to have support for McBSP IP found in [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/soc/mediatek/ |
D | pwrap.txt | 7 inside the SoC. The communication between the SoC and the PMIC can 11 IP Pairing 13 on MT8135 the pins of some SoC internal peripherals can be on the PMIC. 16 are marked with "IP Pairing". These are optional on SoCs which do not support 17 IP Pairing 20 - compatible: 21 "mediatek,mt2701-pwrap" for MT2701/7623 SoCs 22 "mediatek,mt6765-pwrap" for MT6765 SoCs 23 "mediatek,mt6779-pwrap" for MT6779 SoCs 24 "mediatek,mt6797-pwrap" for MT6797 SoCs [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/display/ |
D | st,stih4xx.txt | 3 - sti-vtg: video timing generator 5 - compatible: "st,vtg" 6 - reg: Physical base address of the IP registers and length of memory mapped region. 8 - interrupts : VTG interrupt number to the CPU. 9 - st,slave: phandle on a slave vtg 11 - sti-vtac: video timing advanced inter dye communication Rx and TX 13 - compatible: "st,vtac-main" or "st,vtac-aux" 14 - reg: Physical base address of the IP registers and length of memory mapped region. 15 - clocks: from common clock binding: handle hardware IP needed clocks, the 16 number of clocks may depend of the SoC type. [all …]
|
/Linux-v6.1/drivers/net/can/ctucanfd/ |
D | Kconfig | 2 tristate "CTU CAN-FD IP core" if COMPILE_TEST 4 This driver adds support for the CTU CAN FD open-source IP core. 8 is available (https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top). 9 Implementation on Intel FPGA-based PCI Express board is available 10 from project (https://gitlab.fel.cvut.cz/canbus/pcie-ctucanfd) and 11 on Intel SoC from project (https://gitlab.fel.cvut.cz/canbus/intel-soc-ctucanfd). 15 tristate "CTU CAN-FD IP core PCI/PCIe driver" 19 This driver adds PCI/PCIe support for CTU CAN-FD IP core. 22 at https://gitlab.fel.cvut.cz/canbus/pcie-ctucanfd . 25 tristate "CTU CAN-FD IP core platform (FPGA, SoC) driver" [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/net/ |
D | cdns,macb.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Nicolas Ferre <nicolas.ferre@microchip.com> 11 - Claudiu Beznea <claudiu.beznea@microchip.com> 16 - items: 17 - enum: 18 - cdns,at91rm9200-emac # Atmel at91rm9200 SoC 19 - const: cdns,emac # Generic 21 - items: [all …]
|
D | snps,dwc-qos-ethernet.txt | 1 * Synopsys DWC Ethernet QoS IP version 4.10 driver (GMAC) 7 IP block. The IP supports multiple options for bus type, clocking and reset 13 - compatible: One of: 14 - "axis,artpec6-eqos", "snps,dwc-qos-ethernet-4.10" 15 Represents the IP core when integrated into the Axis ARTPEC-6 SoC. 16 - "nvidia,tegra186-eqos", "snps,dwc-qos-ethernet-4.10" 17 Represents the IP core when integrated into the NVIDIA Tegra186 SoC. 18 - "snps,dwc-qos-ethernet-4.10" 20 "axis,artpec6-eqos", "snps,dwc-qos-ethernet-4.10". It is supported to be 22 - reg: Address and length of the register set for the device [all …]
|
/Linux-v6.1/Documentation/gpu/amdgpu/ |
D | driver-core.rst | 9 "IPs" (Intellectual Property blocks). Each IP encapsulates certain 13 the initialization and operation of each IP. There are also a bunch 15 Those end up getting lumped into the common stuff in the soc files. 16 The soc files (e.g., vi.c, soc15.c nv.c) contain code for aspects of 17 the SoC itself rather than specific IPs. E.g., things like GPU resets 18 and register access functions are SoC dependent. 32 This was a dedicated IP on older pre-vega chips, but has since 43 their interrupts into this IP and it aggregates them into a set of 48 This handles security policy for the SoC and executes trusted 53 SoC. The driver interacts with it to control power management [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/rtc/ |
D | rtc-omap.txt | 4 - compatible: 5 - "ti,da830-rtc" - for RTC IP used similar to that on DA8xx SoC family. 6 - "ti,am3352-rtc" - for RTC IP used similar to that on AM335x SoC family. 7 This RTC IP has special WAKE-EN Register to enable 11 - "ti,am4372-rtc" - for RTC IP used similar to that on AM437X SoC family. 12 - reg: Address range of rtc register set 13 - interrupts: rtc timer, alarm interrupts in order 16 - system-power-controller: whether the rtc is controlling the system power 18 - clocks: Any internal or external clocks feeding in to rtc 19 - clock-names: Corresponding names of the clocks [all …]
|
/Linux-v6.1/drivers/pci/controller/dwc/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 29 Enables support for the PCIe controller in the DRA7xx SoC to work in 32 host-specific features PCI_DRA7XX_HOST must be selected and in order 33 to enable device-specific features PCI_DRA7XX_EP must be selected. 44 Enables support for the PCIe controller in the DRA7xx SoC to work in 47 host-specific features PCI_DRA7XX_HOST must be selected and in order 48 to enable device-specific features PCI_DRA7XX_EP must be selected. 55 bool "Platform bus based DesignWare PCIe Controller - Host mode" 60 Enables support for the PCIe controller in the Designware IP to 62 Designware IP. [all …]
|
/Linux-v6.1/arch/arm/mach-omap2/ |
D | prm_common.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * OMAP2+ common Power & Reset Management (PRM) IP block functions 6 * Tero Kristo <t-kristo@ti.com> 24 #include <linux/clk-provider.h> 27 #include "soc.h" 45 * actual amount of memory needed for the SoC 64 /* prm_base: base virtual address of the PRM IP block */ 70 * prm_ll_data: function pointers to SoC-specific implementations of 86 for (i = 0; i < prcm_irq_setup->nr_regs; i++) { in omap_prcm_events_filter_priority() 88 events[i] & prcm_irq_setup->priority_mask[i]; in omap_prcm_events_filter_priority() [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/pinctrl/ |
D | brcm,iproc-gpio.txt | 5 - compatible: 6 "brcm,iproc-gpio" for the generic iProc based GPIO controller IP that 7 supports full-featured pinctrl and GPIO functions used in various iProc 10 May contain an SoC-specific compatibility string to accommodate any 11 SoC-specific features 13 "brcm,cygnus-ccm-gpio", "brcm,cygnus-asiu-gpio", or 14 "brcm,cygnus-crmu-gpio" for Cygnus SoCs 16 "brcm,iproc-nsp-gpio" for the iProc NSP SoC that has drive strength support 19 "brcm,iproc-stingray-gpio" for the iProc Stingray SoC that has the general 20 pinctrl support completely disabled in this IP block. In Stingray, a [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/clock/ti/ |
D | dra7-atl.txt | 1 Device Tree Clock bindings for ATL (Audio Tracking Logic) of DRA7 SoC. 3 The ATL IP is used to generate clock to be used to synchronize baseband and 4 audio codec. A single ATL IP provides four ATL clock instances sharing the same 7 signals - can compensate the drift between the two ws signal. 10 internally within the SoC or external components) two sets of bindings is needed: 16 Since the clock instances are part of a single IP this binding is used as a node 17 for the DT clock tree, the IP driver is needed to handle the actual configuration 18 of the IP. 20 [1] Documentation/devicetree/bindings/clock/clock-bindings.txt 23 - compatible : shall be "ti,dra7-atl-clock" [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/media/ |
D | samsung-fimc.txt | 1 Samsung S5P/Exynos SoC Camera Subsystem (FIMC) 2 ---------------------------------------------- 4 The S5P/Exynos SoC Camera subsystem comprises of multiple sub-devices 6 the S5P SoCs series known as CAMIF), MIPI CSIS, FIMC-LITE and FIMC-IS (ISP). 8 The sub-subdevices are defined as child nodes of the common 'camera' node which 10 any single sub-device, like common camera port pins or the CAMCLK clock outputs 11 for external image sensors attached to an SoC. 14 -------------------- 18 - compatible: must be "samsung,fimc", "simple-bus" 19 - clocks: list of clock specifiers, corresponding to entries in [all …]
|
D | s5p-mfc.txt | 3 Multi Format Codec (MFC) is the IP present in Samsung SoCs which 10 - compatible : value should be either one among the following 11 (a) "samsung,mfc-v5" for MFC v5 present in Exynos4 SoCs 12 (b) "samsung,mfc-v6" for MFC v6 present in Exynos5 SoCs 13 (c) "samsung,mfc-v7" for MFC v7 present in Exynos5420 SoC 14 (d) "samsung,mfc-v8" for MFC v8 present in Exynos5800 SoC 15 (e) "samsung,exynos5433-mfc" for MFC v8 present in Exynos5433 SoC 16 (f) "samsung,mfc-v10" for MFC v10 present in Exynos7880 SoC 18 - reg : Physical base address of the IP registers and length of memory 21 - interrupts : MFC interrupt number to the CPU. [all …]
|
/Linux-v6.1/drivers/irqchip/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 118 tristate "Broadcom STB 7038-style L1/L2 interrupt controller driver" 126 tristate "Broadcom STB 7120-style L2 interrupt controller driver" 213 bool "J-Core integrated AIC" if COMPILE_TEST 217 Support for the J-Core integrated AIC. 228 interrupt pins, as found on SH/R-Mobile and R-Car Gen1 SoCs. 231 bool "Renesas R-Mobile APE6, R-Car Gen{2,3} and RZ/G{1,2} IRQC support" if COMPILE_TEST 236 devices, as found on R-Mobile APE6, R-Car Gen{2,3} and RZ/G{1,2} SoCs. 246 bool "Renesas RZ/G2L (and alike SoC) IRQC support" if COMPILE_TEST 250 Enable support for the Renesas RZ/G2L (and alike SoC) Interrupt Controller [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/i2c/ |
D | opencores,i2c-ocores.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/i2c/opencores,i2c-ocores.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Peter Korsgaard <peter@korsgaard.com> 11 - Andrew Lunn <andrew@lunn.ch> 14 - $ref: /schemas/i2c/i2c-controller.yaml# 19 - items: 20 - enum: 21 - sifive,fu740-c000-i2c # Opencore based IP block FU740-C000 SoC [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/mmc/ |
D | marvell,xenon-sdhci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/mmc/marvell,xenon-sdhci.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 mmc-controller.yaml and the properties used by the Xenon implementation. 13 Multiple SDHCs might be put into a single Xenon IP, to save size and cost. 20 - Ulf Hansson <ulf.hansson@linaro.org> 25 - enum: 26 - marvell,armada-cp110-sdhci 27 - marvell,armada-ap806-sdhci [all …]
|
/Linux-v6.1/drivers/fpga/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 29 tristate "Altera Partial Reconfiguration IP Core" 31 Core driver support for Altera Partial Reconfiguration IP component 34 tristate "Platform support of Altera Partial Reconfiguration IP Core" 37 Platform driver support for Altera Partial Reconfiguration IP 52 FPGA manager driver support for Arria-V, Cyclone-V, Stratix-V, 62 tristate "Intel Stratix10 SoC FPGA Manager" 65 FPGA manager driver support for the Intel Stratix10 SoC. 88 tristate "Technologic Systems TS-73xx SBC FPGA Manager" 92 present on the TS-73xx SBC boards. [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/spi/ |
D | brcm,spi-bcm-qspi.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/spi/brcm,spi-bcm-qspi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Kamal Dasu <kdasu.kdev@gmail.com> 11 - Rafał Miłecki <rafal@milecki.pl> 15 BRCMSTB (BCM7XXX), Cygnus, NSP and NS2. The Broadcom Master SPI hw IP consits 18 BSPI : Broadcom SPI in combination with the MSPI hw IP provides acceleration 20 io with 3-byte and 4-byte addressing support. 22 Supported Broadcom SoCs have one instance of MSPI+BSPI controller IP. [all …]
|
/Linux-v6.1/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. 60 :term:`SPI` device, or an :term:`IP Block` inside an 61 :term:`SoC` or :term:`FPGA`. 65 together make a larger user-facing functional peripheral. For 66 instance, the :term:`SoC` :term:`ISP` :term:`IP Block` 73 **Inter-Integrated Circuit** 75 A multi-master, multi-slave, packet switched, single-ended, 77 like sub-device hardware components. [all …]
|
/Linux-v6.1/drivers/usb/musb/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 3 # USB Dual Role (OTG-ready) Controller Drivers 7 # (M)HDRC = (Multipoint) Highspeed Dual-Role Controller 14 controller based on the Mentor Graphics silicon IP. Then 19 Texas Instruments families using this IP include DaVinci 22 Allwinner SoCs using this IP include A10, A13, A20, ... 27 module will be called "musb-hdrc". 80 tristate "DA8xx/OMAP-L1x" 127 tristate "Microchip PolarFire SoC platforms" 132 Say Y here to enable support for USB on Microchip's PolarFire SoC. [all …]
|
/Linux-v6.1/drivers/staging/media/imx/ |
D | TODO | 2 - The Frame Interval Monitor could be exported to v4l2-core for 5 - The CSI subdevice parses its nearest upstream neighbor's device-tree 13 2020-06: g_mbus has been removed in favour of the get_mbus_config pad 17 - This media driver supports inheriting V4L2 controls to the 21 removed, userspace should use the subdev-based userspace API instead. 23 - Similarly to the legacy control handling, legacy format handling where 27 - i.MX7: all of the above, since it uses the imx media core 29 - i.MX7: use Frame Interval Monitor 31 - imx7-media-csi: Restrict the supported formats list to the SoC version. 39 As the imx7 CSI bridge can be interfaced with different IP blocks depending on [all …]
|