aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/M2M.dts
Commit message (Collapse)AuthorAgeFilesLines
* ramips: update device tree source filesL. D. Pinney2017-08-031-5/+6
| | | | | | | | 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>
* treewide: dts: use keycode defines from input dt-bindingMathias Kresin2016-11-131-2/+4
| | | | | | | | | | | | | | | | | | | | | 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: fix size-cells on spi nodesÁlvaro Fernández Rojas2016-05-181-1/+1
| | | | | | size-cells should be 0 in order to avoid dummy values in reg properties. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ramips: DTS reworkStanislav Galabov2016-05-121-60/+58
| | | | | | | | Add node aliases to dtsi files. Reword dts files so they're more in-line with upstream. Fix some more warnings and errors reported by dtc Signed-off-by: Stanislav Galabov <sgalabov@gmail.com>
* ramips: Change all '/include/' clauses to '#include' so preprocessing canStanislav Galabov2016-05-101-1/+1
| | | | | | be done properly for the entire device trees. Signed-off-by: Stanislav Galabov <sgalabov@gmail.com>
* ramips: update DTS files to use jedec,spi-nor compatible string for m25p80 ↵Felix Fietkau2015-12-181-1/+1
| | | | | | | | to fix probe issues Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47935
* ralink: fixup devicetree files to work with new ethernet driverJohn Crispin2015-12-171-1/+1
| | | | | | Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 47900
* ramips: fix indentation and other mistakes in .dts{, i} filesJohn Crispin2015-08-171-0/+5
| | | | | | | | | | | | | | | | | | | | The following patch fixes: * wrong indentations * doubled gpio-keys-polled nodes (DIR-300-B7, DIR-320-B1, DIR-610-A1) * duplicate spacings * empty lines at end of files and after last child nodes * trailing and leading whitespace * unnecessary and commented-out code * missing empty lines between nodes and between properties and nodes * unnecessary empty lines between nodes properties [1] in .dts{,i} files, for ramips target. [1] Some of empty lines in SOCs dtsi files were left untouched, because they seem to be there for a reason (readability?). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> SVN-Revision: 46613
* ramips: improve and fix Memory 2 Move supportJohn Crispin2015-01-221-17/+11
| | | | | | | | | | | | | | | | | This patch is a follow up for my previous patch: "ramips: add support for Intenso Memory 2 Move USB 3.0". It fixes a couple of errors in the DTS (one of which broke the gpio-buttons). The kmod-leds-gpio dependency has been dropped as it is already part of the ramips target. Furthermore the ramdisk/uImage image is generated by default for the rt3050 subtarget. This image is needed to flash OpenWrt for the first time onto the device via TFTP. Signed-off-by: Christian Lamparter <chunkeey@googlemail.com> SVN-Revision: 44072
* ramips: add support for Intenso Memory 2 Move USB 3.0John Crispin2015-01-171-0/+113
This adds support for a rt5350-based "portable nas" solution from Intenso. The board comes with 32M RAM and 8M Flash, the built-in HDD is connected/accessible via a usb3.0<->sata bridge VLI VL701. The device has 1 Ethernet port (100M/10M), 1 micro b usb 3.0 socket (for charging the battery, or accessing the hdd directly). Wireless connectivity is provided by the rt5350 SoC [i.e.: 802.11n 1x1 2.4 GHz with a pcb antenna.] Serial, leds, wifi, ethernet and usb are tested and as far as I can tell: they are working fine (tm). Signed-off-by: Christian Lamparter <chunkeey@googlemail.com> SVN-Revision: 44001