aboutsummaryrefslogtreecommitdiff
path: root/target/linux/ramips/dts/mt7620a_tplink_archer-c2-v1.dts
Commit message (Collapse)AuthorAge
* kernel: rtl8367b: use realtek,extif propertyMieczyslaw Nalewaj2024-08-06
| | | | | | | | | | Use realtek,extif property instead of realtek,extif0 to extif2 by extending it with the cpu_port parameter. The extif number is automatically calculated based on cpu_port. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com> Link: https://github.com/openwrt/openwrt/pull/15749 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: tplink,archer-c2-v1: cleaning up nvmem-cells definitionsMieczyslaw Nalewaj2024-06-16
| | | | | | | Remove nvmem-cells definitions due to duplication in mt7620a_tplink_8m.dtsi Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* kernel: rtl8367b: remove unnecessary cpu_port settingMieczyslaw Nalewaj2024-06-08
| | | | | | | | | Set the appropriate cpu_port value based on the use of realtek,extif0 to extif2 instead of the additional cpu_port parameter. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com> Link: https://github.com/openwrt/openwrt/pull/15033 Signed-off-by: Robert Marko <robimarko@gmail.com>
* ramips: use led, function/color syntax for some tp-link archer routersMieczyslaw Nalewaj2024-05-09
| | | | | | | | Setting the LED name and abandoning the label and using the function/color syntax for some TP-Link Archer series routers: Archer C2 v1, Archer C20 v1, Archer C20i and Archer C50 v1 Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: mt7620a_tplink_archer.dtsi rename to mt7620a_tplink_8m.dtsiMieczyslaw Nalewaj2024-04-13
| | | | | | Change the name mt7620a_tplink_archer.dtsi to mt7620a_tplink_8m.dtsi because it will also be a base for TP-Link non-Archer routers. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: TP-Link Archer C2 v1: simplification of the dts definitionMieczyslaw Nalewaj2024-04-13
| | | | | | Import from the mt7620a_tplink_archer.dtsi file and thus simplify the rest of the definition. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: removing unnecessary compatibility for TP-Link Archer C2 v1Mieczyslaw Nalewaj2024-02-27
| | | | | | | Removing: compatible = "rtl8367b" This string is not used anywhere in the code. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: clean up useless dts partition labelsShiji Yang2024-02-21
| | | | | | | | | | 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-07
| | | | | | | | 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: mt7620a: use mac-baseRosen Penev2023-11-26
| | | | | | mac-address-increment is deprecated. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ramips: mt7620a: convert to nvmem-layoutRosen Penev2023-11-26
| | | | | | Allows using mac-base to replace mac-address-increment. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ramips: convert mt76 PCIe NIC EEPROM to NVMEM format for legacy SoCsShiji Yang2023-10-17
| | | | | | | | | | 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 rt2x00 EEPROM to NVMEM formatShiji Yang2023-10-17
| | | | | | | This patch converts legacy Ralink SoCs and MT7620 WiFi calibration data to NVMEM format. The EEPROM size is 0x200. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: convert mtd-mac-address to nvmem implementationAnsuel Smith2021-07-19
| | | | | | | 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>
* treewide: convert mtd-mac-address-increment* to generic implementationAnsuel Smith2021-07-19
| | | | | | | | | | | | | Rework patch 681-NET-add-mtd-mac-address-support to implement only the function to read the mac-address from mtd. Generalize mtd-mac-address-increment function so it can be applied to any source of of_get_mac_address. Rename any mtd-mac-address-increment to mac-address-increment. Rename any mtd-mac-address-increment-byte to mac-address-increment-byte. This should make simplify the conversion of target to nvmem implementation. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ramips: remove model name from LED labelsAdrian Schmutzler2020-10-02
| | | | | | | | | | | | | | | | | 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-25
| | | | | | | | | | | | | | | | | 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: increase SPI frequency for MT7620 ArcherDavid Bauer2020-07-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Increase the SPI frequency for the MT7620 based TP-Link Archer series to 30MHz. TP-Link uses different SPI flash chips for the same board revision, so be conservative to not break boards with a different chip. 30MHz should be well supported by all chips. Tested on Archer C2 v1 (GD25Q64B) and Archer C20i (W25Q64FV). Archer C20i (before) ==================== root@OpenWrt:~# time dd if=/dev/mtd1 of=/tmp/test.bin bs=64k 122+0 records in 122+0 records out real 0m 15.30s user 0m 0.00s sys 0m 15.29s Archer C20i (after) =================== root@OpenWrt:~# time dd if=/dev/mtd1 of=/tmp/test.bin bs=64k 122+0 records in 122+0 records out real 0m 5.99s user 0m 0.00s sys 0m 5.98s Signed-off-by: David Bauer <mail@david-bauer.net> Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: mt7620: tidy up ethernet node in DTS filesAdrian Schmutzler2020-05-17
| | | | | | | | | | | | This tidies up the ethernet node in mt7620 DTS files by: - removing unnecessary status as it is not disabled - reordering properties consistently - adding empty lines to enhance readability This should make comparison and reviewing new PRs based on C/P easier. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: dts: use generic node name for flashSungbo Eo2020-05-09
| | | | | | | | | | | | | | | | | In DTS Checklist[1] we're now demanding proper generic node names, as the name of a node should reflect the function of the device and use generic name for that[2]. Everybody seems to be copy&pasting from DTS files available in the repository today, so let's unify that naming there as well and provide proper examples. While at it, remove unused m25p80 label. Tested on rt5350 (for spi-nor) and rt3662 (for cfi-flash). 1. https://openwrt.org/submitting-patches#dts_checklist 2. https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: use hex notation for *-mtd-eeprom propertySungbo Eo2020-05-08
| | | | | | | Change "0" to "0x0" for consistency. This is an extension of commit 34abfb6e91d1 ("ramips: convert mediatek,mtd-eeprom from decimal to hex notation"). Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: replace pinctrl property namesChuanhong Guo2020-04-12
| | | | | | | | | | | | | | 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: fix Archer C2 v1 5GHz MAC addressDavid Bauer2020-01-02
| | | | | | | | | | | The TP-Link Archer C2 v1 previously had a generic Ralink MAC address set for the 5GHz radio (MT7610), as the caldata does only contain a generic MAC address. Set the MAC address from the vendor firmware for the 5GHz radio to assign unique MAC addresses to every device. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: convert TP-Link MT7620 boards to tpt triggerDavid Bauer2020-01-02
| | | | | | | | | | | | This converts all MediaTek MT7620 boards from TP-Link to use the now supported WiFi throughput LED trigger. This way, the LED state now covers all VAPs regardless of their name. Also align all single-WiFi LEDs to represent the state of the 2.4GHz radio. This was not always the case previously, as later-added support for the MT7610 altered the phy probing order. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: simplify state_default/pinctrl0 in device DTS filesAdrian Schmutzler2019-12-23
| | | | | | | | | 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: fix whitespace issues in DTS filesAdrian Schmutzler2019-10-21
| | | | | | | | | This is the result of grepping/searching for several common whitespace issues like double empty lines, leading spaces, etc. This patch fixes them for the ramips target. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix LED labels not updated during device name changesAdrian Schmutzler2019-08-10
| | | | | | | | | | | | | | In commit d93969a13a5b ("ramips: Improve compatible for TP-Link Archer devices") and subsequent ones, names of several devices in ramips have been changed. Since LED names are frequently invoked by $boardname, this has broken LED setup in 01_leds, as $boardname and prefix in DTS do not match anymore. This patch updates device name prefixes for LEDs in DTS files, and provides a migration script. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips/mt7620: Name DTS files based on schemeAdrian Schmutzler2019-07-10
As introduced with ath79, DTS files for ramips will now be labelled soc_vendor_device.dts(i). With this change, DTS files can be selected automatically without further manual links. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Powered by cgit, Themed by Ted Yin.