1. 03 Sep, 2019 3 commits
  2. 25 Aug, 2019 4 commits
  3. 24 Aug, 2019 1 commit
    • André Draszik's avatar
      ARM: imx: stop adjusting ar8031 phy tx delay · acf993a0
      André Draszik authored
      Recent changes to the Atheros at803x driver cause
      the approach taken here to stop working because
      commit 6d4cd041
      ("net: phy: at803x: disable delay only for RGMII mode")
      and commit cd28d1d6
      ("net: phy: at803x: Disable phy delay for RGMII mode")
      fix the AR8031 driver to configure the phy's (RX/TX)
      delays as per the 'phy-mode' in the device tree.
      
      In particular, the phy tx (and rx) delays are updated
      again as per the 'phy-mode' *after* the code in here
      runs.
      
      Things worked before above commits, because the AR8031
      comes out of reset with RX delay enabled, and the
      at803x driver didn't touch the delay configuration at
      all when "rgmii" mode was selected.
      
      It appears the code in here tries to make device
      trees work that incorrectly specify "rgmii", but
      that can't work any more and it is imperative since
      above commits to have the phy-mode configured
      correctly in the device tree.
      
      I suspect there are a few imx7d based boards using
      the ar8031 phy and phy-mode = "rgmii", but given I
      don't know which ones exactly, I am not in a
      position to update the respective device trees.
      
      Hence this patch is simply removing the superfluous
      code from the imx7d initialisation. An alternative
      could be to add a warning instead, but that would
      penalize all boards that have been updated already.
      Signed-off-by: default avatarAndré Draszik <git@andred.net>
      CC: Russell King <linux@armlinux.org.uk>
      CC: Shawn Guo <shawnguo@kernel.org>
      CC: Sascha Hauer <s.hauer@pengutronix.de>
      CC: Pengutronix Kernel Team <kernel@pengutronix.de>
      CC: Fabio Estevam <festevam@gmail.com>
      CC: NXP Linux Team <linux-imx@nxp.com>
      CC: Kate Stewart <kstewart@linuxfoundation.org>
      CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      CC: Thomas Gleixner <tglx@linutronix.de>
      CC: Leonard Crestez <leonard.crestez@nxp.com>
      CC: linux-arm-kernel@lists.infradead.org
      Signed-off-by: default avatarShawn Guo <shawnguo@kernel.org>
      acf993a0
  4. 15 Aug, 2019 14 commits
  5. 14 Aug, 2019 12 commits
  6. 13 Aug, 2019 1 commit
  7. 11 Aug, 2019 3 commits
  8. 10 Aug, 2019 2 commits
    • Linus Torvalds's avatar
      Merge tag 'riscv/for-v5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux · 296d05cb
      Linus Torvalds authored
      Pull RISC-V updates from Paul Walmsley:
       "A few minor RISC-V updates for v5.3-rc4:
      
         - Remove __udivdi3() from the 32-bit Linux port, converting the only
           upstream user to use do_div(), per Linux policy
      
         - Convert the RISC-V standard clocksource away from per-cpu data
           structures, since only one is used by Linux, even on a multi-CPU
           system
      
         - A set of DT binding updates that remove an obsolete text binding in
           favor of a YAML binding, fix a bogus compatible string in the
           schema (thus fixing a "make dtbs_check" warning), and clarifies the
           future values expected in one of the RISC-V CPU properties"
      
      * tag 'riscv/for-v5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:
        dt-bindings: riscv: fix the schema compatible string for the HiFive Unleashed board
        dt-bindings: riscv: remove obsolete cpus.txt
        RISC-V: Remove udivdi3
        riscv: delay: use do_div() instead of __udivdi3()
        dt-bindings: Update the riscv,isa string description
        RISC-V: Remove per cpu clocksource
      296d05cb
    • Linus Torvalds's avatar
      Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · 6d8f809c
      Linus Torvalds authored
      Pull x86 fixes from Thomas Gleixner:
       "A few fixes for x86:
      
         - Don't reset the carefully adjusted build flags for the purgatory
           and remove the unwanted flags instead. The 'reset all' approach led
           to build fails under certain circumstances.
      
         - Unbreak CLANG build of the purgatory by avoiding the builtin
           memcpy/memset implementations.
      
         - Address missing prototype warnings by including the proper header
      
         - Fix yet more fall-through issues"
      
      * 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        x86/lib/cpu: Address missing prototypes warning
        x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS
        x86/purgatory: Do not use __builtin_memcpy and __builtin_memset
        x86: mtrr: cyrix: Mark expected switch fall-through
        x86/ptrace: Mark expected switch fall-through
      6d8f809c