aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
...
* 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>
* lantiq: dts: move partitions into partition nodeMathias Kresin2019-07-074-88/+103
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: add missing size and address cellsMathias Kresin2019-07-074-0/+8
| | | | | | | | | | Add size and address cells where missing to fix the following devicetree compiler warning: Warning (avoid_default_addr_size): Relying on default #address-cells value Warning (avoid_default_addr_size): Relying on default #size-cells value Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: fix size cellsMathias Kresin2019-07-0711-11/+11
| | | | | | SPI nodes only need an address and no size. Drop the size everywhere. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: fix malformed unit addressesMathias Kresin2019-07-071-1/+1
| | | | | | | | Fixes: Warning (unit_address_format): unit name should not have leading "0x" Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: drop superfluous unit addressMathias Kresin2019-07-0720-68/+48
| | | | | | | | | | | | | The cpu temperature driver has the register offset hardcode and doesn't need a reg. The mdio bus node is only used as a well known name and doesn't need a reg or unit address. syscon-reboot doesn't have a unit address or a reg either. The unit name collides with reset-controller@10 anyway. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: add reg if unit address is setMathias Kresin2019-07-075-0/+29
| | | | | | | | | Add the reg property if the node has an unit address. Fixes the following device tree compiler warning: Warning (unit_address_vs_reg): node has a unit name, but no reg property Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: dts: move memory node to board dtsMathias Kresin2019-07-0747-16/+43
| | | | | | | The memory node is highly board specific and should be only defined in the board dts. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: convert DEVICE_TITLE to new variablesDaniel Golle2019-07-066-323/+704
| | | | | | Also unify naming and add details where they were missing. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ath79: Add DEVICE_VENDOR for Ubiquiti RouterstationAdrian Schmutzler2019-07-051-0/+1
| | | | | | | | This has been overlooked. Reported by: Chen Minqiang (@ptpt52) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: Correctly use DEVICE_VARIANT for NETGEAR WNDR3700Adrian Schmutzler2019-07-041-1/+3
| | | | Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: Move DEVICE_VENDOR for NETGEAR to parent definitionAdrian Schmutzler2019-07-043-6/+1
| | | | Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: split DEVICE_TITLE in multiple variablesPaul Spooren2019-07-048-140/+274
| | | | | | | | | | | | | | This allows the definition of DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT. All three are merged together to look the same as the current DEVICE_TITLE. Also, if DEVICE_TITLE is set it's directly used as a *fallback* for devices which weren't upgraded yet. This is based on the work of @sudhanshu16. The motivation is to create JSON files based on provided metadata, needing clear differentiation between vendor, model and revision. Signed-off-by: Paul Spooren <mail@aparcar.org>
* lantiq: drop kernel 4.14 supportMathias Kresin2019-07-0434-14836/+0
| | | | | | | The current state of the kernel 4.14 support is in the openwrt-19.07 branch. No need to keep a not default used kernel in this branch. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: switch to kernel 4.19Martin Blumenstingl2019-07-041-1/+1
| | | | | | Use kernel 4.19 by default. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: 4.19: fix panic when using the DMA APIMartin Blumenstingl2019-07-045-32/+127
| | | | | | | | | | | With kernel 4.19 the DMA API relies on a struct device to work properly. Backport upstream patches which passed a struct device instead of NULL to the DMA API. Fixes kernel panics during boot. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: 4.19: load PCIe driver after PCI driverMathias Kresin2019-07-041-4/+29
| | | | | | | | | | | | | | | | | | | | | | | | | In case a PCI device is physical present, the Lantiq PCI driver need to be loaded prior to the Lantiq PCIe driver. Otherwise none of them will work because updating the BAR 0 of a device attached to the PCIe Bus will fail. Till kernel commit 9667bb039bf6 ("MIPS: lantiq: remove unnecessary of_platform_default_populate call"), the Lantiq PCI driver was probed early in the boot process via plat_of_setup(). Since the mentioned commit, both drivers are probed via of_platform_default_populate_init() and they are probed according to their order in the devicetree source file. If the Lantiq PCI driver is enabled in the devicetree, defer the probing og the Lantiq PCIe driver till the Lantiq PCI driver is probed. Use the presence of a PCU bus as indicater for a loaded Lantiq PCI driver. This way we don't need to shuffle the PCI/PCIe nodes in the devicetree source file, as they are already (correctly) ordered based on the unit address. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: 4.19: increase usb reset timeoutsMartin Blumenstingl2019-07-042-0/+64
| | | | | | | | | | | With kernel 4.19 dwc2 would not want to initialize due to reset timeouts, while it worked fine with 4.14. Increase the reset timeouts to 1 second, as it was used by the old lantiq ifxhcd usb driver. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: make patches applyHauke Mehrtens2019-07-0422-282/+106
| | | | | | | | | | | | | | | | | | | | | | | | | | The following patches are dropped because they are now upstreamed: - 0002-gpio-stp-xway-Implement-get-callback.patch upstreamed with commit 5b9b2b5284f819 ("gpio: stp-xway: Implement get callback") - 0027-01-net-phy-intel-xway-add-VR9-version-number.patch upstreamed with commit 5b73d9955fb4b0 ("net: phy: intel-xway: add VR9 version number") - 0027-02-net-phy-intel-xway-add-VR9-v1.1-phy-ids.patch upstreamed with commit f452518c982e57 ("net: phy: intel-xway: add VR9 v1.1 phy ids") The following patches were updated: - 0018-MTD-nand-lots-of-xrx200-fixes.patch the mainline driver now resides in drivers/mtd/nand/raw/xway_nand.c (instead of drivers/mtd/nand/xway_nand.c) - 0025-NET-MIPS-lantiq-adds-xrx200-net.patch the DMA API now requires a valid device to be passed to all operations - 0028-NET-lantiq-various-etop-fixes.patch the DMA API now requires a valid device to be passed to all operations Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: copy target to kernel 4.19Hauke Mehrtens2019-07-04116-0/+14836
| | | | | | | | This just copies the files from the kernel 4.14 specific folders into the kernel 4.19 specific folder, no changes are done to the files in this commit. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: enable STP where referencedMathias Kresin2019-07-032-0/+2
| | | | | | | | | | | While moving common used parts to dtsi files, the was disabled by default but not enabled for all boards using the STP. Fixes: f519fea4c6db ("lantiq: kernel 4.14: cleanup dts files") Reported-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me> Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* ar71xx: fix ath79/rb4xx IRQ initialization on kernel 4.14W. Michael Petullo2019-07-031-1/+1
| | | | | | | | | | | | Apply the same approach as in commit 3b53d6fdbc24 ("ar71xx: fix pci irq init on kernel 4.14") to fix IRQ initialization for ath79-based chipsets on rb4xx. Ref: PR#2182 Acked-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Signed-off-by: W. Michael Petullo <mike@flyn.org> [commit ref fix] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: Use -v1 suffix for TP-Link WDR3600/4300Adrian Schmutzler2019-07-035-14/+14
| | | | | | | | | | | | | | | In ath79, identifiers tplink_tl-wdr3600 and tplink_tl-wdr4300 have been used while most other TP-Link devices include the revision. Although there actually is only one major revision of these devices, they bear the revision on their bottom (v1.x). TP-Link also refers to the devices as V1 on its web page. This patch thus adds -v1 to both so it is more consistent with other devices and with what you would expect from reading the on-device sticker and the support pages. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add support for TP-Link TL-WR841n v14Alexander Müller2019-07-024-0/+155
| | | | | | | | | | | | | | | | | | | | | | TP-Link TL-WR841n v14 is a router based on MediaTek MT7628N. - MediaTek MT7628NN - 32 MB of RAM - 4 MB of FLASH - 2T2R 2.4 GHz - 5x 10/100 Mbps Ethernet Installation: - copy the 'openwrt-ramips-mt76x8-tl-wr841n-v14-squashfs-tftp-recovery.bin' file to your tftp server root and rename it to 'tp_recovery.bin'. - configure your PC running the TFTP server with the static IP address 192.168.0.66/24 - push the reset button and plug in the power connector. Wait until the orange led starts blinking (~6sec) Signed-off-by: Alexander Müller <donothingloop@gmail.com> Signed-off-by: Alexander Couzens <lynxis@fe80.eu> [small modifications gpio-hog]
* ramips/leds: use devicetree alias led_wlanAlexander Couzens2019-07-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | Similiar to the lantiq target use a dts alias to define the wlan led instead of static mapping in /etc/board.d/01_leds. Reduce code duplication. A device tree must define the alias "led-wlan" similiar to "led-boot". / { aliases { led-wlan = &led_wlan; }; [..] led_wlan: wlan { label = "tl-wr841n-v14:green:wlan"; gpios = <&gpio1 9 GPIO_ACTIVE_LOW>; }; }; Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* gemini: Add StorLink SL93512r imagesLinus Walleij2019-07-011-7/+17
| | | | | | | | | | | This adds image generation for the StorLink reference design SL93512r. This board is now supported upstream in kernel v4.19. As this image structure is identical to SQ201 and Raidsonic, we simply refer to this as "storlink-reference" from now on. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* gemini: Drop switch kmod and swconfigLinus Walleij2019-07-011-1/+0
| | | | | | | | | The DIR-685 needs this module compiled in for safety (it is facing the LAN ports) and it is now (as of kernel v4.19) using the DSA switch architecture so swconfig is not needed. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* mvebu: add initial support for uDPU boardVladimir Vid2019-06-284-0/+188
| | | | | | | | | | | | | | | | | | | This adds initial support for micro-DPU (uDPU) board which is based on Armada-3720 SoC. micro-DPU is the single-port FTTdp distribution point unit made by Methode Electronics which offers complete modularity with replaceable SFP modules both for uplink and downlink (G.hn over twisted-pair, G.hn over coax, 1G and 2.5G Ethernet over Cat-5e cable). On-board features: - 512 MiB DDR3 - 2 x 2.5G SFP via HSGMII SERDES interface to the A3720 SoC - USB 2.0 Type-C connector - 4GB eMMC - ETSI TS 101548 reverse powering via twisted pair (RJ45) or coax (F Type) uDPU is intented to run on kernel 4.19 on newer due to the SFP and hardware support. Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr>
* mvebu: Fix platform.sh for non-generic espressobin versionsBrett Mastbergen2019-06-281-2/+4
| | | | | | | | When the non-generic espressobin targets were added these board checks were not updated. One side effect of this is that config is not saved during an upgrade of -emmc,-v7, or -v7-emmc devices. Signed-off-by: Brett Mastbergen <bmastbergen@untangle.com>
* kernel: generic: add missing 4.19 config symbolPetr Štetiar2019-06-271-0/+2
| | | | | | | | | | | | | | Fixes following kernel build issue on ath79 with CONFIG_KERNEL_FTRACE=y enabled: Tracers (FTRACE) [Y/n/?] y Kernel Function Tracer (FUNCTION_TRACER) [Y/n/?] y Kernel Function Graph Tracer (FUNCTION_GRAPH_TRACER) [Y/n/?] y Enable trace events for preempt and irq disable/enable (PREEMPTIRQ_EVENTS) [N/y/?] (NEW) ... Preempt / IRQ disable delay thread to test latency tracers (PREEMPTIRQ_DELAY_TEST) [N/m/?] (NEW) Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: add support for TOTOLINK A7000RChuanhong Guo2019-06-263-0/+133
| | | | | | | | | | | | | | | Specifications: - SoC: MT7621AT - RAM: 128MB - Flash: 16M SPI NOR - Ethernet: 5x GE ports - WiFi: 2.4G: MT7615N 5G: MT7615N Flash instruction: Upload generated sysupgrade firmware through factory web interface. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: mt7621: add IRQ for GPIO nodeChuanhong Guo2019-06-261-0/+3
| | | | | | This makes interrupt-based gpio-keys working. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* layerscape: drop pause frame support for aquantia phyYangbo Lu2019-06-261-52/+10
| | | | | | | | | | | | An aquantia phy patch which dropped pause frame support was missing when integrated LSDK-19.03 kernel patches into OpenWrt. Without this patch, LS1043A 10G port would not work. So apply it. Patch link https://source.codeaurora.org/external/qoriq/qoriq-components/ linux/commit/?h=linux-4.14&id=66346b115818365cfaf99d292871b19f0a1d2850 Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* kernel: bump 4.19 to 4.19.56Koen Vandeputte2019-06-254-6/+6
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.130Koen Vandeputte2019-06-257-10/+10
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* x86: fix missing led variable warning during bootPetr Štetiar2019-06-251-0/+2
| | | | | | | | Fixes following warning during the boot: WARNING: Variable 'led' does not exist or is not an array/object Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: generic: add missing 4.19 config symbolPetr Štetiar2019-06-251-0/+1
| | | | | | | | Fixes following kernel build issue on x86/64: PCI PF Stub driver (PCI_PF_STUB) [N/m/y/?] (NEW) Signed-off-by: Petr Štetiar <ynezz@true.cz>
* malta: fix overlay support by updating to f2fs/ext4 based overlaysPetr Štetiar2019-06-252-7/+10
| | | | | | | | | | | | | | | | | Current snapshot images doesn't provide images with usable overlay filesystems: mount_root: no usable overlay filesystem found, using tmpfs overlay So this patch fixes this by updating support to current f2fs/ext4 based overlays and providing squashfs with proper rootfs TARGET_ROOTFS_PARTSIZE size. While at it, I've also added support for optional gzipping of the images, and renamed the output rootfs image filenames to match the more common naming pattern $(IMG_PREFIX)-rootfs-$(FS-TYPE).img. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* malta: configure kernel for f2fs and ext4 based overlaysPetr Štetiar2019-06-251-0/+7
| | | | | | | | jffs2/mtdblock overlays are long time gone, and as we switch to the new f2fs/ext4 based overlays, we need to add missing support for loop block device and f2fs to kernel. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: fix overlay support by updating to f2fs/ext4 based overlaysPetr Štetiar2019-06-252-2/+10
| | | | | | | | | | | | | | | | | | Current snapshot images doesn't provide images with usable overlay filesystems: mount_root: no usable overlay filesystem found, using tmpfs overlay So this patch fixes this by updating support to current f2fs/ext4 based overlays and providing squashfs with proper rootfs TARGET_ROOTFS_PARTSIZE size. While at it, I've also added support for optional gzipping of the images, and renamed the output rootfs image filenames to match the more common naming pattern $(IMG_PREFIX)-rootfs-$(FS-TYPE).img. Cc: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: configure kernel for f2fs and ext4 based overlaysPetr Štetiar2019-06-251-0/+7
| | | | | | | | jffs2/mtdblock overlays are long time gone, and as we switch to the new f2fs/ext4 based overlays, we need to add missing support for loop block device and f2fs to kernel. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: image: fix small disk space in squashfs overlayPetr Štetiar2019-06-251-12/+1
| | | | | | | | | | | | | Current squashfs snapshot images are improperly padded by just 128k, which doesn't correspond with TARGET_ROOTFS_PARTSIZE=128 default config option, leading to following: Filesystem Size Used Available Use% Mounted on /dev/root 2.5M 2.5M 0 100% /rom /dev/loop0 85.0K 9.0K 71.0K 11% /overlay overlayfs:/overlay 85.0K 9.0K 71.0K 11% / Signed-off-by: Petr Štetiar <ynezz@true.cz>
* rb532,x86: image: use new IMG_COMBINED and IMG_ROOTFS varsPetr Štetiar2019-06-252-13/+13
| | | | | | | In `build: image: Add IMG_ROOTFS and IMG_COMBINED variables` we've added this new variables so switch to them now. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* tegra: image: remove image paddingPetr Štetiar2019-06-251-1/+0
| | | | | | | Commit "build: Remove TARGET_IMAGES_PAD option" has removed this config option so remove it from this target as well. Signed-off-by: Petr Štetiar <ynezz@true.cz>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-07 17:39:21 +0000