aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/dts/TDW89X0.dtsi
Commit message (Collapse)AuthorAgeFilesLines
* lantiq: fix console printHauke Mehrtens2017-01-051-0/+4
| | | | | | | | | | | | | | | | | | The boot loader of many boards provides a kernel boot argument with a broken console parameter to the kernel. This will be taken before the stdout-path defined in device tree and the serial will not work on this board. Multiple boards are affected by this problem, so revert this patch for all boards. Later we can remove the boot arguments from the device tree again, after the individual board was checked to work. This partly reverts this commit: commit 4995c64857a09c4cc92238ba0bd52cdb06c4c581 Author: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Date: Sun Dec 11 21:55:00 2016 +0100 lantiq: specify console using stdout-path instead of cmdline argument Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: remove "init" kernel command line parameter from bootargsMartin Blumenstingl2016-12-121-4/+0
| | | | | | | | | | /etc/preinit has been the default init-script for a very long time (at least since Linux 2.6.30 in OpenWrt). Remove the kernel command line "init" parameter to get rid of duplicate and inconsistent definitions of this parameter (some boards, like FRITZ3370 for example did not use it at all, while it's just copy and paste on others). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: specify console using stdout-path instead of cmdline argumentMartin Blumenstingl2016-12-121-1/+1
| | | | | | | | Use devicetree's /chosen/stdout-path instead of the kernel command line (embedded in the .dts-files) to specify the serial console. Using the chosen node is recommended on devicetree based platforms. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: use ath9k device tree bindings binding/owl-loaderMartin Blumenstingl2016-11-291-10/+31
| | | | | | | | | | | | | | | | | This moves the extraction of the eeprom/calibration data to a hotplug firmware script. Additionally it modifies all .dts to configure ath9k directly from within the .dts. The owl-loader approach enables support on devices with exotic eeprom data locations (such as unaligned positions on the flash or data inside an UBI volume). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> [add ath9k caldata mac address patcher] [fixes DGN3500 wifi mac] [fixes BTHOMEHUBV3A wifi mac] [set invalid mac for BTHOMEHUB2B, FRITZ3370, FRITZ7320 & FRITZ7360SL to restore previous random mac behavior] Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: dts: use keycode defines from input dt-bindingMathias Kresin2016-11-131-0/+2
| | | | | | | | | | | | | | | | | | | | | All compiled device tree files not mentioned are binary identical to the former ones. Fix the obvious decimal/hex confusion for the power key of ramips/M2M.dts. Due to the include of the input binding header, the BTN_* node names in: - ramips/GL-MT300A.dts - ramips/GL-MT300N.dts - ramips/GL-MT750.dts - ramips/Timecloud.dts will be changed by the compiler to the numerical equivalent. Move the binding include of lantiq boards to the file where they are used the first time to hint the user where the values do come from. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: cleanup dts filesMathias Kresin2016-11-031-1/+1
| | | | | | | | | | | | | | - remove not existing properties - remove properties having the same values as the included dtsi - remove nodes which are disabled in the included dtsi and not enabled in dts - replace the deprecated pinctrl-* compatible strings - use the same labels for nodes as the included dtsi - move common used vr9 pci properties to vr9.dtsi - remove the unused stp node from HomeHub 2B devcie tree source file - fix spaces vs. tabs and remove superfluous linebreaks Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: enable cpu temp driver for all vr9 boardsMathias Kresin2016-10-191-4/+0
| | | | | | | Only present on v1.2 vr9 SoCs but the driver takes care to not load on boards having a v1.1 SoC. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: Sanitize device tree filesAndreas Eberlein2016-10-191-16/+16
| | | | | | | | | | The device tree file of ARV752DPW uses numbers/hex values for gpio states and input event codes. This cleans it up and uses the available macros from header files. This way the functions are easier to read and comprehend. Signed-off-by: Andreas Eberlein <foodeas@aeberlein.de> [sanitize all device tree files] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use aliases device tree node for ledsMathias Kresin2016-10-051-9/+9
| | | | | | The chosen node is clearly the wrong place for aliases. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: enable cpu temp driver for selected boardsMathias Kresin2016-08-101-0/+4
| | | | | | | | According to the author of the cpu temp driver, not all xrx200 boards have a cpu temperature sensor. For that reason enable the sensor only for tested boards. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix mac address incrementsMathias Kresin2016-08-101-1/+1
| | | | | | | | | | | | Use the same mac address increment in device tree source file and userspace. Don't add a mac address increment to either the only mtd mac-address or to all mac-addresses. Fix a typo in the TDW89X0.dtsi file to add an increment. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: move partitions into partion table nodeblogic2016-05-101-18/+24
| | | | | | | | | | Starting with kernel 4.4, the use of partitions as direct subnodes of the mtd device is discouraged and only supported for backward compatiblity reasons. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49280
* lantiq: Move the definition of the xrx200-net node to vr9.dtsiFelix Fietkau2016-01-291-70/+59
| | | | | | | | | | This removes a lot of duplicate register and interrupt definitions by moving the xrx200-net definition to vr9.dtsi and making all devices re- use it. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48547
* lantiq: Remove incorrect PCIe compatible stringsFelix Fietkau2016-01-171-4/+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-171-6/+17
| | | | | | | | | | | | | | | | 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: 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: use devicename:colour:function led naming schemeJohn Crispin2016-01-011-6/+8
| | | | | | | | | | | | | | | | 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-011-2/+4
| | | | | | | | | | | | | | 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: define default leds in dts filesJohn Crispin2016-01-011-5/+14
| | | | | | | | | | - 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: 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-231-0/+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: 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-051-6/+1
| | | | | | | | | 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-021-2/+1
| | | | | | 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: Add target TP-Link TD-W8980John Crispin2015-10-051-0/+252
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-25 02:03:30 +0000