summaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq
Commit message (Collapse)AuthorAgeFilesLines
* lantiq: Fixed brnImage signature for the VGV7510KW22BRN imagesFelix Fietkau2016-01-171-1/+1
| | | | | | | | | | | | | The old signature only worked because brnboot ignores the leading "5" in the signature. We can see the correct signature when flashing a brnImage via recovery web-interface, in this case brnboot reports: [CGI-Signature Check] buf:[BRNDA6431], sigInFlash:[BRNDA6431] Thanks to Mathias Kresin for reporting this. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48269
* lantiq: Switch to the generic mtdsplit parser implementationsFelix Fietkau2016-01-172-192/+3
| | | | | | | | | This removes the arch-specific mtdsplit parsers and enables the generic implementations for brnImage, EVA and TP-Link instead. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48264
* lantiq: remove clk_round_rate() patchHauke Mehrtens2016-01-131-43/+0
| | | | | | | | | This patch was merged into upstream Linux 4.1. This fixes #21587 and was introduced in r48223. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48229
* kernel/4.1: update to version 4.1.15Hauke Mehrtens2016-01-122-4/+4
| | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48223
* lantiq: Add the xbar to vr9.dtsJohn Crispin2016-01-011-1/+5
| | | | | | | | linux 4.4 (since commit 08b3c894e56580b8ed3e601212a25bda974c3cc2 "MIPS: lantiq: Disable xbar fpi burst mode") requires that the xbar is defined in the .dts of vrx200 (VR9) SoCs. SVN-Revision: 48056
* lantiq: match default xdsl mode and default wan interfaceJohn Crispin2016-01-011-1/+5
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48047
* lantiq: convert vendorid into human readable formJohn Crispin2016-01-011-0/+67
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48046
* lantiq: add the current profile to the stats outputJohn Crispin2016-01-011-0/+30
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48045
* lantiq: TDW8980 - use devicename:colour:function led naming schemeJohn Crispin2016-01-011-1/+1
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48044
* lantiq: P2812HNUFX - move usb leds to P2812HNU-F1John Crispin2016-01-012-10/+18
| | | | | | | | | | The P2812HNU-F3 doesn't have usb leds. Only the P2812HNU-F1 has those leds. Reported-by: Sylwester Petela <sscapi@gmail.com> Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48043
* lantiq: use devicename:colour:function led naming schemeJohn Crispin2016-01-0130-372/+396
| | | | | | | | | | | | | | | | The leds of the following boards are not renamed due to lack of manuals/informations: - ARV7519PW - ARV7510PW22 - ARV4510PW The leds of the ARV4518PWR01* boards are unchanged, since the leds doesn't match the leds from the manual or pictures (e.g. there shouldn't be a wps led). Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48042
* lantiq: add support for indicating the boot state using three ledsJohn Crispin2016-01-0133-132/+189
| | | | | | | | | | | | | | The BTHOMEHUBV5A has a RGB power led, where every colour is perfect to indicate the current boot state. This patch adds support for such cases. The existing led sequences should be the same as before. Boards which are using a led different from power (like TDW89x0) are changed to switch of the led after boot Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48041
* lantiq: use dsl led defined in DTSJohn Crispin2016-01-014-17/+20
| | | | | | | | | | | | | | | | | dsl_control (dsl_notify.sh) is the only process which is aware of the state of the atm/ptm interface. Use the dsl led exclusive for the dsl line state. On boards which don't have a distinct internet and a dsl led, let the netdev status of the atm interface trigger the shared led. Triggering the shared led according to the status of the ppp interface isn't suitable, since the led would be switched of if the ppp connection goes down, but the line is still in sync. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48040
* lantiq: use power leds defined in DTSJohn Crispin2016-01-011-15/+19
| | | | | | | | Use the power leds defined in the dts file instead of hardcoded led names. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48039
* lantiq: use default leds defined in DTSJohn Crispin2016-01-012-20/+23
| | | | | | | | | | | | | Remove all now double defined leds from the led board file. Use pppoe as default for all broadband connections, since it's the default in OpenWrt now. Rename the the wifi leds to make sure, the not applicable default values get overwritten. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48038
* lantiq: define default leds in dts filesJohn Crispin2016-01-0131-135/+371
| | | | | | | | | | - ARV7525PW: use the power led as dsl led as done by the stock firmware - FRITZ3370: use the info led as internet led - FRITZ7320: use the power led as dsl led as done by the stock firmware Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48037
* lantiq: ARV752DPW - fix dts fileJohn Crispin2016-01-011-9/+13
| | | | | | | | | | | | | | Use the same led logic and labels as the OEM firmware (red = okay, blue = failure). Add the red internet led. Remove missing usb led workaround. The workaround shouldn't be in the default configuration. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48036
* lantiq: ARV752DPW22 - fix dts fileJohn Crispin2016-01-011-22/+12
| | | | | | | | | | | No need to switch (and keep) on all leds at boot. Use the same led logic and labels as the OEM firmware (red = okay, blue = failure). Add the red internet led. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48035
* lantiq: DGN1000B - fix typo in dts fileJohn Crispin2016-01-011-1/+1
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48034
* lantiq: ARV4518PWR01* move redundant parts to dtsiJohn Crispin2016-01-013-356/+186
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48033
* lantiq: BTHOMEHUBV2B - remove missing usb led workaroundJohn Crispin2016-01-011-1/+0
| | | | | | | | The workaround shouldn't be in the default configuration. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48032
* lantiq: P2812HNUFX - move leds to dtsiJohn Crispin2016-01-013-114/+61
| | | | | | | | Beside the used labels, they are the same on both boards. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48031
* lantiq: fix Image BuilderJohn Crispin2015-12-231-2/+1
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48002
* lantiq: fix PCI_DEVICE_ID_LANTIQ_PCIEJohn Crispin2015-12-231-10/+2
| | | | | | | | | | | | | | | It's not necessary to define PCI_* if pci_ids.h is included a few lines above. The change to pci_ids.h doesn't look intentional to me, especially since the former value is added to the top of ifxmips_fixup_pcie.c. Both changes were introduced with the kernel 4.1 support patches and were not present in the 3.18 patches. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47996
* lantiq: TDW89x0 - increase spi frequencyJohn Crispin2015-12-231-2/+4
| | | | | | | | | | | | | | | | | Use the same max spi frequency as set in u-boot. According to the datasheets, the Q64-104HIP as well as the Winbond 25Q64FVSIG support spi frequencies up to 50 MHz. During my tests, the Q64-104HIP couldn't be recognized/initialized if the frequency was > 40MHz. Both chips do support fast read as well. While touching the dts file, I fixed the dtc compiler warnings. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47994
* lantiq: disable SW_PORTMAP usage in the ethernet driverJohn Crispin2015-12-231-5/+4
| | | | | | | | | using the special tag in this way lead to port mirroring for certain types of traffic. fallback to using th PMAC_EWAN register for the wan portmap. Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 47993
* lantiq: Configure LED polarity for TDW8970 and TDW8980.John Crispin2015-12-232-4/+1
| | | | | | | | | This patch configures the correct ath9k WLAN LED polarity for the TDW8970, and for the TDW8980 as well. Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> SVN-Revision: 47969
* lantiq: fix ARV7519RW22 buttonsJohn Crispin2015-12-171-7/+7
| | | | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 47918
* lantiq: add the TDW8980 5GHz ledJohn Crispin2015-12-171-0/+7
| | | | | | | | | Still unused, but u-boot doesn't take care of the led, which results in a permanent switched on 5GHz LED. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47915
* lantiq: Fix LED handling.John Crispin2015-12-171-24/+32
| | | | | | | | | | - Use common OpenWrt blink patterns instead of custom ones - Add preinit_regular hook - Handle the TDW89X0 that does not have a configurable power LED Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> SVN-Revision: 47914
* lantiq: Configure LED polarity for TDW8970.John Crispin2015-12-171-0/+4
| | | | | | | | This patch configures the correct ath9k WLAN LED polarity for the TDW8970. Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> SVN-Revision: 47913
* lantiq: Configure disabled WLAN bands for TDW89X0.John Crispin2015-12-171-0/+1
| | | | | | | | | | | | | | | | | The TDW8970 has a AR9381, which is the bgn 3x3:3 variant of the AR938x family. The TDW8980 has a AR9287, which is the bgn 2x2:2 variant of the AR928x family. This means that the chip for both routers is 2.4 GHz only. Anyway, the manufacturer didn't disable the 5 GHz band in the EEPROM partition (at least on my TDW8970). So this patch disables the 5 GHz band. Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> SVN-Revision: 47912
* lantiq: Allow configuration of ath9k disabled bands and LED polarity from ↵John Crispin2015-12-171-1/+17
| | | | | | | | the device tree. Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> SVN-Revision: 47911
* all: drop old uci-defaults.shJo-Philipp Wich2015-12-112-2/+2
| | | | | | | | | Replace former uci-defaults.sh implementation with the uci-defaults-new.sh one and update all users accordingly. Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47867
* lantiq: get rid of ltq-vdsl-fwJohn Crispin2015-12-111-1/+0
| | | | | | | | | Because of dsl-vrx200-firmware-xdsl-* there's no need anymore to download a dsl firmware at runtime. Signed-off-by: Andre Heider <a.heider@gmail.com> SVN-Revision: 47851
* lantiq: fix led setup after switch to uci-defaults-new.shJohn Crispin2015-12-111-6/+7
| | | | | | | | | | | | | | | | | | | | | | | The switch to uci-defaults-new.sh revealed a bug in the former used uci-defaults.sh, which failed to add leds with colons in the led name. This bug isn't any longer present in uci-defaults-new.sh and therefore all via DT defined leds will be added to /etc/config/system with their initial on/off state, regardless whether they are already added by the board specific led mappings. This results for a BTHOMEHUBV5A into the following led configuration: - soc:blue:power is added as led_power with the initial state "switched on" - soc:blue:power is added as led_soc_blue_power with the initial state "switched off" With the final result of a switched off power led after boot. The only led that needs to be added is the BTHOMEHUBV5A specific dimmed led. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47850
* lantiq: fix logic error in dsl board.d codeJo-Philipp Wich2015-12-061-1/+1
| | | | | | | | | | | Starting with r47755 the pppoe wan interface section isn't any longer added to the network config on firstboot, using the default configuration. Since the commit message does not mention such a change, I assume that this wasn't intentionally. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47793
* lantiq: add VDSL2 vectoring status informationFelix Fietkau2015-12-051-1/+12
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47785
* lantiq: get rid of the dsl_fw mtd partitionFelix Fietkau2015-12-054-53/+3
| | | | | | | | | Now that we have redistributable vdsl/adsl firmware blobs in /lib/firmware, we can drop the dsl_fw partition and extend the firmware partition. Signed-off-by: Andre Heider <a.heider@gmail.com> SVN-Revision: 47783
* lantiq: remove 3.18 supportFelix Fietkau2015-12-0546-20339/+0
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47774
* lantiq: fix a race condition in the SPI driver leading to rx FIFO overflows ↵Felix Fietkau2015-12-041-1/+13
| | | | | | | | (and subsequent timeouts) Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47770
* lantiq: re-enable spi-xway for TD-W89X0 now that it is fixedFelix Fietkau2015-12-041-58/+46
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47768
* lantiq: fix xway spi driver timeout issuesFelix Fietkau2015-12-041-1/+1
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47767
* lantiq: clean up the xrx200 ethernet driver and fix stability issuesFelix Fietkau2015-12-042-73/+50
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47766
* lantiq: move esi calls to dsl_cpe_control scripts to fix ordering wrt. ↵Felix Fietkau2015-12-043-10/+2
| | | | | | | | loading vr9 drivers Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47764
* lantiq: switch from uci-defaults to board.dJo-Philipp Wich2015-12-043-214/+154
| | | | | | Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47755
* lantiq: fix up m25p80 device ids (#20975)Felix Fietkau2015-12-025-10/+5
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47690
* lantiq: fix compile errorHauke Mehrtens2015-11-241-1/+1
| | | | | | | | This fixes a problem introduced in r47624. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 47628
* kernel: update m25p80 in 4.1 to the latest version from 4.4-rc1Felix Fietkau2015-11-241-3/+3
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47624
* lantiq: add phy led config support over devicetree bindingsJohn Crispin2015-11-212-2/+534
| | | | | | | | | | | This patch adds the posibility to config the led behaviour of the lantiq phys over the devicetree bindings.It patches the 0023-NET-PHY-adds-driver-for-lantiq-PHY11G for 3.18 and 4.1. I have also added a register description overview for applicable values. This goes to the documentation folder in the linux kernel. Signed-off-by: Florian Eckert <Eckert.Florian@googlemail.com> SVN-Revision: 47566