Home
last modified time | relevance | path

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

12345678910>>...16

/freebsd-src/sys/contrib/device-tree/Bindings/clock/
H A Dmvebu-core-clock.txt4 reading the Sample-At-Reset (SAR) register. The core clock consumer should
8 0 = tclk (Internal Bus clock)
15 0 = tclk (Internal Bus clock)
21 0 = tclk (Internal Bus clock)
27 0 = tclk (Internal Bus clock)
30 3 = hclk (SDRAM Controller Internal Clock)
35 0 = tclk (Internal Bus clock)
41 0 = tclk (Internal Bus clock)
47 0 = tclk (Internal Bus clock)
52 - compatible : shall be one of the following:
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/spi/
H A Dspi-davinci.txt4 Keystone 2 - https://www.ti.com/lit/ug/sprugp2a/sprugp2a.pdf
5 dm644x - https://www.ti.com/lit/ug/sprue32a/sprue32a.pdf
6 OMAP-L138/da830 - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
9 - #address-cells: number of cells required to define a chip select
11 - #size-cells: should be zero.
12 - compatible:
13 - "ti,dm6441-spi" for SPI used similar to that on DM644x SoC family
14 - "ti,da830-spi" for SPI used similar to that on DA8xx SoC family
15 - "ti,keystone-spi" for SPI used similar to that on Keystone2 SoC
17 - reg: Offset and length of SPI controller register space
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/gpio/
H A D8xxx_gpio.txt3 This is for the non-QE/CPM/GUTs GPIO controllers as found on
6 Every GPIO controller node must have #gpio-cells property defined,
7 this information will be used to translate gpio-specifiers.
11 The GPIO module usually is connected to the SoC's internal interrupt
12 controller, see bindings/interrupt-controller/interrupts.txt (the
17 the SoC's internal interrupt controller). See the interrupt controller
18 nodes section in bindings/interrupt-controller/interrupts.txt for
22 - compatible: "fsl,<chip>-gpio" followed by "fsl,mpc8349-gpio"
23 for 83xx, "fsl,mpc8572-gpio" for 85xx, or
24 "fsl,mpc8610-gpio" for 86xx.
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/pinctrl/
H A Dbrcm,iproc-gpio.txt5 - 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
23 - reg:
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/net/dsa/
H A Dlantiq-gswip.txt6 - compatible : "lantiq,xrx200-gswip" for the embedded GSWIP in the
7 xRX200 SoC
8 "lantiq,xrx300-gswip" for the embedded GSWIP in the
9 xRX300 SoC
10 "lantiq,xrx330-gswip" for the embedded GSWIP in the
11 xRX330 SoC
12 - reg : memory range of the GSWIP core registers
21 - compatible : "lantiq,xrx200-mdio" for the MDIO bus inside the GSWIP
22 core of the xRX200 SoC and the PHYs connected to it.
29 - compatible : "lantiq,xrx200-gphy-fw", "lantiq,gphy-fw"
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/rtc/
H A Disil,isl1208.txt8 - "compatible": Should be one of the following:
9 - "isil,isl1208"
10 - "isil,isl1209"
11 - "isil,isl1218"
12 - "isil,isl1219"
13 - "reg": I2C bus address of the device
16 - "interrupt-names": list which may contains "irq" and "evdet"
18 - "interrupts": list of interrupts for "irq" and "evdet"
20 - "isil,ev-evienb": Enable or disable internal pull on EVIN pin
23 Value 0 enables internal pull-up on evin pin, 1 disables it.
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/net/
H A Dfsl-fman.txt5 - FMan Node
6 - FMan Port Node
7 - FMan MURAM Node
8 - FMan dTSEC/XGEC/mEMAC Node
9 - FMan IEEE 1588 Node
10 - FMan MDIO Node
11 - Example
18 Due to the fact that the FMan is an aggregation of sub-engines (ports, MACs,
23 - compatible
32 - cell-index
[all …]
H A Dqcom-emac.txt4 internal PHY. Each device is represented by a device tree node. A phandle
5 connects the MAC node to its corresponding internal phy node. Another
11 - compatible : Should be "qcom,fsm9900-emac".
12 - reg : Offset and length of the register regions for the device
13 - interrupts : Interrupt number used by this controller
14 - mac-address : The 6-byte MAC address. If present, it is the default
16 - internal-phy : phandle to the internal PHY node
17 - phy-handle : phandle to the external PHY node
19 Internal PHY node:
20 - compatible : Should be "qcom,fsm9900-emac-sgmii" or "qcom,qdf2432-emac-sgmii".
[all …]
H A Dmotorcomm,yt8xxx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Sae <frank.sae@motor-comm.com>
13 - $ref: ethernet-phy.yaml#
18 - ethernet-phy-id4f51.e91a
19 - ethernet-phy-id4f51.e91b
21 rx-internal-delay-ps:
24 internal delay (phy-mode is 'rgmii-id' or 'rgmii-rxid') in pico-seconds.
30 tx-internal-delay-ps:
[all …]
H A Dmediatek-net.txt10 - compatible: Should be
11 "mediatek,mt2701-eth": for MT2701 SoC
12 "mediatek,mt7623-eth", "mediatek,mt2701-eth": for MT7623 SoC
13 "mediatek,mt7622-eth": for MT7622 SoC
14 "mediatek,mt7629-eth": for MT7629 SoC
15 "ralink,rt5350-eth": for Ralink Rt5350F and MT7628/88 SoC
16 - reg: Address and length of the register set for the device
17 - interrupts: Should contain the three frame engines interrupts in numeric
19 - clocks: the clock used by the core
20 - clock-names: the names of the clock listed in the clocks property. These are
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/bus/
H A Dmvebu-mbus.txt6 - compatible: Should be set to one of the following:
7 marvell,armada370-mbus
8 marvell,armadaxp-mbus
9 marvell,armada375-mbus
10 marvell,armada380-mbus
11 marvell,kirkwood-mbus
12 marvell,dove-mbus
13 marvell,orion5x-88f5281-mbus
14 marvell,orion5x-88f5182-mbus
15 marvell,orion5x-88f5181-mbus
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/phy/
H A Dphy-mtk-xsphy.txt1 MediaTek XS-PHY binding
2 --------------------------
4 The XS-PHY controller supports physical layer functionality for USB3.1
8 - compatible : should be "mediatek,<soc-model>-xsphy", "mediatek,xsphy",
9 soc-model is the name of SoC, such as mt3611 etc;
10 when using "mediatek,xsphy" compatible string, you need SoC specific
12 - "mediatek,mt3611-xsphy"
14 - #address-cells, #size-cells : should use the same values as the root node
15 - ranges: must be present
18 - reg : offset and length of register shared by multiple U3 ports,
[all …]
H A Dnvidia,tegra194-xusb-padctl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra194-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
15 signals) which connect directly to pins/pads on the SoC package. Each lane
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
[all …]
H A Dfsl,imx8-pcie-phy.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/phy/fsl,imx8-pcie-phy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale i.MX8 SoC series PCIe PHY
10 - Richard Zhu <hongxing.zhu@nxp.com>
13 "#phy-cells":
18 - fsl,imx8mm-pcie-phy
19 - fsl,imx8mp-pcie-phy
27 clock-names:
[all …]
H A Dnvidia,tegra186-xusb-padctl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra186-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
15 signals) which connect directly to pins/pads on the SoC package. Each lane
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/mmc/
H A Dmtk-sd.txt10 - compatible: value should be either of the following.
11 "mediatek,mt8135-mmc": for mmc host ip compatible with mt8135
12 "mediatek,mt8173-mmc": for mmc host ip compatible with mt8173
13 "mediatek,mt8183-mmc": for mmc host ip compatible with mt8183
14 "mediatek,mt8516-mmc": for mmc host ip compatible with mt8516
15 "mediatek,mt6779-mmc": for mmc host ip compatible with mt6779
16 "mediatek,mt2701-mmc": for mmc host ip compatible with mt2701
17 "mediatek,mt2712-mmc": for mmc host ip compatible with mt2712
18 "mediatek,mt7622-mmc": for MT7622 SoC
19 "mediatek,mt7623-mmc", "mediatek,mt2701-mmc": for MT7623 SoC
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/thermal/
H A Dthermal-sensor.yaml1 # SPDX-License-Identifier: (GPL-2.0)
4 ---
5 $id: http://devicetree.org/schemas/thermal/thermal-sensor.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Amit Kucheria <amitk@kernel.org>
20 - thermal-sensor: device that measures temperature, has SoC-specific bindings
21 - cooling-device: device used to dissipate heat either passively or actively
22 - thermal-zones: a container of the following node types used to describe all
25 This binding describes the thermal-sensor.
29 devices may control one or more internal sensors.
[all …]
H A Dthermal.txt15 - thermal sensors: devices which may be used to take temperature
17 - cooling devices: devices which may be used to dissipate heat.
18 - trip points: describe key temperatures at which cooling is recommended. The
20 - cooling maps: used to describe links between trip points and cooling devices;
21 - thermal zones: used to describe thermal data within the hardware;
30 control one or more internal sensors.
33 - #thermal-sensor-cells: Used to provide sensor device specific information
36 with several internal sensors, in order
62 - #cooling-cells: Used to provide cooling device specific information
78 - temperature: An integer indicating the trip temperature level,
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/i2c/
H A Drenesas,i2c.txt1 I2C for R-Car platforms
4 - compatible:
5 "renesas,i2c-r8a7742" if the device is a part of a R8A7742 SoC.
6 "renesas,i2c-r8a7743" if the device is a part of a R8A7743 SoC.
7 "renesas,i2c-r8a7744" if the device is a part of a R8A7744 SoC.
8 "renesas,i2c-r8a7745" if the device is a part of a R8A7745 SoC.
9 "renesas,i2c-r8a77470" if the device is a part of a R8A77470 SoC.
10 "renesas,i2c-r8a774a1" if the device is a part of a R8A774A1 SoC.
11 "renesas,i2c-r8a774b1" if the device is a part of a R8A774B1 SoC.
12 "renesas,i2c-r8a774c0" if the device is a part of a R8A774C0 SoC.
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/media/
H A Drenesas,drif.txt1 Renesas R-Car Gen3 Digital Radio Interface controller (DRIF)
2 ------------------------------------------------------------
4 R-Car Gen3 DRIF is a SPI like receive only slave device. A general
7 +---------------------+ +---------------------+
8 | |-----SCK------->|CLK |
9 | Master |-----SS-------->|SYNC DRIFn (slave) |
10 | |-----SD0------->|D0 |
11 | |-----SD1------->|D1 |
12 +---------------------+ +---------------------+
14 As per datasheet, each DRIF channel (drifn) is made up of two internal
[all …]
/freebsd-src/sys/contrib/device-tree/src/arm/marvell/
H A Darmada-xp-98dx3336.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Device Tree Include file for Marvell 98dx3336 family SoC
7 * Contains definitions specific to the 98dx3236 SoC that are not
11 #include "armada-xp-98dx3236.dtsi"
14 model = "Marvell 98DX3336 SoC";
15 compatible = "marvell,armadaxp-98dx3336", "marvell,armadaxp-98dx3236", "marvell,armada-370-xp";
20 compatible = "marvell,sheeva-v7";
23 clock-latency = <1000000>;
27 soc {
28 internal-regs {
[all …]
H A Darmada-388.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Device Tree Include file for Marvell Armada 388 SoC.
7 * Gregory CLEMENT <gregory.clement@free-electrons.com>
11 * property and the name of the SoC, and add the second SATA host which control
15 #include "armada-385.dtsi"
18 model = "Marvell Armada 388 family SoC";
21 soc {
22 internal-regs {
24 compatible = "marvell,armada-380-ahci";
36 compatible = "marvell,mv88f6828-pinctrl";
H A Darmada-xp-98dx4251.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Device Tree Include file for Marvell 98dx4521 family SoC
7 * Contains definitions specific to the 98dx4521 SoC that are not
11 #include "armada-xp-98dx3236.dtsi"
14 model = "Marvell 98DX4251 SoC";
15 compatible = "marvell,armadaxp-98dx4251", "marvell,armadaxp-98dx3236", "marvell,armada-370-xp";
20 compatible = "marvell,sheeva-v7";
23 clock-latency = <1000000>;
27 soc {
28 internal-regs {
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/media/i2c/
H A Dov2659.txt1 * OV2659 1/5-Inch 2Mp SOC Camera
3 The Omnivision OV2659 is a 1/5-inch SOC camera, with an active array size of
9 - compatible: Must be "ovti,ov2659"
10 - reg: I2C slave address
11 - clocks: reference to the xvclk input clock.
12 - clock-names: should be "xvclk".
13 - link-frequencies: target pixel clock frequency.
16 - powerdown-gpios: reference to the GPIO connected to the pwdn pin, if any.
17 Active high with internal pull down resistor.
18 - reset-gpios: reference to the GPIO connected to the resetb pin, if any.
[all …]
/freebsd-src/sys/contrib/device-tree/Bindings/pci/
H A Dpci-rcar-gen2.txt2 -------------------------
5 AHB. There is one bridge instance per USB port connected to the internal
9 - compatible: "renesas,pci-r8a7742" for the R8A7742 SoC;
10 "renesas,pci-r8a7743" for the R8A7743 SoC;
11 "renesas,pci-r8a7744" for the R8A7744 SoC;
12 "renesas,pci-r8a7745" for the R8A7745 SoC;
13 "renesas,pci-r8a7790" for the R8A7790 SoC;
14 "renesas,pci-r8a7791" for the R8A7791 SoC;
15 "renesas,pci-r8a7793" for the R8A7793 SoC;
16 "renesas,pci-r8a7794" for the R8A7794 SoC;
[all …]

12345678910>>...16