aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ramips: disable CONFIG_MTD_SPLIT_FIRMWAREMathias Kresin2019-01-265-5/+0
| | | | | | | It's no longer needed as all mt7621 devices use DT binding (supported by upstream mtd code) for specifying "firmware" part format explicitly. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: specify "firmware" partition format for remaining devicesRafał Miłecki2019-01-263-0/+3
| | | | | | | | | It results in calling the right MTD parser directly instead of trying them one by one. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> [use the lzma splitter for the AR670W] Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: Add a config for kernel v4.19Linus Walleij2019-01-261-0/+495
| | | | | | | This adds a config for kernel v4.19 to the Gemini target. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* gemini: Add v4.19 kernel patchesLinus Walleij2019-01-2618-0/+1631
| | | | | | | | | | This is the remainder of kernel patches for the v4.19 kernel. A whole slew of the previous patch stack is now upstream, so this mainly contains the stuff that was added upstream between v4.19 and v5.0-rc1, and then the USB FOTG201 patches from Hans. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* ramips: add support for Archer C50 v4David Bauer2019-01-266-1/+211
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the TP-Link Archer C50 v4. It uses the same hardware as the v3 variant, sharing the same FCC-ID. CPU: MediaTek MT7628 (580MHz) RAM: 64M DDR2 FLASH: 8M SPI WiFi: 2.4GHz 2x2 MT7628 b/g/n integrated WiFI: 5GHz 2x2 MT7612 a/n/ac ETH: 1x WAN 4x LAN LED: Power, WiFi2, WiFi5, LAN, WAN, WPS BTN: WPS/WiFi, RESET UART: Near ETH ports, 115200 8n1, TP-Link pinout Create Factory image -------------------- As all installation methods require a U-Boot to be integrated into the Image (and we do not ship one with the image) we are not able to create an image in the OpenWRT build-process. Download a TP-Link image from their Wesite and a OpenWRT sysupgrade image for the device and build yourself a factory image like following: TP-Link image: tpl.bin OpenWRT sysupgrade image: owrt.bin > dd if=tpl.bin of=boot.bin bs=131584 count=1 > cat owrt.bin >> boot.bin Installing via Web-UI --------------------- Upload the boot.bin via TP-Links firmware upgrade tool in the web-interface. Installing via Recovery ----------------------- Activate Web-Recovery by beginning the upgrade Process with a Firmware-Image from TP-Link. After starting the Firmware Upgrade, wait ~3 seconds (When update status is switching to 0%), then disconnect the power supply from the device. Upgrade flag (which activates Web-Recovery) is written before the OS-image is touched and removed after write is succesfull, so this procedure should be safe. Plug the power back in. It will come up in Recovery-Mode on 192.168.0.1. When active, all LEDs but the WPS LED are off. Remeber to assign yourself a static IP-address as DHCP is not active in this mode. The boot.bin can now be uploaded and flashed using the web-recovery. Installing via TFTP ------------------- Prepare an image like following (Filenames from factory image steps apply here) > dd if=/dev/zero of=tp_recovery.bin bs=196608 count=1 > dd if=tpl.bin of=tmp.bin bs=131584 count=1 > dd if=tmp.bin of=boot.bin bs=512 skip=1 > cat boot.bin >> tp_recovery.bin > cat owrt.bin >> tp_recovery.bin Place tp_recovery.bin in root directory of TFTP server and listen on 192.168.0.66/24. Connect router LAN ports with your computer and power up the router while pressing the reset button. The router will download the image via tftp and after ~1 Minute reboot into OpenWRT. U-Boot CLI ---------- U-Boot CLI can be activated by holding down '4' on bootup. Dual U-Boot ----------- This is the first TP-Link MediaTek device to feature a split-uboot design. The first (factory-uboot) provides recovery via TFTP and HTTP, jumping straight into the second (firmware-uboot) if no recovery needs to be performed. The firmware-uboot unpacks and executed the kernel. Web-Recovery ------------ TP-Link integrated a new Web-Recovery like the one on the Archer C7v4 / TL-WR1043v5. Stock-firmware sets a flag in the "romfile" partition before beginning to write and removes it afterwards. If the router boots with this flag set, bootloader will automatically start Web-recovery and listens on 192.168.0.1. This way, the vendor-firmware or an OpenWRT factory image can be written. By doing the same while performing sysupgrade, we can take advantage of the Web-recovery in OpenWRT. It is important to note that Web-Recovery is only based on this flag. It can't detect e.g. a crashing kernel or other means. Once activated it won't boot the OS before a recovery action (either via TFTP or HTTP) is performed. This recovery-mode is indicated by an illuminated WPS-LED on boot. Signed-off-by: David Bauer <mail@david-bauer.net>
* gemini: dlink-dir-685: fix rt2800-pci package nameChristian Lamparter2019-01-261-1/+1
| | | | | | The package is now called kmod-rt2800-pci. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: add support for Linksys EA6350v3Oever González2019-01-2610-2/+734
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: SOC: Qualcomm IPQ4018 RAM: 256 MiB Samsung K4B2G1646F-BYK0 FLASH1: MX25L1605D 2 MB FLASH2: Winbond W25N01GV 128Mb ETH: Qualcomm QCA8075 WLAN0: Qualcomm Atheros QCA4018 2.4GHz 802.11b/g/n 2x2 WLAN1: Qualcomm Atheros QCA4018 5GHz 802.11n/ac W2 2x2 INPUT: WPS, Reset LED: Status - Green SERIAL: Header at J19, Beneath DC Power Jack 1-VCC ; 2-TX ; 3-RX; 4-GND; Serial 115200-8-N-1. Tested and working: - USB (requires extra packages) - LAN Ethernet (Correct MAC-address) - WAN Ethernet (Correct MAC-address) - 2.4 GHz WiFi (Correct MAC-address) - 5 GHz WiFi (Correct MAC-address) - Factory installation from Web UI - OpenWRT sysupgrade - LED - Reset Button Need Testing: - WPS button Install via Web UI: - Attach to a LAN port on the router. - Connect to the Linksys Smart WiFi Page (default 192.168.1.1) and login - Select the connectivity tab on the left - In the manual update box on the right - Select browse, and browse to openwrt-ipq40xx-linksys_ea6350v3-squashfs-factory.bin - Click update. - Read and accept the warning - The router LED will start blinking. When the router LED goes solid, you can now navigate to 192.168.1.1 to your new OpenWrt installation. Sysupgrade: - Flash the sysupgrade image as usual. Please: try to do a reset everytime you can (doing it with LuCI is easy and can be done in the same step). Recovery (Automatic): - If the device fails to boot after install or upgrade, whilst the unit is turned on: 1 - Wait 15 seconds 2 - Switch Off and Wait 10 seconds 3 - Switch on 4 - Repeat steps 1 to 3, 3 times then go to 5. 5 - U-boot will have now erased the failed update and switched back to the last working firmware - you should be able to access your router on LAN. Recovery (Manual): - The steps for manual recovery are the same as the generic u-boot tftp client method. Back To Stock: - Use the generic recovery using the tftp client method to flash the "civic.img". Also you can strip-and-pad the original image and use the generic "mtd" method by flashing over the "kernel" partition. * Just be careful to flash in the partition that the device is currently booted. Signed-off-by: Ryan Pannell <ryan@osukl.com> Signed-off-by: Oever González <notengobattery@gmail.com> [minor edits, removed second compatible of nand, added dtb entry to 4.19] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: dts: Unify naming of gpio-led nodesPetr Štetiar2019-01-268-8/+8
| | | | | | | | | | | | | | | 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 up, removed entries where it could clash due to ath9k-leds] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-01-2613-13/+13
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* ramips: fix support for MX25L25635F flashDeng Qingfang2019-01-264-6/+80
| | | | | | | | | | | | | | | | | | | Patch picked from commit 82618062cf7e This enables 4B opcodes for MX25L25635F, to fix the reboot crash issue (FS#1120) At least 3 devices are using this flash - GeHua GHL-R-001 - Youku YK1 - Newifi D1 Now the MX25L25635F can be correctly detected without breaking MX25L25635E [ 3.034324] spi-mt7621 1e000b00.spi: sys_freq: 220000000 [ 3.045962] m25p80 spi0.0: mx25l25635f (32768 Kbytes) [ 3.056098] 4 fixed-partitions partitions found on MTD device spi0.0 [ 3.068748] Creating 4 MTD partitions on "spi0.0": Signed-off-by: Deng Qingfang <dengqf6@mail2.sysu.edu.cn> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [added deprecation notice]
* mpc85xx: add support for OCEDO PandaDavid Bauer2019-01-2611-0/+472
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CPU: FSL P1020 (2x 800MHz E500 PPC) RAM: 1GB DDR3 FLASH: 256MiB NAND WiFi: 2x Atheros AR9382 2x2:2 abgn ETH: 2x BCM54616S - 1x BCM53128 8-port switch LED: 5x LEDs (Power, WiFi1, WiFi2, N/D, SYS) BTN: 1x RESET Installation ------------ 1. Download initrams kernel image, dtb binary and sysupgrade image. 2. Place initramfs kernel into tftp root directory. Rename to "panda-uimage-factory". 3. Place dtb binary into tftp root directory. Rename to "panda.fdt". 4. Start tftp server on 192.168.100.8/24. 5. Power up the device with the reset button pressed. It will download the initrams and dtb via tftp and boot into OpenWRT in RAM. 6. SSH into the device and remove the factory partitions. > ubirmvol /dev/ubi0 --name=kernel1 > ubirmvol /dev/ubi0 --name=rootfs1 > ubirmvol /dev/ubi0 --name=devicetree1 You will have around 60 MiB of free space with that. You can also delete "kernel2", "devicetree2", "rootfs2" and "storage" respectively in case you do not want to go back to the vendor firmware. 7. Modify the U-Boot bootcmd to allow for booting OpenWRT > fw_setenv bootcmd_owrt "ubi part ubi && ubi read 0x1000000 kernel && bootm 0x1000000" > fw_setenv bootargs_owrt "setenv bootargs console=ttyS0,115200 ubi.mtd=3,2048" > fw_setenv bootcmd "run bootargs_owrt; run bootcmd_owrt" 8. Transfer the sysupgrade image via scp into the /tmp directory. 9. Upgrade the device > sysupgrade -n /tmp/<imagename> Signed-off-by: David Bauer <mail@david-bauer.net>
* mpc85xx: use generic diag.shDavid Bauer2019-01-264-46/+23
| | | | | | | | | | | | | This commit removes the target-specific diag.sh script. This way, the generic one is used for the target, which uses DT-aliases to specify the LEDs used. This way, we are also able to use different LEDs to indicate different states. We use green status LEDs for indicating boot and a running system. Where possible, the red status LED is used to indicate failsafe mode and a running upgrade. Signed-off-by: David Bauer <mail@david-bauer.net>
* ipq40xx: 4.19: fix pcie wifi unit-address of the MR33 and A62Christian Lamparter2019-01-262-2/+2
| | | | | | | | The unit address should be wifi@1,0 since the device is located at 0000:01:00.0. Reported-by: Sven Eckelmann <sven@narfation.org> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* gemini: add EOD marker to rootfs imagesMathias Kresin2019-01-261-1/+2
| | | | | | | | | With 6409b159e8b8 ("gemini: switch to 4.14") the EOF marker were dropped from the rootfs images. Without the marker the rootfs_data partition can't be created and it isn't possible to permanently store any configuration changes. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: fix ITian Square One SQ201 package selectionMathias Kresin2019-01-261-1/+1
| | | | | | | All kernel modules are prefixed with kmod-. Add the prefix to include the desired packages. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: replace date placeholderMathias Kresin2019-01-261-0/+2
| | | | | | | | | | Replace the data placerholder in ImageInfo-itian_sq201 in a reproducible way. The code for the replace was accidentality dropped in 5bac6238959 ("gemini: unify and fix ib-nas4220b and sq201 image creation") Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: drop Teltonika RUT1xx artifactsMathias Kresin2019-01-263-59/+0
| | | | | | | | Support for the Teltonika RUT1xx was added with the switch to kernel 4.4. Hidding such changes in a kernel switch commit is the wrong way and the support for the Teltonika RUT1xx is pretty much incomplete. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: add wiligear image build codeMathias Kresin2019-01-261-2/+23
| | | | | | | | | | | | | | | | | They were dropped with 6409b159e8b8 ("gemini: switch to 4.14") without any explaination. The image generation is disabled for now as it would break the build for the target. The mkfwimage2 call need to be adjusted to reflect the real size of kernel and rootfs. Nevertheless, add the required code to give interested parties a chance to fix the remaining issues. The dts would need to use the ecoscentric,redboot-fis-partitions partition parser to get the correct partition offsets and size. It's expected that the OEM firmware adjusts the on flash partition table with the values defined in the image header. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: fix alphabetical orderMathias Kresin2019-01-261-10/+10
| | | | | | Reorder the image recipes to keep the alphabetical order. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: use dts compatible based image filenamesMathias Kresin2019-01-263-15/+21
| | | | | | | | Use an output image filename based on the compatible string from the dts files. This way it is way easier to get for which board an image is intended. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: drop unnecessary image build default variablesMathias Kresin2019-01-261-3/+0
| | | | | | | They are either not required, set to an earlier set default value or defined due to target features. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: drop unnecessary imagesMathias Kresin2019-01-261-4/+1
| | | | | | | | | The root filesystem is already part of the factory image and most likely not required at all. The same applies to the kernel images. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: all images are factory imagesMathias Kresin2019-01-261-6/+6
| | | | | | | There is no support for sysupgrade in gemini, hence all images are only suitable for an installation via bootloader or oem firmware. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: follow common pattern for temp dir namingMathias Kresin2019-01-261-8/+10
| | | | | | | | For temporary directories <imagename>.tmp is a common pattern in image build code across the tree. Use it for the nas4220b/sq201 recipe as well. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: use existing build code where possibleMathias Kresin2019-01-261-2/+2
| | | | | | | Use the existing image build recipes in favour of introducing deplicate shell code. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: make all tar files more reproducibleMathias Kresin2019-01-261-3/+5
| | | | | | | Force a fixed sorting and use the parameters to create reproducible archives for all tar invocations. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: build images in temporary directoriesMathias Kresin2019-01-261-11/+13
| | | | | | | Create files in temporary directories within the build directory instead manipulating files in the (final) output directory. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: don't hardcode image filenamesMathias Kresin2019-01-261-6/+8
| | | | | | | Use the existing image build code mechanisms to specify the image output filename. Signed-off-by: Mathias Kresin <dev@kresin.me>
* gemini: fix parallel buildMathias Kresin2019-01-261-0/+1
| | | | | | | | | | | | Due to the missing PROFILES all images are build, regardless of the selected (or currently processed in case of a multi profile build). Because of the race condition builds with eight parallel jobs fail, which can be seen on the build bots as well. Add the PROFILES variable for now, till the root cause is identified. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: remove default profileTomasz Maciej Nowak2019-01-261-18/+0
| | | | | | | | | | | | | | | | | | When using Image Builder and building image for Cortex A53 or A72 subtargets, it'll fail with following message: Collected errors: * opkg_install_cmd: Cannot install package mwlwifi-firmware-88w8864. * opkg_install_cmd: Cannot install package mwlwifi-firmware-88w8964. make[2]: *** [Makefile:153: package_install] Error 255 make[1]: *** [Makefile:114: _call_image] Error 2 This is beacuse both packages are available only for Cortex A9 subtarget and are included in PACKAGES array in default profile. Instead patching this, let's remove profiles completely, since all necessary packages are specified in DEVICE_PACKAGES array for each device. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* ipq40xx: remove misplaced MR33 UCI definitionDavid Bauer2019-01-261-3/+0
| | | | | | | | | | | This removes the misplaced UCI-network configuration for the MR33. The LAN port is set in 01_leds while it is already correctly defined in 02_network. This was most likely an oversight as no network configuration belongs into 01_leds. Signed-off-by: David Bauer <mail@david-bauer.net>
* lantiq: Add support for 2nd USB port on Fritz!Box 7320 and 7330Robert Resch2019-01-261-0/+8
| | | | | | | | Enable support for 2nd USB port, which is available on Fritz!Box 7320 and 7330. It was run-tested on 7320 and 7330 as well. Signed-off-by: Robert Resch <openwrt@webnmail.de> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* lantiq: make AVM FRITZ!Box naming consistentDavid Bauer2019-01-267-12/+12
| | | | | | | | | | | | | | This commit changes the model string and device title of all AVM boards to fit the naming of the manufacturer. Drop all provider-specific titles as they are re-used for every device generation by 1&1. The original AVM model name is printed on the bottom of every devices. Exception applies for boards which are only supported by a specific sub-revision. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: adjust Netgear R6120 model nameDavid Bauer2019-01-262-2/+2
| | | | | | | Adjust the model string and device title to match other Netgear routers in the ramips target. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: fix GL.iNet AR300M family GPIOs/LEDsJeff Kletsky2019-01-261-14/+2
| | | | | | | | | | | | | | | | | Change the "status" LED to proper GPIO 12 and "red" naming. Remove GPIO 2 from definition as a USB LED. GPIO 2 is used to control power to the USB socket, not an LED. As such, PWM on the line or typical LED triggers are inappropriate. Users who wish to control the USB power for custom applications can manipulate the GPIO through code, or for example, export it through /sys/class/gpio/export. Runtime-tested:  GL.iNet AR300M-Lite Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
* kernel: fix sdhci-msm build errorJo-Philipp Wich2019-01-251-0/+23
| | | | | | | | | | | | | | | | | | | | | | A missing upstream stable backport leads to the following build error: CC drivers/mmc/host/sdhci-msm.o drivers/mmc/host/sdhci-msm.c:1158:3: error: 'const struct sdhci_ops' has no member named 'write_w' .write_w = sdhci_msm_write_w, ^~~~~~~ drivers/mmc/host/sdhci-msm.c:1158:13: warning: excess elements in struct initializer .write_w = sdhci_msm_write_w, ^~~~~~~~~~~~~~~~~ drivers/mmc/host/sdhci-msm.c:1158:13: note: (near initialization for 'sdhci_msm_ops') scripts/Makefile.build:326: recipe for target 'drivers/mmc/host/sdhci-msm.o' failed Solve the issue by backporting commit 99d570da30 ("mmc: Kconfig: Enable CONFIG_MMC_SDHCI_IO_ACCESSORS") from linux-stable. Ref: https://github.com/openwrt/openwrt/commit/528508ae8b33c76deaf18f313973144a7e920678#commitcomment-32049231 Fixes: 528508ae8b ("kernel: bump 4.14 to 4.14.95") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* gemini: unify and fix ib-nas4220b and sq201 image creationChristian Lamparter2019-01-242-34/+25
| | | | | | | | | | | | | Both Build/sq201-images and Build/nas4220b-images scripts are very similar. This patch unifies both methods at the cost of renaming the produced sysupgrade file names, but with the benifit of creating better reproducible files. The patch also fixes a race in parallel builds in which case the ImageInfo of one device could end up in both sysupgrade files. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* gemini: lazy set IMAGE_NAMEChristian Lamparter2019-01-241-1/+1
| | | | | | | | | | | Currently, IMAGE_NAME is expanded at declaration time and this causes strange filename in the builder's logs: |cp: cannot stat '[...]/openwrt-gemini-dlink-dns-313-.': No such file or directory |cp: cannot stat '[...]/openwrt-gemini-nas4220b-.': No such file or directory |[...] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* layerscape: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-01-242-2/+2
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* oxnas: dts: Unify naming of gpio-led nodesPetr Štetiar2019-01-243-3/+3
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* oxnas: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-01-243-3/+3
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* kernel: 4.19: use upstream usbport led trigger fixChristian Lamparter2019-01-242-79/+91
| | | | | | | This patch replaces the current hack with a better version of the RFC patch has been accepted upstream. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq806x: dts: Unify naming of gpio-led nodesPetr Štetiar2019-01-2410-10/+10
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* ipq806x: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-01-2410-10/+10
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* ipq40xx: dts: Unify naming of gpio-led nodesPetr Štetiar2019-01-2415-15/+15
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* ipq40xx: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-01-2415-15/+15
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* apm821xx: dts overhaulChristian Lamparter2019-01-246-26/+4
| | | | | | | | | | - remove stray #address-cells / #size-cells - fix partition unit-addresses in wd-mybooklive.dts - remove index from MBL's gpio node name Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: dts: Unify naming of gpio-led nodesPetr Štetiar2019-01-245-5/+5
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* apm821xx: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-01-245-5/+5
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* at91: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-01-242-2/+2
| | | | | | | | | | | | | | 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> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-29 12:55:33 +0000