aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/mt7628an_tplink_8m-split-uboot.dtsi
Commit message (Collapse)AuthorAgeFilesLines
* ramips: mt7628: move mtd-eeprom out of root DTSIAdrian Schmutzler2021-08-171-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | The mt76x8 subtarget is the only one in ramips that stores the mediatek,mtd-eeprom property directly in the "root" mt7628an.dtsi. This is not optimal for a few different reasons: * If you don't really know it or are used to other (sub)targets, the property will be set somewhat magically. * The property is set based on &factory partition before (if at all) this partition is defined. * There are several devices that have different offset or even different partitions to read from, which will then be overwritten in the DTS files. Thus, definitions are scattered between root DTSI and individual files. Based on these circumstances, the "root" definition is removed and the property is added to the device-based DTS(I) files where needed and applicable. This should be easier to grasp for unexperienced developers and will move the property closer to the partition definitions. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: convert mtd-mac-address to nvmem implementationAnsuel Smith2021-07-191-2/+14
| | | | | | | Define nvmem-cells and convert mtd-mac-address to nvmem implementation. The conversion is done with an automated script. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ramips: simplify status for ehci/ohci on mt7628 TP-Link devicesAdrian Schmutzler2020-12-071-8/+0
| | | | | | | | | | | | | | At the moment, ehci/ohci is enabled in mt7628an SoC DTSI, then disabled in the TP-Link-specific DTSI files, and finally enabled again in the DTS files of the devices needing it. This on-off-on scheme is hard to grasp on a quick look. Thus, this patch drops the status in the TP-Link-specific DTSI files, having the TP-Link devices treated like the rest of mt7628an DTSes, i.e. ehci/ohci is enabled by default and needs to be disabled explicitly where needed. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: move dts-v1 statement to top-level DTSI filesAdrian Schmutzler2020-09-251-0/+1
| | | | | | | | | | | | | | | | | The "/dts-v1/;" identifier is supposed to be present once at the top of a device tree file after the includes have been processed. In ramips, we therefore requested to have in the DTS files so far, and omit it in the DTSI files. However, essentially the syntax of the parent mtxxxx/rtxxxx DTSI files already determines the DTS version, so putting it into the DTS files is just a useless repetition. Consequently, this patch puts the dts-v1 statement into the top-level SoC-based DTSI files, and removes all other occurences. Since the dts-v1 statement needs to be before any other definitions, this also moves the includes accordingly where necessary. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: move includes to DTSI for mt7628an_tplink_8m*Adrian Schmutzler2020-02-221-0/+3
| | | | | | | | | | All devices inherited from mt7628an_tplink_8m.dtsi and mt7628an_tplink_8m-split-uboot.dtsi contain the same additional includes in the DTS files. Move them to the DTSI files instead. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: mt76x8: fix bogus mediatek,portmapSungbo Eo2020-01-181-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | mt76x8 uses esw_rt3050 driver, which does not accept mediatek,portmap with string values. Convert the strings to integers to make it work. According to its switch setup, WRTnode 2P/2R have a WAN port at port 0, so the correct value should be 0x3e. tplink_8m.dtsi uses "llllw", but it does not match switch setups of any device using the DTSI. Remove it from the DTSI and add correct value to DTS for each device. These devices have a WAN port at port 0. Set the value to 0x3e. - tplink,archer-c20-v4 - tplink,archer-c50-v3 - tplink,tl-mr3420-v5 - tplink,tl-wr840n-v4 - tplink,tl-wr841n-v13 - tplink,tl-wr842n-v5 These devices have only one ethernet port. They don't need portmap setting. - tplink,tl-wa801nd-v5 - tplink,tl-wr802n-v4 - tplink,tl-wr902ac-v3 Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: fix portmap for TP-Link Archer C50 v4Maxim Anisimov2019-12-191-1/+1
| | | | | | According to 02_network portmap is wan=0 lan1=1 lan2=2 lan3=3 lan4=4 Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com>
* ramips: provide label MAC addressAdrian Schmutzler2019-09-191-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds the label MAC address for several devices in ramips. Some devices require setting the MAC address in 02_network: For the following devices, the netif device can be linked in device tree, but the MAC address cannot be read: - cudy,wr1000 - dlink,dir-615-d - dlink,dir-615-h1 - dlink,dir-860l-b1 - glinet,gl-mt300a - glinet,gl-mt300n - glinet,gl-mt750 - vocore,vocore2 - vocore,vocore2-lite - zbtlink,zbt-we1326 - zbtlink,zbt-wg3526 For the following devices, label MAC address is tied to lan or wan, so no node to link to exists in device tree: - dlink,dir-510l - dlink,dwr-116-a1 - dlink,dwr-118-a1 - dlink,dwr-118-a2 - dlink,dwr-921-c1 - dlink,dwr-922-e2 - all hiwifi devices - lava,lr-25g001 - xiaomi,mir3p Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: dts: drop memory nodesChuanhong Guo2019-07-111-5/+0
| | | | | | | | mt7621 and mt7628 now have the ability to detect memory size automatically. Drop memory nodes and let kernel determine memory size. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips/mt76x8: Name DTS files based on schemeAdrian Schmutzler2019-07-101-0/+89
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>