Permalink
Commits on May 30, 2018
  1. ramips: Use generic board detect for GnuBee devices

    neheb authored and blogic committed May 27, 2018
    This is a port of an old commit from mkresin's tree:
    
    09260cdf3e9332978c2a474a58e93a6f2b55f4a8
    
    This has the potential to break sysupgrade but it should be fine as
    there is no stable release of LEDE or OpenWrt that support these devices.
    
    Signed-off-by: Rosen Penev <rosenp@gmail.com>
    (cherry picked from commit 9685f39)
  2. ramips: Fix WiFi after 5f7396e

    neheb authored and blogic committed May 29, 2018
    That commit exposed a bug in the DTS files used by mt7621 where the wrong
    reg value for pcie1 (and potentially pcie2) was being used. This was
    causing WiFi failures for interfaces in pcie1.
    
    eg. 2.4GHz working but not 5GHz.
    
    As all of these dts entries are already specified in mt7621.dtsi, remove
    them.
    
    Signed-off-by: Rosen Penev <rosenp@gmail.com>
    (cherry picked from commit 02f815d)
Commits on May 24, 2018
  1. target/linux: drop anything not on v4.9 or v4.14

    blogic committed May 24, 2018
    Signed-off-by: John Crispin <john@phrozen.org>
  2. ath79: drop, its not ready for a release yet

    blogic committed May 24, 2018
    Signed-off-by: John Crispin <john@phrozen.org>
  3. ramips: Fix up GnuBee PC1 DTS file a little

    neheb authored and blogic committed May 24, 2018
    There's nothing connected to i2c on this board, so remove it.
    
    Also edited the gpio group to match the PC2 as they're the same.
    
    Signed-off-by: Rosen Penev <rosenp@gmail.com>
    (cherry picked from commit 8c818fa)
  4. brcm47xx: add switch port mapping to Asus WL-500W

    mparthey authored and blogic committed May 22, 2018
    Switch ports 0..3 are connected to external ports LAN{1..4} in sequence,
    switch port 4 is not used, and switch port 5 is connected to the CPU.
    The WAN port is attached to the CPU's second network interface; it has no
    connection to the internal switch.
    
    Reuse the "Dell TrueMobile 2300" entry, which describes the same mapping.
    
    Signed-off-by: Mirko Parthey <mirko.parthey@web.de>
    (cherry picked from commit 7ac238f)
  5. ipq806x: drop "mtd: nand: add Winbond manufacturer and chip"

    pkgadd authored and blogic committed May 18, 2018
    The W25N01GV NAND is currently not used in any ipq806x device.
    
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    (cherry picked from commit a436ef9)
  6. ipq806x: drop linux 4.9 support

    pkgadd authored and blogic committed May 18, 2018
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    (cherry picked from commit 2819732)
  7. ipq806x: switch to linux 4.14

    pkgadd authored and blogic committed May 18, 2018
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    (cherry picked from commit 18e9ed2)
  8. ipq806x: remove spi-nor from r7800 dts

    dissent1 authored and blogic committed Jan 18, 2018
    There's no spi-nor in R7800, so disable unequipped interfaces.
    
    Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit 8c1c1c4)
  9. ipq806x: remove rpm pinctrl from board dts

    dissent1 authored and blogic committed Jan 18, 2018
    These pins seem to be used by hw exclusively, so claiming it in
    kernel causes an error in syslog in k4.14+.
    
    Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit 96cd316)
  10. ipq806x: fix EA8500 switch control

    dissent1 authored and blogic committed Jan 18, 2018
    EA8500 has pcie2 slot unequipped.
    By EA8500 hw design default pcie2 reset gpio (gpio63) is used to
    reset the switch. That's why enabling pcie2 brings the switch into
    a working state.
    
    So let's just control the gpio63 without enabling the pcie2 slot.
    
    We have to remove the pcie2_pins node so the gpio63 is not defined
    twice. Because pcie2 node has a reference to pcie2_pins we have to
    remove it as well.
    
    Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit 7f694ef)
  11. ipq806x: move mmc specific nodes into v1.0 dtsi

    dissent1 authored and blogic committed Jan 18, 2018
    These nodes are common for all revisions so put it into SoC v1.0
    dtsi file.
    
    Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit 7a4f9c5)
  12. ipq806x: fix pcie tx termination offset

    dissent1 authored and blogic committed Jan 18, 2018
    According to GPL tarballs and QSDK related branch tx termination
    offset for ipq8064 SoC version >= 2.0 should be equal to 0 and
    not 7.
    
    https://github.com/paul-chambers/netgear-r7800/blob/master/git_home/linux.git/sourcecode/arch/arm/mach-msm/board-ipq806x.c#L1682-L1685
    
    Fix this.
    
    Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit fbedc22)
  13. ipq806x: apply updated USB PHY settings to v2.0 SoC

    dissent1 authored and blogic committed Jan 18, 2018
    USB PHY power settings introduced for ipq8065 SoC with commit
    644a0d5 "ipq8065: adjust SS USB PHY power settings"
    
    According to that commit msg and in correspondence to GPL tarballs
    and related QSDK branch those settings are applied to ipq8064
    SoCs of version >= 2.0.
    
    https://github.com/paul-chambers/netgear-r7800/blob/master/git_home/linux.git/sourcecode/arch/arm/mach-msm/board-ipq806x.c#L2507-L2514
    
    Now as we have clarified that mass market boards are of SoC v2.0
    move those USB PHY settings from ipq8065 (v3.0 SoC) dtsi to
    ipq8064 v2.0 dtsi.
    
    Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit d4b98c3)
  14. ipq806x: reference ipq8065 as ipq8064 v3.0

    dissent1 authored and blogic committed Jan 18, 2018
    ipq8065 is ipq8064 v3.0
    > socinfo_init: v6, id=280, ver=3.0, raw_id=17, raw_ver=17, hw_plat=0,  hw_plat_ver=65536
    
    Include dtsi accordingly and remove the unneeded qcom-ipq8065-v1.0.dtsi
    
    Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit e16f9ab)
  15. ipq806x: move mass market ipq8064 to v2 dtsi

    dissent1 authored and blogic committed Jan 18, 2018
    According to OEM bootlog entry mass market devices are ipq8064 SoC
    v2.0:
    > socinfo_init: v6, id=202, ver=2.0, raw_id=2064, raw_ver=2064, hw_plat=0,  hw_plat_ver=65536
    
    I've checked C2600, EA8500 and VR2600v but couldn't find other
    boards bootlog. I think it's safe to assume that other boards are
    also v2.0. R7500 may be an exception because it was the first
    device to hit the market.
    
    So switch to v2.0 dtsi.
    
    Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit 067036e)
  16. ipq806x: introduce ipq8064 SoC v2 dtsi

    dissent1 authored and blogic committed Jan 18, 2018
    According to QCA internal numbering there are 3 versions of
    ipq8064/5 SoC:
    ipq8064 v1.0 - probably ipq8064 evaluation boards only
    ipq8064 v2.0 - probably ipq8064 mass market boards only
    ipq8064 v3.0 - aka ipq8065, boards based on ipq8065.
    
    Each next revision includes configuration differences from
    previous revision and adds something new.
    
    Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit adbdf78)
  17. kernel: iqp806x low latency kernel does not boot

    Marc Benoit authored and blogic committed Apr 4, 2018
    It keeps failing (R7800) with the stack trace below
    
    BUG: scheduling while atomic: kworker/0:1/26/0x00000002
    
    (unwind_backtrace) from [<c02121d0>] (show_stack+0x10/0x14)
    (show_stack) from [<c03932e4>] (dump_stack+0x7c/0x9c)
    (dump_stack) from [<c0239b90>] (__schedule_bug+0x5c/0x80)
    (__schedule_bug) from [<c05b7260>] (__schedule+0x50/0x3f4)
    (__schedule) from [<c05b76a8>] (schedule+0xa4/0xd4)
    (schedule) from [<c05ba430>] (schedule_hrtimeout_range_clock+0xc8/0x100)
    (schedule_hrtimeout_range_clock) from [<c05ba480>]
           (schedule_hrtimeout_range+0x18/0x20)
    (schedule_hrtimeout_range) from [<c05b9f78>] (usleep_range+0x48/0x50)
    (usleep_range) from [<c03f333c>] (__clk_hfpll_enable+0x44/0xd0)
    (__clk_hfpll_enable) from [<c03f3474>] (clk_hfpll_set_rate+0xac/0xc4)
    (clk_hfpll_set_rate) from [<c03ec390>] (clk_change_rate+0xf4/0x1fc)
    (clk_change_rate) from [<c03ec510>] (clk_core_set_rate_nolock+0x78/0x94)
    (clk_core_set_rate_nolock) from [<c03ec54c>] (clk_set_rate+0x20/0x30)
    (clk_set_rate) from [<c0424168>] (dev_pm_opp_set_rate+0x190/0x26c)
    (dev_pm_opp_set_rate) from [<c04a8548>] (set_target+0x40/0x108)
    (set_target) from [<c04a4.140>] (__cpufreq_driver_target+0x3f4/0x488)
    (__cpufreq_driver_target) from [<c04a7494>] (od_dbs_timer+0xcc/0x154)
    (od_dbs_timer) from [<c04a7998>] (dbs_work_handler+0x2c/0x54)
    (dbs_work_handler) from [<c02309e8>] (process_one_work+0x1c0/0x2f0)
    (process_one_work) from [<c02319a8>] (worker_thread+0x2a4/0x404)
    (worker_thread) from [<c0235944>] (kthread+0xd8/0xe8)
    (kthread) from [<c020eef0>] (ret_from_fork+0x14/0x24)
    
    Signed-off-by: Marc Benoit <marcb62185@gmail.com>
    [slh: rebase for kernel v4.14 as well]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit e40db29)
  18. ipq806x: define KERNEL_SIZE in KB instead of byte for the image gener…

    pkgadd authored and blogic committed May 18, 2018
    …ation
    
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    (cherry picked from commit 05f53ee)
  19. ipq806x: increase kernel partition size for the Netgear Nighthawk X4 …

    pkgadd authored and blogic committed May 18, 2018
    …R7500v2
    
    Starting with kernel 4.14 and gcc 7, the kernel doesn't fit into the
    2 MB reserved for the kernel partition by the OEM firmware anymore.
    
    This patch increases the kernel partition from 2 MB to 4 MB, at the
    expense of the rootfs, for all supported kernels.
    
    WARNING: This breaks sysupgrade! Flashing a firmware containing this
    changed partitioning from an older image with 2 MB reserved for the
    kernel partion requires the tftp recovery procedure, thereby losing
    all settings.
    
    This change follows the functional example of the Netgear r7800, but
    has not been runtime tested on a Netgear Nighthawk X4 R7500v2.
    
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    (cherry picked from commit c3af761)
  20. ipq806x: increase kernel partition size for the Netgear Nighthawk X4 …

    pkgadd authored and blogic committed May 18, 2018
    …R7500
    
    Starting with kernel 4.14 and gcc 7, the kernel doesn't fit into the
    2 MB reserved for the kernel partition by the OEM firmware anymore.
    
    This patch increases the kernel partition from 2 MB to 4 MB, at the
    expense of the rootfs, for all supported kernels.
    
    WARNING: This breaks sysupgrade! Flashing a firmware containing this
    changed partitioning from an older image with 2 MB reserved for the
    kernel partion requires the tftp recovery procedure, thereby losing
    all settings.
    
    This change follows the functional example of the Netgear r7800, but
    has not been runtime tested on a Netgear Nighthawk X4 R7500
    
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    Cc: Jonas Gorski <jonas.gorski@gmail.com>
    (cherry picked from commit c228bbe)
  21. ipq806x: increase kernel partition size for the Netgear Nighthawk X4 …

    pkgadd authored and blogic committed May 18, 2018
    …D7800
    
    Starting with kernel 4.14 and gcc 7, the kernel doesn't fit into the
    2 MB reserved for the kernel partition by the OEM firmware anymore.
    
    This patch increases the kernel partition from 2 MB to 4 MB, at the
    expense of the rootfs, for all supported kernels.
    
    WARNING: This breaks sysupgrade! Flashing a firmware containing this
    changed partitioning from an older image with 2 MB reserved for the
    kernel partion requires the tftp recovery procedure, thereby losing
    all settings.
    
    This change follows the functional example of the Netgear r7800, but
    has not been runtime tested on a Netgear Nighthawk X4 D7800.
    
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    Cc: Tathagata Das <tathagata@alumnux.com>
    (cherry picked from commit 45b8a7c)
  22. ipq806x: increase kernel partition size for the TP-Link Archer VR2600v

    pkgadd authored and blogic committed May 18, 2018
    The default image does not fit 2 MB anymore, expand kernel partition
    to 3 MB.
    
    Upgrading should work transparently via sysupgrade in both directions.
    Another option would be to merge "kernel" and "rootfs" into a single
    "firmware" partition using MTD_SPLIT_TPLINK_FW, but just changing the
    sizes of the existing partitioning has been deemed safer in the absence
    of an actual runtime test on an affected device; the maximum for rootfs
    changes from 10.4 MB to 9.4 MB.
    
    This change follows the example for the TP-Link Archer C2600, but has
    not been runtime tested on a TP-Link Archer VR2600v.
    
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    Cc: Sebastian Quilitz <zeraphim@x-pantion.de>
    (cherry picked from commit 0c967d9)
  23. ipq806x: increase kernel partition size for the TP-Link Archer C2600

    pkgadd authored and blogic committed May 18, 2018
    The default image does not fit 2 MB anymore, expand os-image partition
    to 4 MB.
    
    Upgrading works transparently via sysupgrade in both directions.
    Another option would have been to merge "os-image" and "rootfs" into a
    single "firmware" partition using MTD_SPLIT_TPLINK_FW, but just
    changing the sizes of the existing partitioning has been deemed safer
    and actually tested on an affected device; the maximum for rootfs
    changes from 27 MB to 25 MB.
    
    Run-tested on TP-Link Archer C2600.
    
    Signed-off-by: Joris de Vries <joris@apptrician.nl>
    [slh: extend comments and commit message, rename rootfs]
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    
    (cherry picked from commit b72b366)
  24. ipq806x: increase kernel partition size for the Netgear r7800

    pkgadd authored and blogic committed May 18, 2018
    Starting with kernel 4.14 and gcc 7, the kernel doesn't fit into the
    2 MB reserved for the kernel partition by the OEM firmware anymore.
    
    This patch increases the kernel partition from 2 MB to 4 MB, at the
    expense of the rootfs, for all supported kernels.
    
    WARNING: This breaks sysupgrade! Flashing a firmware containing this
    changed partitioning from an older image with 2 MB reserved for the
    kernel partion requires the tftp recovery procedure, thereby losing
    all settings.
    
    This patch is based on a corresponding change by Pavel Kubelun
    <be.dissent@gmail.com> and has been tested by Michael Yartys
    <michael.yartys@protonmail.com>
    
    Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    (cherry picked from commit dc50694)
  25. ipq806x: cleanup kernel config

    Ram Chandra Jangir authored and blogic committed May 17, 2018
    Disable MSM8960, MSM8974 and APQ8084
     - since these are different SoC's than IPQ806x
    Removed unrequired serial configs
     - since ipq806x uses SERIAL_MSM only
    
    Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
    Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    (cherry picked from commit 7ac6697)
  26. ipq806x: add kernel 4.14 support

    Ram Chandra Jangir authored and blogic committed May 4, 2018
     - Rebased the patches for 4.14
     - Dropped spi-qup and 0027, 0028, 0029
       clk patches since it's already included
       in upstream.
    
     Tested on IPQ AP148 Board:
      1) NOR boot and NAND boot
      2) Tested USB and PCIe interfaces
      3) WDOG test
      4) cpu frequency scaling
      5) ethernet, 2G and 5G WiFi
      6) ubi sysupgrade
    
    Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
    Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
    (cherry picked from commit 93dd2f7)
  27. ipq40xx: add eva-image for FRITZ!Box 4040

    blocktrron authored and blogic committed May 15, 2018
    This commit adds an EVA flashable image for the FRITZ!Box 4040.
    
    The image contains the U-Boot with OpenWRT appended to it. This way we
    remove the need to use UART for initial flashing.
    
    Signed-off-by: David Bauer <mail@david-bauer.net>
    (cherry picked from commit 70e6ea3)
  28. build: add apend-uboot command

    blocktrron authored and blogic committed May 15, 2018
    This commit adds an append-uboot command to append U-Boot from the
    bin-directory.
    
    Signed-off-by: David Bauer <mail@david-bauer.net>
    (cherry picked from commit 399495a)
  29. ramips: change wifi led trigger for Archer C50v3

    blocktrron authored and blogic committed May 18, 2018
    This commit alters the TP-Link Archer C50v3 LED settings to use the phy
    trigger instead of the netdev one. This way the WiFi status is displayed
    even if the wifi interface name is altered.
    
    Signed-off-by: David Bauer <mail@david-bauer.net>
    (cherry picked from commit ce91c85)
  30. ramips: fix Archer C50v3 LED mapping

    blocktrron authored and blogic committed May 18, 2018
    This commit fixes the wrong LED mapping of the Archer C50 v3.
    Commit was tested with an EU device.
    
    Signed-off-by: David Bauer <mail@david-bauer.net>
    (cherry picked from commit 35d00d9)
  31. ar71xx: Add support for PISEN TS-D084

    981213 authored and blogic committed Apr 22, 2018
    PISEN TS-D084 is an wireless router with a battery and integrated power supply based on Atheros AR9331.
    
    Specification:
    
    - 400/400/200 MHz (CPU/DDR/AHB)
    - 64 MB of RAM (DDR2)
    - 8 MB of FLASH (SPI NOR)
    - 1x 10/100 Mbps Ethernet
    - 1T1R 2.4 GHz (AR9331)
    - 1x USB 2.0
    
    Flash instruction:
    The manufacturer are using exactly the same firmware header as TP-LINK TL-WR703N (including device ID!). Simply upload the factory firmware into WebUI and flashing is done.
    
    Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
    (cherry picked from commit a789c0f)
  32. kernel: enable THIN_ARCHIVES by default

    rsa9000 authored and blogic committed May 21, 2018
    THIN_ARCHIVES option is enabled by default in the kernel configuration
    and no one target config disables it. So enable it by default and remove
    this symbol from target specific configs to keep them light.
    
    Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
    (cherry picked from commit 67a3cdc)
  33. kernel: enable FUTEX_PI by default

    rsa9000 authored and blogic committed May 21, 2018
    New FUTEX_PI configuration symbol enabled if FUTEX and RT_MUTEX symbols
    are enabled. Both of these symbols are enabled by default in the
    generic config, so enable FUTEX_PI by default too to keep platform
    specific configs minimal.
    
    Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
    (cherry picked from commit bdc2b58)