aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/ZBT-APE522II.dts
Commit message (Collapse)AuthorAgeFilesLines
* ramips: move partitions into partition table nodeAlex Maclean2018-08-041-22/+26
| | | | | | | | 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: Alex Maclean <monkeh@monkeh.net>
* ramips: fix dtc warningsMathias Kresin2018-08-041-2/+0
| | | | | | Fix individual boards dtc warnings or obvious mistakes. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix pci/pcie related dtc warningsMathias Kresin2018-08-041-7/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add the ranges property to the PCI bridges where missing. Add the unit address to PCI bridge where missing. Rework the complete rt3883 pci node. Drop the PCI unit nodes from the dtsi. They are not used by any dts file and should be rather in the dts than in the SoC dtsi. Express the PCI-PCI bridge in a clean devicetree syntax. The ralink,pci-slot isn't used by any driver, drop it. Move the pci interrupt controller out of the pci node. It doesn't share the same reg and therefore should be an independent/SoC child node. Move the pci related rt3883 pinctrl setting to the dtsi instead of defining the very same for each rt3883 board. If the device_type property is used for PCI units, the unit is treated as pci bridge which it isn't. Drop it for PCI units. Reference pci-bridges or the pci node defined in the dtsi instead of recreating the whole node hierarchy. It allows to change the referenced node in the dtsi without the need to touch all dts. Fix the PCI(e) wireless unit addresses. All our PCI(e) wireless chips are the first device on the bus. The unit address has to be the bus address instead of the PCI vendor/device id. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: use pinmux nodes from dtsiMathias Kresin2017-11-221-5/+2
| | | | | | | Use the pinmux nodes from the included dtsi file instead of adding duplicate nodes. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: update device tree source filesL. D. Pinney2017-08-031-6/+7
| | | | | | | | Use the GPIO dt-bindings macros and add compatible strings in the ramips device tree source files. Signed-off-by: L. D. Pinney <ldpinney@gmail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: cleanup SPI flash device tree properties usageMathias Kresin2017-02-021-1/+0
| | | | | | | | | Use only the jedec,spi-nor compatible string. Everything else either never worked or is only support to keep compatibility. Remove the linux,modalias property. It is obsolete since kernel 4.4. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mt76: update to the latest versionFelix Fietkau2017-02-011-1/+1
| | | | | | | | Uses upstream code to parse DT supported band/frequency information. Update existing .dts files to the new format and remove unnecessary overrides. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* treewide: dts: use keycode defines from input dt-bindingMathias Kresin2016-11-131-1/+3
| | | | | | | | | | | | | | | | | | | | | 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>
* ramips: add suport for ZBT APE522IIRoger Pueyo Centelles2016-06-221-0/+143
The ZBT APE522II is a dual-radio outdoor CPE based on the MT7620a SoC. It has 64 MB RAM, 8 MB flash, 2 Fast Ethernet ports via internal switch (one with 802.3af 48V PoE support), a 802.11b/g/n SoC 2.4 GHz radio and an 802.11a/n/ac MT7612E-based 5 GHz radio. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>