一、Linux設(shè)備樹的起源
在Linux 2.6中,arch/arm/plat-xxx和arch/arm/mach-xxx中充斥著大量的垃圾代碼,相當(dāng)多數(shù)的代碼只是在描述板級(jí)細(xì)節(jié),而這些板級(jí)細(xì)節(jié)對(duì)于內(nèi)核來講,不過是垃圾,如板上的platform設(shè)備、resource、i2c_board_info、spi_board_info以及各種硬件platform_data。
在Linux3.x版本后,arch/arm/plat-xxx和arch/arm/mach-xxx中,描述板級(jí)細(xì)節(jié)的代碼(比如platform_device、i2c_board_info等)被大量取消,取而代之的是設(shè)備樹,其目錄位于
arch/arm/boot/dts。設(shè)備樹最早用于PowerPC等其他體系架構(gòu),后來應(yīng)用到ARM架構(gòu)。
二、設(shè)備樹原理
1.DTS的加載過程
- 首先用戶要了解硬件配置和系統(tǒng)運(yùn)行參數(shù),并把這些信息組織成Device Tree source file。
- 通過DTC(Device Tree Compiler),可以將這些適合人類閱讀的Device Tree source file變成適合機(jī)器處理的Device Tree binary file(也叫DTB,device tree blob)。
- 在系統(tǒng)啟動(dòng)的時(shí)候,boot program(例如:firmware、bootloader)可以將保存在flash中的DTB copy到內(nèi)存(或通過bootloader的交互式命令加載DTB,或者firmware可以探測(cè)到device的信息,組織成DTB保存在內(nèi)存中),并把DTB的起始地址傳遞給client program(例如OS kernel,bootloader或者其他特殊功能的程序)。對(duì)于計(jì)算機(jī)系統(tǒng)(computer system),一般是firmware->bootloader->OS,對(duì)于嵌入式系統(tǒng),一般是bootloader->OS。
- 本質(zhì)上,Device Tree改變了原來用hardcode方式將HW 配置信息嵌入到內(nèi)核代碼的方法,改用bootloader傳遞一個(gè)DB的形式。
2.DTS的描述信息
- Device Tree由一系列被命名的結(jié)點(diǎn)(node)和屬性(property)組成,而結(jié)點(diǎn)本身可包含子結(jié)點(diǎn)。所謂屬性,其實(shí)就是成對(duì)出現(xiàn)的name和value。在Device Tree中,可描述的信息包括(原先這些信息大多被hard code到kernel中):
- CPU的數(shù)量和類別
- 內(nèi)存基地址和大小
- 總線和橋
- 外設(shè)連接
- 中斷控制器和中斷使用情況
- GPIO控制器和GPIO使用情況
- Clock控制器和Clock使用情況
注意:
對(duì)于可以動(dòng)態(tài)探測(cè)到的設(shè)備是不需要描述的,例如USB device。
一個(gè)SoC可能對(duì)應(yīng)多個(gè)多個(gè)產(chǎn)品和電路板,勢(shì)必這些.dts文件需包含許多共同的部分,Linux內(nèi)核為了簡化,把SoC公用的部分或者多個(gè)machine共同的部分一般提煉為.dtsi,類似于C語言的頭文件。
三、設(shè)備樹常見概念
DT : Device Tree
FDT : Flattened DeviceTree
OF : Open Firmware
DTS : Device Tree Source
DTSI : Device Tree Source Include
DTB : Device Tree Blob
DTC : Device Tree Compiler
1.DTS的組成結(jié)構(gòu)
- 1個(gè)root結(jié)點(diǎn)"/"
- root結(jié)點(diǎn)下面含一系列子結(jié)點(diǎn)
- 子結(jié)點(diǎn)下又含有一系列子結(jié)點(diǎn)
- 各結(jié)點(diǎn)都有一系列屬性,屬性類型有
- 空屬性:empty-property
- 字符串屬性:string-property
- 字符串列表屬性:string-list-property
- Cells(u32整型)屬性:cell-property
- 二進(jìn)制數(shù)屬性:binary-property
2.快速編譯設(shè)備樹---DTC (device tree compiler)
- 將.dts編譯為.dtb的工具
- DTC的源代碼位于內(nèi)核的scripts/dtc目錄,在Linux內(nèi)核使能了Device Tree的情況下,編譯內(nèi)核的時(shí)候主機(jī)工具dtc會(huì)被編譯出來
- 在Linux內(nèi)核的arch/arm/boot/dts/Makefile中,描述了當(dāng)某種SoC被選中后,哪些.dtb文件會(huì)被編譯出來,如與EXYNOS對(duì)應(yīng)的.dtb包括:
dtb-$(CONFIG_ARCH_EXYNOS) += exynos4210-origen.dtb \
exynos4210-smdkv310.dtb \
exynos4412-origen.dtb \
- 我們可以單獨(dú)編譯Device Tree文件。當(dāng)我們?cè)贚inux內(nèi)核下運(yùn)行make dtbs時(shí),若我們之前選擇了ARCH_EXYNOS,上述.dtb都會(huì)由對(duì)應(yīng)的.dts編譯出來
- DTC除了可以編譯.dts文件以外,其實(shí)也可以“反匯編”.dtb文件為.dts文件,其指令格式為:
./scripts/dtc/dtc -I dtb -O dts -o xxx.dts arch/arm/boot/dts/xxx.dtb
3.開發(fā)固件設(shè)備樹---Open Firmware Device Tree
- Device Tree可以描述的信息包括CPU的數(shù)量和類別、內(nèi)存基地址和大小、總線和橋、外設(shè)連接、中斷控制器和中斷使用情況、GPIO控制器和GPIO使用情況、Clock控制器和Clock使用情況。
- 設(shè)備樹信息被保存在一個(gè)ASCII 文本文件中,適合人類的閱讀習(xí)慣,類似于xml文件, 在ARM Linux中,一個(gè).dts文件對(duì)應(yīng)一個(gè)ARM的machine放置在內(nèi)核的
arch/arm/boot/dts/ - 設(shè)備樹是一種數(shù)據(jù)結(jié)構(gòu),用于描述設(shè)備信息的語言,具體而言,是用于操作系統(tǒng)中描述硬件,使得不需要對(duì)設(shè)備的信息進(jìn)行硬編碼(hard code)
- Device Tree由一系列被命名的結(jié)點(diǎn)(node)和屬性(property)組成,而結(jié)點(diǎn)本身可包含子結(jié)點(diǎn)。所謂屬性,其實(shí)就是成對(duì)出現(xiàn)的name和value
- 設(shè)備樹源文件dts被編譯成dtb二進(jìn)制文件,在bootloader運(yùn)行時(shí)傳遞給操作系統(tǒng),操作系統(tǒng)對(duì)其進(jìn)行解析展開(Flattened),從而產(chǎn)生一個(gè)硬件設(shè)備的拓?fù)鋱D有了這個(gè)拓?fù)鋱D,在編程的過程中可以直接通過系統(tǒng)提供的接口獲取到設(shè)備樹中的節(jié)點(diǎn)和屬性信息
四、設(shè)備樹語法
1.節(jié)點(diǎn)node
- 節(jié)點(diǎn)名稱:每個(gè)節(jié)點(diǎn)必須有一個(gè)“<名稱>[@<設(shè)備地址>]”形式的名字:
<名稱> 就是一個(gè)不超過31位的簡單 ascii 字符串,節(jié)點(diǎn)的命名應(yīng)該根據(jù)它所體現(xiàn)的是什么樣的設(shè)備。 - <設(shè)備地址>用來訪問該設(shè)備的主地址,并且該地址也在節(jié)點(diǎn)的 reg 屬性中列出,同級(jí)節(jié)點(diǎn)命名必須是唯一的,但只要地址不同,多個(gè)節(jié)點(diǎn)也可以使用一樣的通用名稱,當(dāng)然設(shè)備地址也是可選的,可以有也可以沒有
- 樹中每個(gè)表示一個(gè)設(shè)備的節(jié)點(diǎn)都需要一個(gè) compatible 屬性
1)節(jié)點(diǎn)名稱name
- name描述設(shè)備類型,比如網(wǎng)口宜用ethernet;如果有地址,則用@指定地址
<name>[@<unit-address>]
舉例:
cpus {}
serial@101F2000 { }
ethernet@0,0 {}
2.屬性property
- 簡單的鍵-值對(duì),它的值可以為空或者包含一個(gè)任意字節(jié)流。雖然數(shù)據(jù)類型并沒有編碼進(jìn)數(shù)據(jù)結(jié)構(gòu),但在設(shè)備樹源文件中任有幾個(gè)基本的數(shù)據(jù)表示形式:
- 文本字符串(無結(jié)束符)可以用雙引號(hào)表示:
string-property = "a string" - Cells是 32 位無符號(hào)整數(shù),用尖括號(hào)限定:
cell-property = <0xbeef 123 0xabcd1234> - 二進(jìn)制數(shù)據(jù)用方括號(hào)限定:
binary-property = [01 23 45 67]; - 不同表示形式的數(shù)據(jù)可以使用逗號(hào)連在一起:
mixed-property = "a string", [01 23 45 67], <0x12345678>; - 逗號(hào)也可用于創(chuàng)建字符串列表:
string-list = "red fish", "blue fish";
- 文本字符串(無結(jié)束符)可以用雙引號(hào)表示:
1)compatible屬性
- 指定了系統(tǒng)的名稱,是一個(gè)字符串列表,它包含了一個(gè)“<制造商>,<型號(hào)>”形式的字符串。重要的是要指定一個(gè)確切的設(shè)備,并且包括制造商的名字,以避免命名空間沖突。
compatible = "<manufacturer>,<model>" [, "model"]
#manufacturer指定廠家名,model指定特定設(shè)備型號(hào),后續(xù)的model指定兼容的設(shè)備型號(hào)。
- <model>對(duì)應(yīng)到具體的驅(qū)動(dòng)文件定義的設(shè)備,如spidev 對(duì)應(yīng)于openwrt/build_dir/target-mipsel_24kc_glibc-2.24/linux-ramips_mt7688/linux-4.4.167/drivers/spi/spidev.c的spidev_spi_driver的name。
舉例:
compatible = "smc, smc91c11";
compatible = "samsung,k8f1315ebm", "cfi-flash";
2)#address-cells和#size-cells屬性
-
#address-cells = <1>: 基地址、片選號(hào)等絕對(duì)起始地址所占字長,單位uint32 -
#size-cells = <1>: 長度所占字長,單位uint32
external-bus {
#address-cells = <2>
#size-cells = <1>;
ethernet@0,0 {
compatible = "smc,smc91c111";
reg = <0 0 0x1000>; // 地址占兩個(gè)cells, 長度占1個(gè)cells
nterrupts = < 5 2 >;
};
}
3)reg屬性
reg = <addr1 len1 [addr2 len2] [addr3 len3]>...: addr表明基址,len表明長度,addr由#address-cells個(gè)uint32值組成,len由#size-cells個(gè)uint32值組成。表明了設(shè)備使用的一個(gè)地址范圍。
/{
compatible = "acme,coyotes-revenge";
#address-cells = <1>;
#size-cells = <1>;
serial@101f2000 {
compatible = "arm,pl011";
reg = <0x101f2000 0x1000 >;
interrupts = < 2 0 >;
};
}
4)中斷屬性
interrupt-parent - 設(shè)備結(jié)點(diǎn)透過它來指定它所依附的中斷控制器的phandle,當(dāng)結(jié)點(diǎn)沒有指定interrupt-parent時(shí),則從父級(jí)結(jié)點(diǎn)繼承。
interrupt-controller - 一個(gè)空的屬性定義該節(jié)點(diǎn)作為一個(gè)
接收中斷信號(hào)的設(shè)備#interrupt-cells - 表明連接此中斷控制器的設(shè)備的interrupts屬性的cell大?。▊€(gè)數(shù))
-
interrupts - 一個(gè)中斷指示符的列表,對(duì)應(yīng)于該設(shè)備上的每個(gè)中斷輸出信號(hào),在ARM GIC中:
-
當(dāng)#interrupt-cells為3時(shí),interrupts包含三個(gè)cells,如
interrupts = <0 168 4> [, <0 169 4>]- 第一個(gè)cell代表中斷類型:0 表示SPI中斷,1 表示PPI中斷
- 第二個(gè)cell代表具體的中斷類型:、
- PPI中斷:私有外設(shè)中斷(Private Peripheral Interrupt),是每個(gè)CPU私有的中斷。最多支持16個(gè)PPI中斷,范圍【0 - 15】。
- SPI中斷類型:公用外設(shè)中斷(Shared Peripheral Interrupt),最多可以支持988個(gè)外設(shè)中斷,范圍【0 - 987】。
- 第三個(gè)cell代表中斷觸發(fā)標(biāo)志:
- bits [ 3 :0 ] 觸發(fā)類型和級(jí)別標(biāo)志:
1 = 低- 至- 高邊沿觸發(fā)
2 = 高- 到- 低邊沿觸發(fā)
4 = 活躍的高水平- 敏感
8 = 低電平有效- 敏感 - bits [ 15 :8 ] PPI中斷cpu掩碼。每個(gè)位對(duì)應(yīng)于每個(gè)位附加到GIC的8個(gè)可能的cpu。指示設(shè)置為“1”的位中斷被連接到該CPU 。只有有效的PPI中斷。
- bits [ 3 :0 ] 觸發(fā)類型和級(jí)別標(biāo)志:
-
當(dāng)#interrupt-cells為2時(shí),interrupts包含2個(gè)cells,如
interrupts = <2 4>- 第一個(gè)cell代表具體的中斷類型:
- SGI中斷:軟件觸發(fā)中斷(Software Generated Interrupt),通常用于多核間通訊,最多支持16個(gè)SGI中斷,硬件中斷號(hào)從ID0~ID15。
- PPI中斷:私有外設(shè)中斷(Private Peripheral Interrupt),是每個(gè)CPU私有的中斷。最多支持16個(gè)PPI中斷,硬件中斷號(hào)從ID16~ID31。
- SPI中斷類型:公用外設(shè)中斷(Shared Peripheral Interrupt),最多可以支持988個(gè)外設(shè)中斷,硬件中斷號(hào)從ID32~ID1019。
- 第二個(gè)cell代表中斷觸發(fā)標(biāo)志:
- bits [ 3 :0 ] 觸發(fā)類型和級(jí)別標(biāo)志:
1 = 低- 至- 高邊沿觸發(fā)
2 = 高- 到- 低邊沿觸發(fā)
4 = 活躍的高水平- 敏感
8 = 低電平有效- 敏感 - bits [ 15 :8 ] PPI中斷cpu掩碼。每個(gè)位對(duì)應(yīng)于每個(gè)位附加到GIC的8個(gè)可能的cpu。指示設(shè)置為“1”的位中斷被連接到該CPU 。只有有效的PPI中斷。
- bits [ 3 :0 ] 觸發(fā)類型和級(jí)別標(biāo)志:
備注:ARM GIC V3說明:kernel/Documentation/devicetree/bindings/arm/gic.txt
- 第一個(gè)cell代表具體的中斷類型:
-
-
reg - 指定基物理地址和所述GIC寄存器的大小
- 第一個(gè)區(qū)域是GIC分銷商的注冊(cè)基數(shù)和規(guī)模。
- 第二個(gè)區(qū)域是GIC cpu 接口寄存器的基數(shù)和大小。
/ {
compatible = "acme,coyotes-revenge";
#address-cells = <1>;
#size-cells = <1>;
interrupt-parent = <&intc>;//指定依附的中斷控制器是intc
serial@101f0000 { //子節(jié)點(diǎn):串口設(shè)備
compatible = "arm,pl011";
reg = <0x101f0000 0x1000 >;
interrupts = < 1 0 >;
};
intc: interrupt-controller@10140000 { //intc中斷控制器
compatible = "arm,pl190";
reg = <0x10140000 0x1000 >;
interrupt-controller;//定義為中斷控制器設(shè)備
#interrupt-cells = <2>;
};
}
四、設(shè)備樹文件分析
mt7628/mt7688的設(shè)備樹管腳配置參考o(jì)penwrt/build_dir/target-mipsel_24kc_glibc-2.24/linux-ramips_mt7688/linux-4.4.167/arch/mips/ralink/mt7620.c文件
//mt7628an.dtsi文件
/ {
#address-cells = <1>;
#size-cells = <1>;
compatible = "ralink,mtk7628an-soc";
cpus {
cpu@0 {
compatible = "mips,mips24KEc";
};
};
chosen {
bootargs = "console=ttyS0,57600";
};
aliases {
serial0 = &uartlite;
};
cpuintc: cpuintc@0 {
#address-cells = <0>;
#interrupt-cells = <1>;
interrupt-controller;
compatible = "mti,cpu-interrupt-controller";
};
palmbus: palmbus@10000000 {
compatible = "palmbus";
reg = <0x10000000 0x200000>;
ranges = <0x0 0x10000000 0x1FFFFF>;
#address-cells = <1>;
#size-cells = <1>;
sysc: sysc@0 {
compatible = "ralink,mt7620a-sysc";
reg = <0x0 0x100>;
};
watchdog: watchdog@120 {
compatible = "ralink,mt7628an-wdt", "mtk,mt7621-wdt";
reg = <0x120 0x10>;
resets = <&rstctrl 8>;
reset-names = "wdt";
interrupt-parent = <&intc>;
interrupts = <24>;
};
intc: intc@200 {
compatible = "ralink,mt7628an-intc", "ralink,rt2880-intc";
reg = <0x200 0x100>;
resets = <&rstctrl 9>;
reset-names = "intc";
interrupt-controller;
#interrupt-cells = <1>;
interrupt-parent = <&cpuintc>;
interrupts = <2>;
ralink,intc-registers = <0x9c 0xa0
0x6c 0xa4
0x80 0x78>;
};
memc: memc@300 {
compatible = "ralink,mt7620a-memc", "ralink,rt3050-memc";
reg = <0x300 0x100>;
resets = <&rstctrl 20>;
reset-names = "mc";
interrupt-parent = <&intc>;
interrupts = <3>;
};
gpio@600 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "mtk,mt7628-gpio", "mtk,mt7621-gpio";
reg = <0x600 0x100>;
interrupt-parent = <&intc>;
interrupts = <6>;
gpio0: bank@0 {
reg = <0>;
compatible = "mtk,mt7621-gpio-bank";
gpio-controller;
#gpio-cells = <2>;
};
gpio1: bank@1 {
reg = <1>;
compatible = "mtk,mt7621-gpio-bank";
gpio-controller;
#gpio-cells = <2>;
};
gpio2: bank@2 {
reg = <2>;
compatible = "mtk,mt7621-gpio-bank";
gpio-controller;
#gpio-cells = <2>;
};
};
i2c: i2c@900 {
compatible = "mediatek,mt7621-i2c";
reg = <0x900 0x100>;
resets = <&rstctrl 16>;
reset-names = "i2c";
#address-cells = <1>;
#size-cells = <0>;
status = "disabled";
pinctrl-names = "default";
pinctrl-0 = <&i2c_pins>;
};
i2s: i2s@a00 {
compatible = "mediatek,mt7628-i2s";
reg = <0xa00 0x100>;
resets = <&rstctrl 17>;
reset-names = "i2s";
interrupt-parent = <&intc>;
interrupts = <10>;
txdma-req = <2>;
rxdma-req = <3>;
dmas = <&gdma 4>,
<&gdma 6>;
dma-names = "tx", "rx";
status = "disabled";
};
spi0: spi@b00 {
compatible = "ralink,mt7621-spi";
reg = <0xb00 0x100>;
resets = <&rstctrl 18>;
reset-names = "spi";
#address-cells = <1>;
#size-cells = <0>;
pinctrl-names = "default";
pinctrl-0 = <&spi_pins>;
status = "disabled";
};
uartlite: uartlite@c00 {
compatible = "ns16550a";
reg = <0xc00 0x100>;
reg-shift = <2>;
reg-io-width = <4>;
no-loopback-test;
clock-frequency = <40000000>;
resets = <&rstctrl 12>;
reset-names = "uartl";
interrupt-parent = <&intc>;
interrupts = <20>;
pinctrl-names = "default";
pinctrl-0 = <&uart0_pins>;
};
uart1: uart1@d00 {
compatible = "ns16550a";
reg = <0xd00 0x100>;
reg-shift = <2>;
reg-io-width = <4>;
no-loopback-test;
clock-frequency = <40000000>;
resets = <&rstctrl 19>;
reset-names = "uart1";
interrupt-parent = <&intc>;
interrupts = <21>;
pinctrl-names = "default";
pinctrl-0 = <&uart1_pins>;
status = "disabled";
};
uart2: uart2@e00 {
compatible = "ns16550a";
reg = <0xe00 0x100>;
reg-shift = <2>;
reg-io-width = <4>;
no-loopback-test;
clock-frequency = <40000000>;
resets = <&rstctrl 20>;
reset-names = "uart2";
interrupt-parent = <&intc>;
interrupts = <22>;
pinctrl-names = "default";
pinctrl-0 = <&uart2_pins>;
status = "disabled";
};
pwm: pwm@5000 {
compatible = "mediatek,mt7628-pwm";
reg = <0x5000 0x1000>;
resets = <&rstctrl 31>;
reset-names = "pwm";
pinctrl-names = "default";
pinctrl-0 = <&pwm0_pins>, <&pwm1_pins>;
status = "disabled";
};
pcm: pcm@2000 {
compatible = "ralink,mt7620a-pcm";
reg = <0x2000 0x800>;
resets = <&rstctrl 11>;
reset-names = "pcm";
interrupt-parent = <&intc>;
interrupts = <4>;
status = "disabled";
};
gdma: gdma@2800 {
compatible = "ralink,rt3883-gdma";
reg = <0x2800 0x800>;
resets = <&rstctrl 14>;
reset-names = "dma";
interrupt-parent = <&intc>;
interrupts = <7>;
#dma-cells = <1>;
#dma-channels = <16>;
#dma-requests = <16>;
status = "disabled";
};
};
pinctrl: pinctrl {
compatible = "ralink,rt2880-pinmux";
pinctrl-names = "default";
pinctrl-0 = <&state_default>;
state_default: pinctrl0 {
};
spi_pins: spi {
spi {
ralink,group = "spi";
ralink,function = "spi";
};
};
spi_cs1_pins: spi_cs1 {
spi_cs1 {
ralink,group = "spi cs1";
ralink,function = "spi cs1";
};
};
i2c_pins: i2c {
i2c {
ralink,group = "i2c";
ralink,function = "i2c";
};
};
uart0_pins: uartlite {
uartlite {
ralink,group = "uart0";
ralink,function = "uart0";
};
};
uart1_pins: uart1 {
uart1 {
ralink,group = "uart1";
ralink,function = "uart1";
};
};
uart2_pins: uart2 {
uart2 {
ralink,group = "uart2";
ralink,function = "uart2";
};
};
sdxc_pins: sdxc {
sdxc {
ralink,group = "sdmode";
ralink,function = "sdxc";
};
};
pwm0_pins: pwm0 {
pwm0 {
ralink,group = "pwm0";
ralink,function = "pwm0";
};
};
pwm1_pins: pwm1 {
pwm1 {
ralink,group = "pwm1";
ralink,function = "pwm1";
};
};
pcm_i2s_pins: i2s {
i2s {
ralink,group = "i2s";
ralink,function = "pcm";
};
};
};
rstctrl: rstctrl {
compatible = "ralink,mt7620a-reset", "ralink,rt2880-reset";
#reset-cells = <1>;
};
clkctrl: clkctrl {
compatible = "ralink,rt2880-clock";
#clock-cells = <1>;
};
usbphy: usbphy@10120000 {
compatible = "ralink,mt7628an-usbphy", "mediatek,mt7620-usbphy";
reg = <0x10120000 0x1000>;
#phy-cells = <1>;
resets = <&rstctrl 22 &rstctrl 25>;
reset-names = "host", "device";
clocks = <&clkctrl 22 &clkctrl 25>;
clock-names = "host", "device";
};
sdhci: sdhci@10130000 {
compatible = "ralink,mt7620-sdhci";
reg = <0x10130000 0x4000>;
interrupt-parent = <&intc>;
interrupts = <14>;
pinctrl-names = "default";
pinctrl-0 = <&sdxc_pins>;
status = "disabled";
};
ehci: ehci@101c0000 {
compatible = "generic-ehci";
reg = <0x101c0000 0x1000>;
phys = <&usbphy 1>;
phy-names = "usb";
interrupt-parent = <&intc>;
interrupts = <18>;
};
ohci: ohci@101c1000 {
compatible = "generic-ohci";
reg = <0x101c1000 0x1000>;
phys = <&usbphy 1>;
phy-names = "usb";
interrupt-parent = <&intc>;
interrupts = <18>;
};
ethernet: ethernet@10100000 {
compatible = "ralink,rt5350-eth";
reg = <0x10100000 0x10000>;
interrupt-parent = <&cpuintc>;
interrupts = <5>;
resets = <&rstctrl 21 &rstctrl 23>;
reset-names = "fe", "esw";
mediatek,switch = <&esw>;
};
esw: esw@10110000 {
compatible = "mediatek,mt7628-esw", "ralink,rt3050-esw";
reg = <0x10110000 0x8000>;
resets = <&rstctrl 23>;
reset-names = "esw";
interrupt-parent = <&intc>;
interrupts = <17>;
};
pcie: pcie@10140000 {
compatible = "mediatek,mt7620-pci";
reg = <0x10140000 0x100
0x10142000 0x100>;
#address-cells = <3>;
#size-cells = <2>;
interrupt-parent = <&cpuintc>;
interrupts = <4>;
resets = <&rstctrl 26 &rstctrl 27>;
reset-names = "pcie0", "pcie1";
clocks = <&clkctrl 26 &clkctrl 27>;
clock-names = "pcie0", "pcie1";
status = "disabled";
device_type = "pci";
bus-range = <0 255>;
ranges = <
0x02000000 0 0x00000000 0x20000000 0 0x10000000 /* pci memory */
0x01000000 0 0x00000000 0x10160000 0 0x00010000 /* io space */
>;
pcie-bridge {
reg = <0x0000 0 0 0 0>;
#address-cells = <3>;
#size-cells = <2>;
device_type = "pci";
};
};
wmac: wmac@10300000 {
compatible = "mediatek,mt7628-wmac";
reg = <0x10300000 0x100000>;
interrupt-parent = <&cpuintc>;
interrupts = <6>;
status = "disabled";
mediatek,mtd-eeprom = <&factory 0x0000>;
};
};