summaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/mt7628an_wavlink_wl-wn570ha1.dts
Commit message (Collapse)AuthorAgeFilesLines
* ramips: clean up useless dts partition labelsShiji Yang2024-02-211-1/+1
| | | | | | | | | | The previous NVMEM eeprom conversions[1][2] left a lot of partition labels that were no longer used. They can be removed now. [1] https://github.com/openwrt/openwrt/pull/13584 [2] https://github.com/openwrt/openwrt/pull/13587 Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: convert to new LED color/function format where possibleChristian Marangi2024-02-071-2/+5
| | | | | | | | Initial conversion to new LED color/function format and drop label format where possible. The same label is composed at runtime. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* ramips: mt7628: use nvmem-layoutRosen Penev2023-11-251-11/+14
| | | | | | Will allow using mac-base. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ramips: convert mt76 PCIe NIC EEPROM to NVMEM format for legacy SoCsShiji Yang2023-10-171-1/+6
| | | | | | | | | | This patch converts MT761{0,2,3} PCIe WiFi calibration data to NVMEM format for legacy Ralink SoCs (MT7620 and Mt7628). The EEPROM size of the MT7610 and MT7612 is 0x200. there are only three devices uses MT7613 NIC, ASUS RT-AC1200 V2, COMFAST CF-WR758AC V2 and Keenetic KN-1613. The EEPROM size of them is 0x4da8. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: convert MT7628 EEPROM to NVMEM formatShiji Yang2023-10-171-11/+13
| | | | | | | This patch converts MT7628 WiFi calibration data to NVMEM format. The EEPROM size is 0x400. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: mt7628: move mtd-eeprom out of root DTSIAdrian Schmutzler2021-08-171-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | 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-1/+12
| | | | | | | 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: remove model name from LED labelsAdrian Schmutzler2020-10-021-6/+6
| | | | | | | | | | | | | | | | | Like in the previous patch for ath79 target, this will remove the "devicename" from LED labels in ramips as well. The devicename is removed in DTS files and 01_leds, consolidation of definitions into DTSI files is done where (easily) possible, and migration scripts are updated. For the latter, all existing definitions were actually just devicename migrations anyway. Therefore, those are removed and a common migration file is created in target base-files. This is actually another example of how the devicename removal makes things easier. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: move dts-v1 statement to top-level DTSI filesAdrian Schmutzler2020-09-251-3/+2
| | | | | | | | | | | | | | | | | 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: drop redundant chosen/bootargsAdrian Schmutzler2020-06-251-4/+0
| | | | | | | chosen/bootargs are defined to the same value in device DTS files that is already set in the SoC DTSI. Remove the redundant definitions. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: replace pinctrl property namesChuanhong Guo2020-04-121-2/+2
| | | | | | | | | | | | | | Upstream pinctrl driver in drivers/staging uses groups/function/ralink,num-gpios instead of ralink,group/ralink,function/ralink,nr-gpio Replace these properties in dts as well as the pinctrl driver in patches-4.14. This commit is created using: sed -i 's/ralink,group/groups/g' sed -i 's/ralink,function/function/g' sed -i 's/ralink,nr-gpio/ralink,num-gpios/g' Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: mt7628: update dts for upstream gpio-mt7621 driverChuanhong Guo2020-04-121-7/+7
| | | | | | | | | | upstream driver merged 3 separated gpio banks into one gpio node. and gpioX Y in our local driver should be replaced with gpio X*32+Y. This patch is created using the following sed command: sed -i -r 's/(.*)gpio([0-9]) ([0-9]+)(.*)/echo "\1gpio $((\2*32+\3))\4"/ge' Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* 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: simplify state_default/pinctrl0 in device DTS filesAdrian Schmutzler2019-12-231-6/+4
| | | | | | | | | The node pinctrl0 is already set up in the SOC DTSI files, but defined again as member of pinctrl in most of the device DTS(I) files. This patch removes this redundancy for the entire ramips target. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips/mt762x: convert devices to interrupt-driven gpio-keysAdrian Schmutzler2019-10-211-2/+1
| | | | | | | | | | | This converts all remaining devices to use interrupt-driven gpio-keys compatible instead of gpio-keys-polled. The poll-interval is removed. While at it, add/remove newlines in keys and leds node where necessary. 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/+135
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>