aboutsummaryrefslogtreecommitdiff
path: root/target/linux/bcm63xx/dts/bcm6348.dtsi
Commit message (Collapse)AuthorAge
* bcm63xx: drop targetÁlvaro Fernández Rojas2024-03-04
| | | | | | | | | | | | BCM63xx maintainance is a PITA since there's no full Device Tree support and therefore every board needs it's own definition in board_bcm963xx.c There's no DSA support for this board and there have been very few contributions in the last years. Moreover, BCM63xx SoCs >= BCM6358 are already supported in bmips target, so any efforts to keep this target alive aren't worth the time. Let's focus the community efforts on improving bmips instead. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: pinctrl: fix BCM6348 groupsDaniel González Cabanelas2021-02-23
| | | | | | | | | | | | | | | | | | | | The current driver has some troubles: - Some groupings are wrong. - The pinctrl group0 owns pins never used (at least in Openwrt) for any pinmux. The driver hijacks all the pins on the group avoiding any other use, spite they're free. I.e. for buttons, causing this kernel error: [ 4.735928] gpio-keys-polled keys: unable to claim gpio 479, err=-22 [ 4.742642] gpio-keys-polled: probe of keys failed with error -22 - Minor errors about groupings on the documentation - Missing "diag" grouping in dtsi - Wrong groupings in dtsi Fix it by setting the correct groups. And relax the pin capturing, letting the gpios belonging to any group to be used for other purposes like buttons. This was the behavior with stock firmwares and old OpenWrt versions which never caused any trouble. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* bcm63xx: move dts-v1 statement to top-level DTSI filesAdrian Schmutzler2020-10-10
| | | | | | | | | | | The "/dts-v1/;" identifier is supposed to be present once at the top of a device tree file after the includes have been processed. Like done for other targets recently, put the dts-v1 statement into the top-level SoC-based DTSI files, and remove all other occurences. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* brcm63xx: rename target to bcm63xxAdrian Schmutzler2020-02-14
This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>