aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/mt7620a_dlink_dir-810l.dts
Commit message (Collapse)AuthorAgeFilesLines
* ramips: remove model name from LED labelsAdrian Schmutzler2020-10-021-39/+0
| | | | | | | | | | | | | | | | | 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-2/+0
| | | | | | | | | | | | | | | | | 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: fix WAN LED for D-Link DIR-810L/TRENDnet TEW-810DRAdrian Schmutzler2020-06-111-9/+7
| | | | | | | | | | | | | | | | | | The WAN LED on DIR-810L was actually blinking on LAN1 port activity. This has already been improved for the TEW-810DR, where the GPIO has been set up explicitly rather than having it controlled by the switch. This patch also applies this setup to the DIR-810L. In addition, the trigger in 01_leds is set up with ucidef_set_led_switch for both devices now, so state changes should be displayed correctly as well. Reported-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [DIR-810L] Tested-by: J. Scott Heppler <shep971@centurylink.net> [TEW-810DR]
* ramips: create shared DTSI for DIR-810L and TEW-810DRAdrian Schmutzler2020-05-261-112/+1
| | | | | | | These devices seem to have the same board, so let's have a common file. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: mt7620: tidy up ethernet node in DTS filesAdrian Schmutzler2020-05-171-0/+1
| | | | | | | | | | | | 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: 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: increase spi-max-frequency to 50 MHz for D-Link DIR-810LAdrian Schmutzler2020-03-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Read times drop when increasing frequency to 25 MHz and 50 MHz, but not in between or for further increase. So, use 50 MHz as the lowest frequency with the fastest speed. Test results (thanks to Roger): The device reports a mx25l6405d flash chip. I tried all the maximum values in the devices' datasheet (Table 10. AC CHARACTERISTICS). All of them worked with and without "m25p,fast-read": > 10 MHz root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 1m 33.00s user 0m 0.01s sys 1m 7.56s > 25 MHz root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 34.42s user 0m 0.02s sys 0m 23.58s > 25 MHz, fast read root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 34.45s user 0m 0.02s sys 0m 23.59s > 33 MHz root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 34.39s user 0m 0.00s sys 0m 23.60s > 33 MHz, fast read root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 34.46s user 0m 0.01s sys 0m 23.62s > 50 MHz root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 26.81s user 0m 0.01s sys 0m 18.25s > 50 MHz, fast read root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 26.84s user 0m 0.00s sys 0m 18.25s > 66 MHz root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 26.80s user 0m 0.01s sys 0m 18.23s > 66 MHz, fast read root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 26.80s user 0m 0.02s sys 0m 18.23s > 86 MHz root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 26.84s user 0m 0.01s sys 0m 18.24s > 86 MHz, fast read root@OpenWrt:~# time cat /dev/mtd* > /dev/null real 0m 26.80s user 0m 0.02s sys 0m 18.23s Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ramips: fix and tidy up DTS for D-Link DIR-810LAdrian Schmutzler2020-03-051-8/+10
| | | | | | | | | | | | | This patch addresses several issues for D-Link DIR-810L: - add correct button codes - harmonize button node names - use generic flash@0 - remove unused pin groups from state_default - improve sorting of properties Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ramips: fix partition offset for D-Link DIR-810LAdrian Schmutzler2020-03-051-2/+2
| | | | | | | | | | | | | | The Jffs2 partition for the D-Link DIR-810L is currently off by 0x10000. Apply the correct offset based on the other partitions' size/offset and the information about stock OS from the Wiki. This is just based on the named information and _not_ verified on device. Fixes: 36e3424fa520 ("ramips: add support for dir810l and asus rp-n53") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* 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: fix WiFi MAC addresses for D-Link DIR-810LAdrian Schmutzler2019-10-151-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | So far, WiFi MAC addresses for this device have been set up from caldata. However, this returns values which do not look like MAC addresses. They also do not match stock firmware: wlan0 (5.0): 00:11:22:00:17:D0 from 0x8004 wlan1 (2.4): 00:11:22:00:17:CD from 0x4 (and 0x2e) It looks like the only valid MAC address on this device is at 0x28. So, this patch changes setup to calculate addresses based on the value at 0x28: lan: *:0A (flash, label) wan: *:0B (flash + 1) wifi2: *:0A (flash) wifi5: *:0C (flash + 2) Thanks to Roger Pueyo Centelles <roger.pueyo@guifi.net> for investigating this on his devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: provide label MAC addressAdrian Schmutzler2019-09-191-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: enable external amplifier for D-Link DIR-810LRoger Pueyo Centelles2019-09-101-0/+2
| | | | | | | | The 2.4 GHz radio had very poor signal reception (-89 dBm for an AP sitting 5 m away). By enabling the external amplifier, received signal has improved to -50 dBm for the same AP. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ramips/mt7620: Name DTS files based on schemeAdrian Schmutzler2019-07-101-0/+154
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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-07 20:58:19 +0000