aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm63xx/dts/homehub2a.dts
Commit message (Collapse)AuthorAgeFilesLines
* brcm63xx: use more systematic names for image and DTS filesAdrian Schmutzler2020-02-081-171/+0
| | | | | | | | | | | | | | | | | | | | This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* brcm63xx: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-02-051-1/+1
| | | | | | | | | | | | | | In DTS Checklist[1] we're now demanding proper generic node names, as the name of a node should reflect the function of the device and use generic name for that[2]. Everybody seems to be copy&pasting from DTS files available in the repository today, so let's unify that naming there as well and provide proper examples. 1. https://openwrt.org/submitting-patches#dts_checklist 2. https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation Signed-off-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* ath79, brcm63xx: Fix debounce-interval properties in gpio-keys-polled nodesPetr Štetiar2018-12-171-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes wrong usage of debounce-interval subnode property of gpio-keys-polled nodes, which was used inproperly in parent node, but it belongs to the subnodes, excerpt from the docs: Optional subnode-properties: - debounce-interval: Debouncing interval time in milliseconds. If not specified defaults to 5. And the docs are up to date as the source code matches that description as well: if (fwnode_property_read_u32(child, "debounce-interval", &button->debounce_interval)) button->debounce_interval = 5; While at it, I've also re-formatted gpio-keys-polled nodes, usually just adding new lines after every key subnode. Cc: Tomasz Maciej Nowak <tomek_n@o2.pl> Cc: Matt Merhar <mattmerhar@protonmail.com> Cc: Jonas Gorski <jonas.gorski@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* brcm63xx: drop linux,part-probe usage where possibleJonas Gorski2018-07-291-2/+0
| | | | | | | It was present as 4.4 compatibility, but since we now use 4.9 or later with the new upstream solution, we don't need it anymore. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: drop root parameter from cmdlineJonas Gorski2018-02-131-1/+1
| | | | | | | | | | | The root= parameter overrides the automatic rootfs detection by partition name, so drop it. Fixes boot from flash after renumeration changes of partitions due to parser changes. Fixes FS#1350. Fixes: a27d59bb4274 ("brcm63xx: switch to new partition layout specification") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: switch to new partition layout specificationJonas Gorski2018-02-111-11/+18
| | | | | | | Now that we support parsing the expected upstream definition, update the dts files to it. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: register serial through device treeJonas Gorski2017-12-161-0/+5
| | | | | | | Register serial consoles through device tree instead of through board data. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: switch to hardware led controllersJonas Gorski2017-06-101-84/+95
| | | | | | | Instead of bit banging SPI to talk to the GPIO chip, use the hardware led controllers intended for controlling the LEDs. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: add pinctrl supportJonas Gorski2017-06-101-6/+6
| | | | | | | Add and enable pincontrol drivers, and update dts(i) files with appropriate hogs. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* treewide: dts: use keycode defines from input dt-bindingMathias Kresin2016-11-131-1/+1
| | | | | | | | | | | | | | | | | | | | | 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>
* treewide: dts: fix dtc compiler warningsMathias Kresin2016-11-121-1/+1
| | | | | | | | | | | Fixes invalid device tree parameters. Drop the mvsw61xx node used in mvebu device tree source files. It looks like some kind of ethernet switch cargo cult. Neither the marvell,88e6352 nor the marvell,88e6172 compatible strings can be found in any LEDE file or in the kernel sources. Signed-off-by: Mathias Kresin <dev@kresin.me>
* brcm63xx: move the bootargs into the dtb filesJonas Gorski2016-06-211-0/+4
| | | | | | Instead of using a fixed commandline, allow one per device. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: make use of dt-includesJonas Gorski2015-07-161-3/+5
| | | | | | | | | Now that we have a dtc command that invokes the preprocessor, make use of it and replace the magic numbers with KEY_* defines. Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 46391
* brcm63xx: Add BT Home Hub 2A support.Jonas Gorski2015-03-251-0/+140
Support for the BT HomeHub 2.0 Type A. This router was manufactured by Thomson, and it's BCM6358 based. The leds are controled by two chained HC594, all working ok. The BCM5325 switch has the RESET# pin wired to the GPIO15, but currently there is no way to tell the b53 driver how to get this gpio number in brcm63xx, therefore swconfig won't use it when performing a switch reset. The patch was tested with several firmwares, and all except unsupported stuff (i.e xDSL) works pretty well. Tested-by: Tahir <tahir00ali@gmail.com> Signed-off-by: Daniel Gonzalez <dgcbueu@gmail.com> SVN-Revision: 44985