Home
last modified time | relevance | path

Searched +full:soc +full:- +full:specific (Results 1 – 25 of 1008) sorted by relevance

12345678910>>...41

/openbmc/linux/drivers/gpu/drm/rockchip/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
16 Choose this option if you have a Rockchip soc chipset.
20 IP found on the SoC.
38 bool "Rockchip specific extensions for Analogix DP driver"
43 This selects support for Rockchip SoC specific extensions
45 on RK3288 or RK3399 based SoC, you should select this option.
53 This selects support for Rockchip SoC specific extensions
55 RK3399 based SoC, you should select this
59 bool "Rockchip specific extensions for Synopsys DW HDMI"
61 This selects support for Rockchip SoC specific extensions
[all …]
/openbmc/u-boot/include/
H A Dspl_gpio.h1 /* SPDX-License-Identifier: GPL-2.0+ */
4 * typically the SoC GPIO banks.
15 * The functions listed here should be implemented in the SoC GPIO driver.
16 * They correspond to the normal GPIO API (asm-generic/gpio.h). The GPIO
17 * number is encoded in an unsigned int by an SoC-specific means. Pull
18 * values are also SoC-specific.
24 * often specific to a particular SoC generation. This allows the GPIO
30 * encoding is SoC-specific.
34 * spl_gpio_set_pull() - Set the pull up/down state of a GPIO
37 * @gpio: GPIO to adjust (SoC-specific)
[all …]
/openbmc/linux/drivers/net/ethernet/stmicro/stmmac/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "STMicroelectronics Multi-Gigabit Ethernet driver"
34 This selects the platform specific bus support for the stmmac driver.
45 tristate "Support for snps,dwc-qos-ethernet.txt DT binding."
50 Support for chips using the snps,dwc-qos-ethernet.txt DT binding.
57 platform specific code to function or is using platform
67 This selects the Anarion SoC glue layer support for the stmmac driver.
89 This selects the IPQ806x SoC glue layer support for the stmmac
91 acceleration features available on this SoC. Network devices
92 will behave like standard non-accelerated ethernet interfaces.
[all …]
/openbmc/linux/Documentation/process/
H A Dmaintainer-soc.rst1 .. SPDX-License-Identifier: GPL-2.0
4 SoC Subsystem
8 --------
10 The SoC subsystem is a place of aggregation for SoC-specific code.
13 * devicetrees for 32- & 64-bit ARM and RISC-V
14 * 32-bit ARM board files (arch/arm/mach*)
15 * 32- & 64-bit ARM defconfigs
16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit
17 ARM, RISC-V and Loongarch
19 These "SoC-specific drivers" do not include clock, GPIO etc drivers that have
[all …]
/openbmc/linux/drivers/pci/controller/dwc/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 menu "DesignWare-based PCIe controllers"
27 required only for DT-based platforms. ACPI platforms with the
38 and therefore the driver re-uses the DesignWare core functions to
45 bool "Axis ARTPEC-6 PCIe controller (host mode)"
51 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
55 bool "Axis ARTPEC-6 PCIe controller (endpoint mode)"
61 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
65 tristate "Baikal-T1 PCIe controller"
70 Enables support for the PCIe controller in the Baikal-T1 SoC to work
[all …]
/openbmc/linux/arch/arm/mach-omap2/
H A Dcm.h1 /* SPDX-License-Identifier: GPL-2.0-only */
5 * Copyright (C) 2007-2009, 2012 Texas Instruments, Inc.
6 * Copyright (C) 2007-2009 Nokia Corporation
25 #include "prcm-common.h"
45 * struct cm_ll_data - fn ptrs to per-SoC CM function implementations
46 * @split_idlest_reg: ptr to the SoC CM-specific split_idlest_reg impl
47 * @wait_module_ready: ptr to the SoC CM-specific wait_module_ready impl
48 * @wait_module_idle: ptr to the SoC CM-specific wait_module_idle impl
49 * @module_enable: ptr to the SoC CM-specific module_enable impl
50 * @module_disable: ptr to the SoC CM-specific module_disable impl
[all …]
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
H A Dmarvell,mvebu-pinctrl.txt1 * Marvell SoC pinctrl core driver for mpp
3 The pinctrl driver enables Marvell SoCs to configure the multi-purpose pins
4 (mpp) to a specific function. For each SoC family there is a SoC specific
7 Please refer to pinctrl-bindings.txt in this directory for details of the
11 A Marvell SoC pin configuration node is a node of a group of pins which can
12 be used for a specific device or function. Each node requires one or more
16 - compatible: "marvell,<soc>-pinctrl"
17 Please refer to each marvell,<soc>-pinctrl.txt binding doc for supported SoCs.
20 - marvell,pins: string array of mpp pins or group of pins to be muxed.
21 - marvell,function: string representing a function to mux to for all
[all …]
H A Dfsl,imx-pinctrl.txt10 Please refer to pinctrl-bindings.txt in this directory for details of the
15 used for a specific device or function. This node represents both mux and config
18 such as pull-up, open drain, drive strength, etc.
21 - compatible: "fsl,<soc>-iomuxc"
22 Please refer to each fsl,<soc>-pinctrl.txt binding doc for supported SoCs.
25 - fsl,pins: each entry consists of 6 integers and represents the mux and config
28 imx*-pinfunc.h under device tree source folder. The last integer CONFIG is
29 the pad setting value like pull-up on this pin. And that's why fsl,pins entry
41 Please refer to each fsl,<soc>-pinctrl,txt binding doc for SoC specific part
45 Some requirements for using fsl,imx-pinctrl binding:
[all …]
/openbmc/linux/Documentation/devicetree/bindings/mmc/
H A Dbluefield-dw-mshc.txt1 * Mellanox Bluefield SoC specific extensions to the Synopsys Designware
4 Read synopsys-dw-mshc.txt for more details
7 a SoC with storage medium such as eMMC or SD/MMC cards. This file documents
9 by synopsys-dw-mshc.txt and the properties used by the Mellanox Bluefield SoC
10 specific extensions to the Synopsys Designware Mobile Storage Host Controller.
15 - "mellanox,bluefield-dw-mshc": for controllers with Mellanox Bluefield SoC
16 specific extensions.
20 /* Mellanox Bluefield SoC MMC */
22 compatible = "mellanox,bluefield-dw-mshc";
25 fifo-depth = <0x100>;
[all …]
/openbmc/linux/drivers/pinctrl/nomadik/
H A Dpinctrl-abx500.h1 /* SPDX-License-Identifier: GPL-2.0 */
34 * struct abx500_function - ABx500 pinctrl mux function
46 * struct abx500_pingroup - describes a ABx500 pin group
47 * @name: the name of this specific pin group
49 * from the driver-local pin enumeration space
73 #define UNUSED -1
85 * function between the ABx500 SOC family when using
109 * struct abx500_gpio_irq_cluster - indicates GPIOs which are interrupt
116 * read-in values into the cluster information table
126 * struct abx500_pinrange - map pin numbers to GPIO offsets
[all …]
/openbmc/linux/Documentation/devicetree/bindings/sifive/
H A Dsifive-blocks-ip-versioning.txt1 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
17 auto-discovery, the maintainers of these IP blocks intend to increment
25 upstream sifive-blocks commits. It is expected that most drivers will
26 match on these IP block-specific compatible strings.
28 DT data authors, when writing data for a particular SoC, should
[all …]
/openbmc/linux/Documentation/arch/arm/spear/
H A Doverview.rst6 ------------
11 The ST Microelectronics SPEAr range of ARM9/CortexA9 System-on-Chip CPUs are
19 - SPEAr3XX (3XX SOC series, based on ARM9)
20 - SPEAr300 (SOC)
21 - SPEAr300 Evaluation Board
22 - SPEAr310 (SOC)
23 - SPEAr310 Evaluation Board
24 - SPEAr320 (SOC)
25 - SPEAr320 Evaluation Board
26 - SPEAr6XX (6XX SOC series, based on ARM9)
[all …]
/openbmc/linux/drivers/ufs/host/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0+
5 # Copyright (C) 2011-2013 Samsung India Software Operations
45 This selects the Cadence-specific additions to UFSHCD platform driver.
58 tristate "QCOM specific hooks to UFS controller platform driver"
64 This selects the QCOM specific additions to UFSHCD platform driver.
65 UFS host on QCOM needs some vendor specific configuration before
67 specific registers.
73 tristate "Mediatek specific hooks to UFS controller platform driver"
79 This selects the Mediatek specific additions to UFSHCD platform driver.
80 UFS host on Mediatek needs some vendor specific configuration before
[all …]
/openbmc/linux/drivers/thermal/samsung/
H A Dexynos_tmu.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * exynos_tmu.c - Samsung Exynos TMU (Thermal Management Unit)
25 #include <dt-bindings/thermal/thermal_exynos.h>
43 /* Exynos3250 specific registers */
46 /* Exynos4210 specific registers */
50 /* Exynos5250, Exynos4412, Exynos3250 specific registers */
73 /* Exynos5260 specific */
79 /* Exynos4412 specific */
83 /* Exynos5433 specific registers */
106 /* Exynos7 specific registers */
[all …]
/openbmc/u-boot/
H A Dconfig.mk1 # SPDX-License-Identifier: GPL-2.0+
3 # (C) Copyright 2000-2013
36 SOC := $(CONFIG_SYS_SOC:"%"=%)
40 # so calculate CPUDIR before including ARCH/SOC/CPU config.mk files.
42 # CPU-specific code.
46 sinclude $(srctree)/$(CPUDIR)/config.mk # include CPU specific rules
48 ifdef SOC
49 sinclude $(srctree)/$(CPUDIR)/$(SOC)/config.mk # include SoC specific rules
59 sinclude $(srctree)/board/$(BOARDDIR)/config.mk # include board specific rules
63 PLATFORM_CPPFLAGS += -finstrument-functions -DFTRACE
[all …]
/openbmc/linux/Documentation/sound/soc/
H A Doverview.rst2 ALSA SoC Layer Overview
6 provide better ALSA support for embedded system-on-chip processors (e.g.
8 subsystem there was some support in the kernel for SoC audio, however it
9 had some limitations:-
11 * Codec drivers were often tightly coupled to the underlying SoC
12 CPU. This is not ideal and leads to code duplication - for example,
13 Linux had different wm8731 drivers for 4 different SoC platforms.
18 machine specific code to re-route audio, enable amps, etc., after such an
31 features :-
36 * Easy I2S/PCM audio interface setup between codec and SoC. Each SoC
[all …]
/openbmc/linux/drivers/mmc/host/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
94 implements a hardware byte swapper using a 32-bit datum.
123 disabled, it will steal the MMC cards away - rendering them
135 identified by ACPI Compatibility ID PNP0D40 or specific
161 (SDHCI). This hardware is found e.g. in Xilinx' Zynq SoC.
243 tristate "SDHCI OF support for the MCHP Sparx5 SoC"
248 found in the MCHP Sparx5 SoC.
250 If you have a Sparx5 SoC with this interface, say Y or M here.
295 tristate "SDHCI support on Marvell's Dove SoC"
301 Marvell's Dove SoC.
[all …]
/openbmc/linux/Documentation/devicetree/
H A Dusage-model.rst1 .. SPDX-License-Identifier: GPL-2.0
44 ----------
56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
57 and 64-bit support, the decision was made to require DT support on all
61 blob without requiring a real Open Firmware implementation. U-Boot,
66 existing non-DT aware firmware.
74 -------------
79 -------------------
88 per-machine hard coded selections.
101 ---------------------------
[all …]
/openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A Dmpic.txt14 - compatible
22 - reg
24 Value type: <prop-encoded-array>
29 - interrupt-controller
35 - #interrupt-cells
39 specifiers do not contain the interrupt-type or type-specific
42 - #address-cells
47 - pic-no-reset
53 configuration registers to a sane state-- masked or
60 - big-endian
[all …]
/openbmc/linux/Documentation/devicetree/bindings/arm/marvell/
H A Dmarvell,orion5x.txt1 Marvell Orion SoC Family Device Tree Bindings
2 ---------------------------------------------
4 Boards with a SoC of the Marvell Orion family, eg 88f5181
9 In addition, the above compatible shall be extended with the specific
10 SoC. Currently known SoC compatibles are:
12 "marvell,orion5x-88f5181"
13 "marvell,orion5x-88f5182"
15 And in addition, the compatible shall be extended with the specific
21 "lacie,ethernet-disk-mini-v2"
22 "lacie,d2-network"
[all …]
/openbmc/linux/drivers/pinctrl/mvebu/
H A Dpinctrl-mvebu.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
6 * Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
13 * struct mvebu_mpp_ctrl_data - private data for the mpp ctrl operations
29 * struct mvebu_mpp_ctrl - describe a mpp control
39 * internal function, inside the SoC. Each muxable unit can be switched
44 * specific mode. The optional mpp_gpio_req/_dir functions can be used
62 * struct mvebu_mpp_ctrl_setting - describe a mpp ctrl setting
64 * @name: ctrl setting name, e.g. uart2, spi0 - unique per mpp_mode
69 * A ctrl_setting describes a specific internal mux function that a mpp pin
71 * register for common mpp pin configuration registers on MVEBU. SoC specific
[all …]
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/
H A D0035-corstone1000-purge-U-Boot-specific-DT-nodes.patch4 Subject: [PATCH] corstone1000: purge U-Boot specific DT nodes
6 Remove U-Boot specific DT nodes before passing the DT to Linux
8 This is needed to pass SystemReady IR 2.0 dt-schema tests
10 Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>
11 Upstream-Status: Pending [RFC: https://lore.kernel.org/u-boot/aca7e6fa-2dec-a7c5-e47e-84c5ffa6f9b7@…
12 ---
16 diff --git a/board/armltd/corstone1000/corstone1000.c b/board/armltd/corstone1000/corstone1000.c
18 --- a/board/armltd/corstone1000/corstone1000.c
20 @@ -9,6 +9,7 @@
24 +#include <dt-structs.h>
[all …]
/openbmc/u-boot/arch/arm/mach-aspeed/
H A DKconfig13 prompt "Aspeed SoC select"
18 bool "Support Aspeed AST2400 SoC"
21 The Aspeed AST2400 is a ARM-based SoC with arm926ejs CPU.
26 bool "Support Aspeed AST2500 SoC"
30 The Aspeed AST2500 is a ARM-based SoC with arm1176 CPU.
35 bool "Support Aspeed AST2600 SoC"
43 The Aspeed AST2600 is a ARM-based SoC with Cortex-A7 CPU.
54 absolutely required for a specific system or for debugging
60 bool "Enable built-in AST2x00 Super I/O hardware"
63 The Aspeed AST2400 and AST2500 include a built-in Super I/O
[all …]
/openbmc/linux/Documentation/devicetree/bindings/rtc/
H A Disil,isl12057.txt8 ("wakeup-source") to handle the specific use-case found
9 on at least three in-tree users of the chip (NETGEAR ReadyNAS 102, 104
10 and 2120 ARM-based NAS); On those devices, the IRQ#2 pin of the chip
12 to the SoC but to a PMIC. It allows the device to be powered up when
14 get access to the 'wakealarm' sysfs entry, this specific property can
15 be set when the IRQ#2 pin of the chip is not connected to the SoC but
20 - "compatible": must be "isil,isl12057"
21 - "reg": I2C bus address of the device
25 - "wakeup-source": mark the chip as a wakeup source, independently of
26 the availability of an IRQ line connected to the SoC.
[all …]
/openbmc/u-boot/doc/
H A DREADME.fec_mxc1 U-Boot config options used in fec_mxc.c
4 Selects fec_mxc.c to be compiled into u-boot. Can read out the
5 ethaddr from the SoC eFuses (see below).
11 Defaults to MII100 for 100 Base-tx.
12 RGMII selects 1000 Base-tx reduced pin count interface.
13 RMII selects 100 Base-tx reduced pin count interface.
18 This should not be specified by a board file. It is cpu specific.
24 Relevant only if PHYLIB not used. Skips auto-negotiation restart.
32 phy. This is usefull if there is a direct MAC <-> MAC connection, for
34 ethernet-switch.
[all …]

12345678910>>...41