summaryrefslogtreecommitdiff
path: root/target/linux/lantiq/dts
Commit message (Collapse)AuthorAgeFilesLines
* lantiq: add support for TP-Link VR200vHauke Mehrtens2016-01-181-0/+280
| | | | | | | | | This adds basic support for TP-Link VR200v. Currently the following parts are not working: FXO, Voice, DECT, WIFI (both) Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48328
* lantiq: Remove incorrect PCIe compatible stringsFelix Fietkau2016-01-172-5/+0
| | | | | | | | | Re-defining the compatible property is not required since the correct value is inherited from vr9.dtsi. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48295
* lantiq: Switch to the new SPI driverFelix Fietkau2016-01-178-31/+92
| | | | | | | | | | | | | | | | Compared to the "old" driver: - Each device must assign a pinctrl setting to the SPI node to allow the new SPI driver to configure the SPI pins. While here we are also using separate input and output settings so we are independent of whether the bootloader configures the pins correctly. - We use the new "compatible" strings to make the driver choose the correct number of chip-selects for each SoC. - The new driver starts counting the chip-selects at 1 (instead of 0, like the old one did). Thus we have to adjust the devices accordingly. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48293
* lantiq: Enable the hardware SPI driver on the DGN3500/DGN3500BFelix Fietkau2016-01-171-53/+38
| | | | | | Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48290
* lantiq: Enable SPI for the EASY80920 board againFelix Fietkau2016-01-171-46/+41
| | | | | | | | Also switch to the SPI definition provided by vr9.dtsi Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48289
* lantiq: Switch FRITZ3370 from spi-gpio to the hardware SPI driverFelix Fietkau2016-01-171-40/+31
| | | | | | Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48288
* lantiq: Re-use the SPI node from vr9.dtsi in TDW89X0.dtsiFelix Fietkau2016-01-171-40/+36
| | | | | | | | This removes the duplicate SPI register definition. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48287
* lantiq: Add the SPI node to ar9.dtsi and vr9.dtsiFelix Fietkau2016-01-172-0/+20
| | | | | | | | | | This allows devices to use SPI without having to re-define (and thus duplicating) the whole SPI node. By default SPI is disabled (as before) because only few devices need it. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48286
* lantiq: Configure the PCIe reset GPIO using OFFelix Fietkau2016-01-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | After the latest pinctrl backports there are only 50 (instead of 56 as before) GPIOs/pins exported (thus the first GPIO on VRX200 SoCs is now 462, before it was 456). This means that any hardcoded GPIOs have to be adjusted. This broke the PCIe driver (which seems to be the only driver which uses hardcoded GPIO numbers), it only reports: ifx_pcie_wait_phy_link_up timeout ifx_pcie_wait_phy_link_up timeout ifx_pcie_wait_phy_link_up timeout ifx_pcie_wait_phy_link_up timeout ifx_pcie_wait_phy_link_up timeout pcie_rc_initialize link up failed!!!!! To prevent more of these issues in the future we remove the hardcoded PCIe reset GPIO definition and simply pass it via device-tree (like the PCI driver does). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48285
* lantiq: Use the new pinctrl compatible stringsFelix Fietkau2016-01-174-4/+4
| | | | | | | | | | | | | | | | These were introduced in upstream commit be14811c03cf "pinctrl/lantiq: introduce new dedicated devicetree bindings" and finally allow us to use the individual pins within our dts (for example spi_clk, etc.). Please note that this changes the number of GPIOs which are available for some SoCs. VRX200 SoCs for example only have 50 pins, but previously 56 pins were exposed. This means that all places which are using hardcoded GPIO numbers (which are not passed via device-tree) need to be adjusted (because the first GPIO number is now 462, instead of 456). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48284
* 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: 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-0129-368/+392
| | | | | | | | | | | | | | | | 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-0131-78/+173
| | | | | | | | | | | | | | 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-012-2/+2
| | | | | | | | | | | | | | | | | 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: 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: 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: 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: 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: 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: get rid of the dsl_fw mtd partitionFelix Fietkau2015-12-053-18/+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: 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 up m25p80 device ids (#20975)Felix Fietkau2015-12-025-10/+5
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47690
* Revert "lantiq: activate spi-xway on TDW89X0"John Crispin2015-10-191-47/+59
| | | | | | | | | | This reverts commit 68c2e4789b4f071ee75d39248f4d08fe8283eb28. commit r47159 was bad Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 47207
* lantiq: activate spi-xway on TDW89X0John Crispin2015-10-071-59/+47
| | | | | | | | use the hardware spi core in favour of spi-gpio. Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 47159
* lantiq: several ARV7519RW22 fixesJohn Crispin2015-10-051-9/+13
| | | | | | | | | | | | | | Fixes ARV7519RW22 flash register (only 1 flash). Power LED is green, not red. Rename message LEDs to internet. Add LEDs configuration (lan, wan, power). Enable switch VLANs. Fix secondary USB. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> Signed-off-by: José Vázquez Fernández <ppvazquezfer@gmail.com> SVN-Revision: 47132
* lantiq: Add target TP-Link TD-W8980John Crispin2015-10-053-250/+284
| | | | | | | | | The device is similar to the TD-W8970, beside a different Atheros 2.4 GHz wireless chip and the additional, PCI connected, WAVE300 5 GHz wireless. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47130
* lantiq: Introduce DWC2 compatible DTS definitions for AR9 USBJohn Crispin2015-09-141-1/+10
| | | | | | | | | | | | Since the AR9 USB is very similar to the VR9 USB it too can be used with the upstream DWC2 driver. Here are the DTS definitions which make it compatible with the DWC2 driver. Signed-off-by: Antti Seppälä <a.seppala@gmail.com> SVN-Revision: 46914
* lantiq: Add support for Arcadyan ARV8539PW22 (Speedport W 504V)John Crispin2015-07-071-0/+162
| | | | | | | | lantiq: Add support for Arcadyan ARV8539PW22 (Speedport W 504V) Signed-off-by: Jannis Pinter <jannis@pinterjann.is> SVN-Revision: 46224
* lantiq: Add support for the BT Home Hub 5AJohn Crispin2015-07-071-0/+287
| | | | | | | | | | | | | | | u-boot support depends on the next "upstream" version ([0]) from Daniel Schwierzeck. Since the installation process is quite complicated a "how to" was added to the wiki: [1] [0] https://github.com/danielschwierzeck/u-boot-lantiq/tree/openwrt/v2014.01-next [1] http://wiki.openwrt.org/toh/bt/homehub_v5a V2: Use the correct PCI interrupt (fixes 2.4GHz wifi) Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 46223
* lantiq: Make the MEI address available for kernel driversJohn Crispin2015-07-071-0/+1
| | | | | | | | Newer DSL driver versions depend on the address information. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 46221
* lantiq: Add support for Arcadyan VGV7510KW22 (known as o2 Box 6431)John Crispin2015-06-053-0/+342
| | | | SVN-Revision: 45897
* lantiq: fix VG3503J rootfs offsetJonas Gorski2015-06-011-1/+1
| | | | | | | | | | In r44391 the kernel partion size was increased to allow larger kernels, but the rootfs partition offset was missed. Fix this by setting the rootfs offset to the expected value. Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 45868
* lantiq: Convert Zyxel P-2812HNU-FX and TP-Link TD-W8970 to support dwc2John Crispin2015-03-113-1/+19
| | | | | | | | | | | | | | Here the device tree entry for ifxhcd is listed as compatible with one supported in dwc2 (after patching the dwc driver appropriately). A second entry is added to support the second core of the hcd. This entry is listed to be compatible with only dwc2. Done this way there should be backwards support for both hcd drivers (ltq-hcd and dwc2) Signed-off-by: Antti Seppälä <a.seppala@gmail.com> Signed-off-by: Vincent Pelletier <plr.vincent@gmail.com> SVN-Revision: 44676
* lantiq: fix DGN3500 root deviceJohn Crispin2015-02-131-1/+1
| | | | | | Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us> SVN-Revision: 44428
* lantiq: fix VG3503J partition table for newer kernelsJohn Crispin2015-02-111-2/+2
| | | | | | | | the kernel has increased and does not fit into the 1,5MB anymore. Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 44391
* lantiq: td-w8970: fix reset buttonJohn Crispin2015-02-091-2/+2
| | | | | | | | For TP-LINK TD-W8970 button should work as "reset", not "BTN_1". Signed-off-by: Cezary Jackiewicz <cezary.jackiewicz@gmail.com> SVN-Revision: 44352
* lantiq: add 3.18 supportJohn Crispin2015-02-096-340/+12
| | | | | | Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 44348
* lantiq: DGN3500 cleanupsJohn Crispin2015-01-181-1/+1
| | | | | | | | | This patch builds on the previous three to streamline support for the Netgear DGN3500. Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us> SVN-Revision: 44032
* Remove old P2812HNUFX dtsJohn Crispin2015-01-171-308/+0
| | | | | | | | Remove unused P2812HNUFX board definition. Signed-off-by: Sylwester Petela <sscapi@gmail.com> SVN-Revision: 43988
* lantiq: Add device tree for P2812HNUF1 and P2812HNUF3John Crispin2015-01-173-0/+472
| | | | | | | | Add device tree for P2812HNUF1 and P2812HNUF3. Signed-off-by: Sylwester Petela <sscapi@gmail.com> SVN-Revision: 43986
* lantiq: BT Home Hub3A - device treeJohn Crispin2015-01-081-0/+210
| | | | | | | | BT Home Hub3A - device tree Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> SVN-Revision: 43877
generated by cgit v1.1 at 2024-10-31 09:28:41 +0000