summaryrefslogtreecommitdiff
path: root/target/linux/lantiq/dts/BTHOMEHUBV5A.dts
Commit message (Collapse)AuthorAgeFilesLines
* 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-6/+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: 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-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: 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: BTHOMEHUBV5A - use the power event code for the restart buttonMathias Kresin2016-06-201-1/+1
| | | | | | | | | | The restart event code is used in LEDE to trigger a factory reset on long press as well. By using the power event code, the restart functionality can be used without being prone to trigger a factory reset. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: move partitions into partion table nodeblogic2016-05-101-21/+27
| | | | | | | | | | 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: BTHOMEHUBV5A - explicit select the flash deviceJohn Crispin2016-02-081-1/+1
| | | | | | | | | | | | | The stock u-boot doesn't disable unused flash banks. Therefore, the nand driver tries to initialize a not connected NOR flash and the device hangs on boot. Workaround the issue by selecting the second flash bank (NAND). Signed-off-by: Mathias Kresin <openwrt@kresin.me> Acked-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48657
* lantiq: Move the definition of the xrx200-net node to vr9.dtsiFelix Fietkau2016-01-291-90/+80
| | | | | | | | | | 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: 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-3/+11
| | | | | | | | | | | | | | 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-2/+7
| | | | | | | | | | - 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: 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
generated by cgit v1.1 at 2025-03-21 13:16:00 +0000