aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/dts/BTHOMEHUBV3A.dts
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-12/+10
| | | | | | | | | | | | | | | | | 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: fix button keys codes used in dtsMathias Kresin2016-11-271-1/+1
| | | | | | Use keycodes that matches the intended use case based on the label. 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-15/+0
| | | | | | | | | | | | | | - 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: Sanitize device tree filesAndreas Eberlein2016-10-191-19/+19
| | | | | | | | | | 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-7/+7
| | | | | | The chosen node is clearly the wrong place for aliases. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: mac address setting on BTHOMEHUBV3ABen Mulvihill2016-07-051-2/+1
| | | | | | | | | | Rename uboot environment partition on BT Home Hub 3A so that mac address setting works correctly. Also, the mac address field in the ath9k calibration data is not used, and should not be referenced in the dts. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
* lantiq: move partitions into partion table nodeblogic2016-05-101-25/+31
| | | | | | | | | | 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: remove read-only flag on two partitions on BTHOMEHUBV3AJohn Crispin2016-04-261-2/+0
| | | | | | | | | | | Remove read-only flag on two partitions on BTHOMEHUBV3A: uboot-config - otherwise fw_setenv command cannot be used. ath9k-cal - so that ath9k calibration data can be copied to the partition on a newly installed board. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> SVN-Revision: 49250
* lantiq: use devicename:colour:function led naming schemeJohn Crispin2016-01-011-9/+9
| | | | | | | | | | | | | | | | 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-4/+8
| | | | | | | | | | | | | | 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-3/+8
| | | | | | | | | | - 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: 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.2.3 (git 2.25.1) at 2024-11-01 18:18:12 +0000