aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/files
Commit message (Collapse)AuthorAgeFilesLines
* lantiq: flag FritzBox 7360 family buttons active-lowDavid Bauer2022-01-141-2/+2
| | | | | | | | All buttons of the FritzBox 7360 family are active-low, not active-high. Corrent the GPIO flag. This fixes release triggers upon push of a button. Reported-by: Jan-Niklas Burfeind <git@aiyionpri.me> Signed-off-by: David Bauer <mail@david-bauer.net>
* lantiq: replace patches with version accepted upstreamAleksander Jan Bajkowski2022-01-081-2/+0
| | | | | | Replace recently added patches with version accepted upstream. Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
* lantiq: ar7: use okli loader for FRITZ!BoxMathias Kresin2021-11-272-0/+8
| | | | | | | | | | With Kernel 5.10 the ar7 FRITZ!Box are not booting the initramfs nor the sysupgrade image any more. Presumably due to the grown kernel. Use the okli preloader to workaround the bootloader issue. No solution so far for the initramfs. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: improve ethernet performanceAleksander Jan Bajkowski2021-11-154-0/+8
| | | | | | | | This commit contains a series of fixes for DMA. The burst length patch significantly improves Ethernet performance. Patches were tested on the xRX200 and xRX330. Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
* lantiq: fix mac address from nvmem-cellsMathias Kresin2021-11-142-2/+0
| | | | | | | | | | The devicetree property mac-address is expected to be set by the bootloader and has priority over the nvmem supplied one. Drop the mac-address address property from the dtsi files, to let the mac address from nvmem-cells get used. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ath9k: OF: qca,disable-(2|5)ghz => ieee80211-freq-limitChristian Lamparter2021-10-302-2/+2
| | | | | | | | | | | | | | | | | | OpenWrt maintains two special out-of-tree DT properties: "qca,disable-5ghz" and "qca,disable-2ghz". These are implemented in a mac80211 ath9k patch "550-ath9k-disable-bands-via-dt.patch". With the things being what they are, now might be a good point to switch the devices to the generic and upstream "ieee80211-freq-limit" property. This property is much broader and works differently. Instead of disabling the drivers logic which would add the affected band and channels. It now disables all channels which are not within the specified frequency range. Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Tested-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> # HH5A Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* lantiq: kernel: xway-nand: Move ECC engine setting to new DT bindingDaniel Kestrel2021-10-0212-7/+22
| | | | | | | | | | | | | | | | When trying to add support for another device with Micron NAND chips, it was discovered that the default setting in the kernel source does not work with Micron Chips, since the device trees setting is overwritten and hard coded by the kernel xway_nand driver. This was the original reason for this PR. A kernel patch sets the default ECC mode to soft without overwriting the device tree settings and the device tree for devices using it are updated with new parameters because the old ones are deprecated by torvalds/linux@533af69. A patch for kernel 5.4 is provided to support the new settings because kernel 5.4 does not support it. Signed-off-by: Daniel Kestrel <kestrel1974@t-online.de>
* lantiq: convert mtd-mac-address to nvmem for Fritz!Box 736xAdrian Schmutzler2021-08-204-5/+48
| | | | | | | Convert this series by moving the definitions to the individual devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: convert mtd-mac-address to nvmem implementationAnsuel Smith2021-07-1921-30/+270
| | | | | | | Define nvmem-cells and convert mtd-mac-address to nvmem implementation. The conversion is done with an automated script. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* treewide: convert mtd-mac-address-increment* to generic implementationAnsuel Smith2021-07-1910-11/+11
| | | | | | | | | | | | | Rework patch 681-NET-add-mtd-mac-address-support to implement only the function to read the mac-address from mtd. Generalize mtd-mac-address-increment function so it can be applied to any source of of_get_mac_address. Rename any mtd-mac-address-increment to mac-address-increment. Rename any mtd-mac-address-increment-byte to mac-address-increment-byte. This should make simplify the conversion of target to nvmem implementation. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* lantiq: xrx200: switch the subtarget to the mainline DSA driverMartin Blumenstingl2021-06-2618-1036/+840
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable the XRX200 PMAC, GSWIP DSA tag and GSIP DSA drivers in the 5.4 kernel config. Update the existing vr9_*.dts{,i} to use the new Ethernet and switch drivers. Drop the swconfig package from the xrx200 target because swconfig doesn't manage DSA based switches. The new /etc/config/network format for the DSA driver is not compatible with the old (swconfig) based one. Show a message during sysupgrade notifying users about this change and asking them to start with a fresh config (or forcefully update and then migrate the config manually). Failsafe mode can now automatically bring up the first lan interface based on board.json including DSA based setups. Drop 05_set_preinit_iface_lantiq from the xRX200 sub-target as this is not needed anymore. For now we are keeping it for the ase, xway and xway_legacy until there's some confirmation that it can be dropped from there as well. While here, some boards also receive minor fixups: - Use LAN1 as LAN1 (according to a photo this port can also be configured as WAN) on the Buffalo WBMR-300HPD. This makes it easier to read the port mapping because otherwise we would have LAN{2,3,4} and WAN (which was the case for the non-DSA version previously). - vr9_avm_fritz3390.dts: move the "gpio" comment from port 0 and 1 to their corresponding PHYs - vr9_tplink_vr200.dtsi: move the "gpio" comment from port 0 to PHY 0 - vr9_tplink_tdw89x0.dtsi: move the "gpio" comment from port 0 to PHY 0 Acked-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Tested-by: Notupus <notpp46@googlemail.com> # TD-W9980/DM200/FRITZ 7430 Tested-by: Martin Schiller <ms@dev.tdt.de> # tested on TDT VR2020 Tested-by: Martin Schiller <ms@dev.tdt.de> # tested on TP-Link TD-W8980B Tested-by: Martin Schiller <ms@dev.tdt.de> # tested on ZyXEL P-2812HNU-F1 Tested-by: Daniel Kestrel <kestrel1974@t-online.de> # tested on Fritzbox 7490 Tested-by: Daniel Kestrel <kestrel1974@t-online.de> # tested on Fritzbox 3490 Tested-by: @jospezial <jospezial@gmx.de> # tested on VGV7510KW22 (o2 Box 6431) Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: mark PCI bridges as suchMathias Kresin2021-04-123-0/+6
| | | | | | | | Use the device_type property to mark PCI host bridges as such. With linux 5.10 it is mandatory, otherwise the PCI IO space is flages as PCI memory and the PCI init fails. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add basic support for AVM FRITZ!Box 3390Andreas Böhler2021-04-031-0/+308
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The FRITZ!Box 3390 actually contains two SoCs, one Lantiq with a 5GHz WiFi and one AR9342 with a 2.4GHz WiFi. Only the Lantiq has access to the flash memory, the Atheros runs fully from RAM. Specifications -------------- - Lantiq 500 MHz - 128MiB RAM - 128MiB NAND - 256k Flash - AR9580 5GHz WiFi - AR9342 560 MHz - 64MiB RAM - AR9328 2.4GHz WiFi Remarks ------- This commit only adds support for the Lantiq side of things and prepares the drivers for communication with the Atheros SoC. Thus, only 5GHz WiFi works by default, the 2.4GHz WiFi will be added via another target. Some kernel patches will be required to add support for the Atheros SoC. Installation ------------ Use the eva_ramboot.py script to boot the initramfs image. Then, transfer the sysupgrade image to the device and run sysupgrade to flash it to the NAND. Signed-off-by: Andreas Böhler <dev@aboehler.at> Acked-by: Aleksander Jan Bajkowski A.Bajkowski@stud.elka.pw.edu.pl Signed-off-by: Joachim Cerny <cocktail_yogi@web.de>
* lantiq: VR9: fix gpio-hog by defining the GPIO rangesJoachim Cerny2021-04-031-0/+1
| | | | | | | | | | defined gpio-ranges according to Reference: https://github.com/torvalds/linux/blob/master/drivers/pinctrl/pinctrl-xway.c#L864 This change is needed by gpio-hog on Fritzbox 3390 thx to @abajk Acked-by: Aleksander Jan Bajkowski A.Bajkowski@stud.elka.pw.edu.pl Signed-off-by: Andreas Böhler <dev@aboehler.at> Signed-off-by: Joachim Cerny <cocktail_yogi@web.de>
* lantiq: vr9: set the usb led trigger via devicetreeMathias Kresin2021-03-015-20/+36
| | | | | | | | | | Assign the usbdev trigger via devicetree and drop the userspace handling of the usb leds. Drop the now unused userspace helper code as well. Signed-off-by: Mathias Kresin <dev@kresin.me> Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: ARV752DPW22: set the usb led trigger via devicetreeMathias Kresin2021-03-012-1/+34
| | | | | | | | | | Assign the usbdev trigger via devicetree and drop the userspace handling of the usb leds Add the PCI attached usb controller as trigger sources for the usb led as well. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fritz7320: enable USB power supplyMathias Kresin2021-02-181-0/+46
| | | | | | | | | | | | The USB ports if a FRIZZ!Box 7320 do not supply power to connected devices. Add the GPIOs enabling USB power as regulator, to enable USB power supply as soon as the USB driver is loaded. Fixes FS#3624 Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: change phy-mode to mii for FRITZ!Box 7412Aleksander Jan Bajkowski2021-02-051-1/+1
| | | | | | | | | | | FRITZ!Box 7412 loads the firmware for fast ethernet PHY and mii is more accurate in this case. Gmii is used by Gigabit ethernet PHYs. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Reviewed-by: Mathias Kresin <dev@kresin.me> [minor commit title/message adjustments] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: xrx200: remove redundant stp parametersAleksander Jan Bajkowski2020-12-193-10/+0
| | | | | | | These parameters are the same as in vr9.dtsi. This patch removes redundant parameters. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* lantiq: xrx200: remove unused lan/wan labels from dtsAleksander Jan Bajkowski2020-12-1412-13/+13
| | | | | | These labels are not used anywhere and can be removed. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* lantiq: add support for AVM FRITZ!Box 7430Leon Maurice Adam2020-10-271-0/+273
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware: - SoC: Lantiq VRX 220 - CPU: 2x MIPS 34Kc 500 MHz - RAM: 128 MiB 250 MHz - Flash: 128 MiB NAND - Ethernet: Built-in Fast Ethernet switch, 4 ports used - Wifi: Atheros AR9381-AL1A b/g/n with 2 pcb/internal and 1 external antennas - USB: 1x USB 2.0 - DSL: Built-in A/VDSL2 modem - DECT: Dialog SC14441 - LEDs: 1 two-color, 4 one-color - Buttons: 1x DECT, 1x WIFI - Telephone connectors: 1 FXS port via TAE or RJ11 connector With the exception of FXS/DECT everything works (there are no drivers for AVM's FXS or DECT implementation), DSL is yet untested. Installation: Boot up the device and wait a few seconds. Run the eva_ramboot.py script in scripts/flashing/ to load the initramfs image on the device: $ ./scripts/flashing/eva_ramboot.py 192.168.178.1 <path to your initramfs image> If the script fails to reach the device, maybe try 169.254.120.1. Wait until booting is complete. You should now be able to reach your device under the default ip address 192.168.1.1. Before flashing, check if linux_fs_start is not set to 1 in the tffs partition: $ fritz_tffs_nand -d /dev/mtd1 -n linux_fs_start If linux_fs_start is 1, you will need to reset it to 0, either by FTP, upgrading FritzOS or doing a recovery. Now you should be able to flash the device using sysupgrade. Signed-off-by: Leon Maurice Adam <leon.adam@aol.de> Acked-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> [drop BOARD_NAME, use wpad-basic-wolfssl, drop 4.19, drop dts-v1, remove model prefix from LED names] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: fix indent in vr9_avm_fritz7412.dtsAdrian Schmutzler2020-10-271-1/+1
| | | | | | Indent should be tabs. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: remove support for kernel 4.19Adrian Schmutzler2020-10-1982-0/+12121
| | | | | | | | | | | | | The target uses 5.4 as default kernel since 06/2020. Kernel 4.19 support is not really maintained anymore, it does not seem to be needed and upcoming changes (mainly DSA) will break backward-compatibility anyway. Thus, make maintaining of old stuff and reviewing of new stuff easier by removing support for kernel 4.19. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: copy target to kernel 5.4Mathias Kresin2020-03-1681-12272/+0
| | | | | | | | | Duplicate kernel 4.19 config and patches for kernel 5.4. Duplicate the devicetree source files as well, they need kernel 5.4 specific adjustments. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: vgv7510kw22: fix missing wirelessMathias Kresin2020-03-161-2/+2
| | | | | | | | | | | | | | | | | | | | For some reason pin 7 (gphy0_led1_pins) need to be set to output prior to loading the PCI driver. Otherwise the wireless doesn't appear on the PCI bus. Of course, it doesn't make much sense, since pin 7 is used to drive the LAN1 led. It can either be done by setting the pins function to GPHY or GPIO + direction output. However, the pinctrl driver doesn't provide a way to switch a pin to GPIO. It is done indirectly by the pinctrl driver at the time a GPIO is requested (requesting a GPIO always resets the function to GPIO). Do it via pinmux driver, as it is always loaded first. Use the GPHY function as it's the pins intended purpose for this board. Fixes: FS#2895 Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: move mux for pins into subnodesMathias Kresin2020-03-153-115/+161
| | | | | | | | | | | The mux need to be defined in a subnode to be considered by the pinctrl framework. These muxes aren't set as expected and might cause not working subsystems. Fixes: 8e7b573b7aa4 ("lantiq: dts: assign the PCI pins to the PCI controller node") Fixes: dcb5e52209e5 ("lantiq: dts: assign the STP pins to the STP GPIO controller node") Fixes: 660200e53d62 ("lantiq: dts: assign the GPHY LED pins to the Ethernet controller node") Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: enable 5ghz wifi on VR200/VR200vKevin Schmidt2019-12-231-1/+20
| | | | | | Enable mt76 driver on VR200/VR200v. Signed-off-by: Kevin Schmidt <kevin.patrick.schmidt@googlemail.com>
* lantiq: move include to parent falcon_lantiq_easy98000.dtsiAdrian Schmutzler2019-12-224-6/+2
| | | | | | | This moves the include of lantiq.dtsi from the DTS files to the parent falcon_lantiq_easy98000.dtsi. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: remove ar9_lantiq_easy50810.dtsAdrian Schmutzler2019-12-221-73/+0
| | | | | | This file seems to be orphaned, no device setup existing for it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: use soc_vendor_device scheme on DTS fileAdrian Schmutzler2019-12-2282-33/+33
| | | | | | | | | | | | This renames lantiq DTS(I) files to follow soc_vendor_device scheme. This will make DTS files easier to maintain. As a side effect, DTS file name can be derived from device node names now, only having to specify a SOC variable in Makefiles. While at it, move files to arch/mips/boot/dts/lantiq subfolder. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: dts: assign the ASC pins to the serial controller nodeMartin Blumenstingl2019-12-223-8/+9
| | | | | | | | Assign the ASC pins to the serial controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the PCI pins to the PCI controller nodeMartin Blumenstingl2019-12-2227-260/+213
| | | | | | | | Assign the PCI pins to the PCI controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the STP pins to the STP GPIO controller nodeMartin Blumenstingl2019-12-2211-68/+36
| | | | | | | | Assign the STP pins to the STP GPIO controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the GPHY LED pins to the Ethernet controller nodeMartin Blumenstingl2019-12-227-54/+71
| | | | | | | | Assign the GPHY LED pins to the Ethernet controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the NAND pins to the nand-controller nodeMartin Blumenstingl2019-12-2216-85/+112
| | | | | | | | | | | | Assign the NAND pins to the NAND controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. While here, define all NAND pins (CLE, ALE, read/RD, ready busy/RDY and CE/CS1). This means that the pinctrl subsystem knows that these pins are in use and cannot be re-assigned as GPIOs for example. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: define the SPI pins in {amazonse,ar9,vr9}.dtsiMartin Blumenstingl2019-12-2212-141/+66
| | | | | | | | | Define the SPI pins in the corresponding SoCs.dtsi and assign them to the SPI controller node. All known boards use CS4 and it's likely that this is hardcoded in bootrom so this doesn't bother with having per-board SPI pinmux settings. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the MDIO pins to the gsw nodeMartin Blumenstingl2019-12-2219-80/+27
| | | | | | | | | | | | Assign the MDIO pins to the switch node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. This converts amazonse, ar9 and vr9. danube is skipped because the pin controller doesn't define a pinmux for the MDIO pins (some of the SoC pads may be hardwired to the MDIO pins instead of being configurable). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* treewide: remove dts-v1 identifier from DTSI filesAdrian Schmutzler2019-12-081-1/+0
| | | | | | | | | | | | | | | | The "/dts-v1/;" identifier is supposed to be put once at the beginning of a device tree file. Thus, it makes no sense to provide it a second time in to-be-included DTSI files. This removes the identifier from all DTSI files in /target/linux. Most of the DTS files in OpenWrt do contain the "/dts-v1/;". It is missing for most of the following targets, though: mvebu, ipq806x, mpc85xx, ipq40xx This does not touch ipq806x for now, as the bump to 4.19 is close. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: unify Fritz!Box LED mappingsDavid Bauer2019-08-154-6/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | This commit unifies the LED mapping of the AVM Fritz!Box routers, which have a combined Power/DSL LED. With the stock firmware, the Power LED has the following characteristics: - Blink when DSL sync is being established - Solid when DSL sync is present We can't completely resemble this behavior in OpenWrt. Currently, the Power LED is completely off, when DSL sync is missing. This is not really helpful, as a user might have the impression, that he bricked his device. Instead, map the Info-LED to the state of the DSL connection. There is no consistent behavior for the Info-LED in the stock firmware, as the user can set it's function by himself. The DSL connection state is one possible option for the Info LED there. Also use the red Power LED to indicate a running upgrade, in case the board has a two-color Power LED. Signed-off-by: David Bauer <mail@david-bauer.net>
* lantiq: add led-upgrade alias for Fritz!Box 7412David Bauer2019-08-101-0/+1
| | | | | | | This adds the led-upgrade alias for the AVM Fritz!Box 7412 to indicate a running firmware upgrade. Signed-off-by: David Bauer <mail@david-bauer.net>
* lantiq: enable second VPE on Fritz!Box 7412David Bauer2019-08-101-1/+1
| | | | | | | | | The AVM Fritz!Box 7412 does not use the VMMC part of the Lantiq chip but rather a proprietary solution based on the DECT chip for the FXS ports. Therefore, the second VPE can be enabled for use with OpenWrt. Signed-off-by: David Bauer <mail@david-bauer.net>
* lantiq: correct Fritz!Box 7412 button logic levelDavid Bauer2019-08-101-2/+2
| | | | | | | | | The AVM FRITZ!Box 7412 buttons are both active low, which is currently incorrectly defined in the device-tree. This leads to the device booting directly into failsafe. Signed-off-by: David Bauer <mail@david-bauer.net>
* lantiq: dts: use generic node namesPetr Štetiar2019-07-0765-161/+155
| | | | | | | | | | | | | | | | | | 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> [split out treewide patch, integrated P2812HNUF1 rename patch] Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [merged key and led changes, use generic node name for flash, wifi and gpio] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: drop falcon clock nodeMathias Kresin2019-07-071-26/+0
| | | | | | | | | It is pretty ovbious a misuse of the simple-bus binding as no child has a address. Luckly the clock node isn't used at all so it is safe to get rid of it. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: drop empty falcon devicetree nodeMathias Kresin2019-07-071-6/+2
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: fix unit address mismatch warningMathias Kresin2019-07-071-2/+2
| | | | | | | | | Set a unit address matching the reg property for the EASY98000 ethernet node. Fixes a unit mismatch devicetree compiler warning. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: move localbus childs to dtsMathias Kresin2019-07-079-52/+80
| | | | | | | | The localbus childs are highly board specific and need to be part of the board dts. Otherwise we run into duplicate unit address issues if a board has something else (NAND) connected to the bus id. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: fix vmmc unit and register addressMathias Kresin2019-07-072-3/+3
| | | | | | | | | | The register address is the same for danube und vr9. The register size is 0x400 byte for danube and 0x300 byte for vr9. The change doesn't have an impact as the vmmc driver doesn't use the devicetree and has hardcoded register offsets. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: use lower case for hex valuesMathias Kresin2019-07-075-42/+42
| | | | | | Use only lower case for hex values to keep it consistent. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: drop superfluous address and size cellsMathias Kresin2019-07-0752-172/+3
| | | | | | | | Fixes the following devicetree compiler warning: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property Signed-off-by: Mathias Kresin <dev@kresin.me>
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-31 09:40:05 +0000