aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ath79/dts/qca9563_ubnt_unifiac.dtsi
Commit message (Collapse)AuthorAgeFilesLines
* ath79: remove model name from LED labelsAdrian Schmutzler2020-10-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, we request LED labels in OpenWrt to follow the scheme modelname:color:function However, specifying the modelname at the beginning is actually entirely useless for the devices we support in OpenWrt. On the contrary, having this part actually introduces inconvenience in several aspects: - We need to ensure/check consistency with the DTS compatible - We have various exceptions where not the model name is used, but the vendor name (like tp-link), which is hard to track and justify even for core-developers - Having model-based components will not allow to share identical LED definitions in DTSI files - The inconsistency in what's used for the model part complicates several scripts, e.g. board.d/01_leds or LED migrations from ar71xx where this was even more messy Apart from our needs, upstream has deprecated the label property entirely and introduced new properties to specify color and function properties separately. However, the implementation does not appear to be ready and probably won't become ready and/or match our requirements in the foreseeable future. However, the limitation of generic LEDs to color and function properties follows the same idea pointed out above. Generic LEDs will get names like "green:status" or "red:indicator" then, and if a "devicename" is prepended, it will be the one of an internal device, like "phy1:amber:status". With this patch, we move into the same direction, and just drop the boardname from the LED labels. This allows to consolidate a few definitions in DTSI files (will be much more on ramips), and to drop a few migrations compared to ar71xx that just changed the boardname. But mainly, it will liberate us from a completely useless subject to take care of for device support review and maintenance. To also drop the boardname from existing configurations, a simple migration routine is added unconditionally. Although this seems unfamiliar at first look, a quick check in kernel for the arm/arm64 dts files revealed that while 1033 lines have labels with three parts *:*:*, still 284 actually use a two-part labelling *:*, and thus is also acceptable and not even rare there. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: move dts-v1 statement to ath79.dtsiAdrian Schmutzler2020-09-251-2/+2
| | | | | | | | | | | | | | | | | | | The "/dts-v1/;" identifier is supposed to be present once at the top of a device tree file after the includes have been processed. In ath79, we therefore requested to have in the DTS files so far, and omit it in the DTSI files. However, essentially the syntax of the parent ath79.dtsi file already determines the DTS version, so putting it into the DTS files is just a useless repetition. Consequently, this patch puts the dts-v1 statement into the parent ath79.dtsi, which is (indirectly) included by all DTS files. All other occurences are removed. Since the dts-v1 statement needs to be before any other definitions, this also moves the includes to make sure the ath79.dtsi or its descendants are always included first. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: drop redundant status for gpio target-wideAdrian Schmutzler2020-07-031-4/+0
| | | | | | | | All definitions of gpio in SoC DTSI files do not set status, i.e. have it enabled. This drops all remaining redundant "status = okay" definitions in descendent files (mostly older ones). Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: drop and consolidate redundant chosen/bootargsAdrian Schmutzler2020-06-251-4/+0
| | | | | | | | | | | | | | In ath79, for several SoCs the console bootargs are defined to the very same value in every device's DTS. Consolidate these definitions in the SoC dtsi files and drop further redundant definitions elsewhere. The only device without any bootargs set has been OpenMesh OM5P-AC V2. This will now inherit the setting from qca955x.dtsi Note that while this tidies up master a lot, it might develop into a frequent pitfall for backports. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: rename EEPROM to artAdrian Schmutzler2019-11-271-3/+3
| | | | | | | | | | | | | This renames all remaining occurrences of "EEPROM" to "art" to further harmonize the partition labelling in ath79. This will help to reduce the amount of user-space code and might be beneficial when code is copy/pasted in the future. Affected are only devices from Ubiquiti, where the XM board is already using "art" in ath79. Acked-by: Piotr Dymacz <pepe2k@gmail.com> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: remove wmac mtd-mac-address for UniFi AC familyRoger Pueyo Centelles2019-11-031-1/+1
| | | | | | | | | | | | | | | | The MAC address for the wmac 2.4 GHz radio of the Ubiquiti UniFi AC family of devices is actually embedded in the mtd-cal-data, so there is no need for mtd-mac-address (which was incorrectly forcing wmac to have the same MAC as eth0). This makes it coherent with the stock firmware and the ar71xx target: · XX:XX:XX:X0:XX:XX eth0 · XX:XX:XX:X1:XX:XX ath0/wlan1 (2.4 GHz) · XX:XX:XX:X2:XX:XX ath1/wlan0 (5 GHz) Checked on a UniFi AC Mesh, a UniFi AC LR and a UniFi Lite. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ath79: fix whitespace issues in DTS filesAdrian Schmutzler2019-10-061-1/+0
| | | | | | | | | This is the result of grepping/searching for several common whitespace issues like double empty lines, leading spaces, etc. This patch fixes them for the ath79 target. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix UniFi AC LED mappingDavid Bauer2019-09-121-4/+9
| | | | | | | | | | | The UniFi AC LED mapping is currently off. The blue/white LED are used as WiFi indicators, while the vendor firmware does not feature WiFI LEDs. Instead, the LEDs are used to indicate the devices status. Align the LED mapping to match the vendor firmware as good as possible. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: Fix UBNT Unifi AC LEDsPaul Wassi2018-12-311-2/+2
| | | | | | | Both LEDs on these devices are ACTIVE_HIGH, change back to what it is on ar71xx. Signed-off-by: Paul Wassi <p.wassi@gmx.at>
* treewide: dts: Remove default-state=off property from all gpio LED nodesPetr Štetiar2018-12-171-2/+0
| | | | | | | | | | | | | | | | | | >From the Documentation/devicetree/bindings/leds/common.txt: - default-state : The initial state of the LED. Valid values are "on", "off", and "keep". If the LED is already on or off and the default-state property is set the to same value, then no glitch should be produced where the LED momentarily turns off (or on). The "keep" setting will keep the LED at whatever its current state is, without producing a glitch. The default is off if this property is not present. So setting the default-state of the LEDs to `off` is redundant as `off` is default LED state anyway. We should remove it as almost every new PR/patch submission contains this property by default which seems to be just copy&paste from some DTS file already present in the tree. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: specify "firmware" partition format for Ubiquiti UniFiRafał Miłecki2018-11-241-0/+1
| | | | | | | | | | | | This affects: 1. Ubiquiti UniFi-AC-LITE/LR 2. Ubiquiti UniFi-AC-PRO 3. Ubiquiti UniFi-AC-MESH 4. Ubiquiti UniFi-AC-MESH PRO Succesfully tested on UniFi AP AC Pro. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ath79: fix dts warningsMathias Kresin2018-08-081-4/+0
| | | | | | | Fix all issues found by the devicetree compiler like wrong address/size cells as well as wrong/missing/superfluous unit addresses. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ath79: remove bs-partition ro-flag for UniFi AC devicesChristoph Krapp2018-07-041-1/+0
| | | | | | | | | | | | This removes the read-only flag from the bs (bootselect) partition on UniFi AC devices. This allows to correct the indicator from which partition the device is booting its kernel from. See also: - freifunk-gluon/gluon#1301 - https://bugs.lede-project.org/index.php?do=details&task_id=662 Signed-off-by: Christoph Krapp <achterin@googlemail.com>
* ath79: add support for Ubiquiti UniFi AC-ProLucian Cristian2018-06-281-0/+122
rework the dts to a common unifi-ac dtsi pro network is connected via phy0 and has usb ports lite network is connected via phy4 without usb ports Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>