1. 06 Nov, 2019 1 commit
  2. 04 Nov, 2019 7 commits
  3. 02 Nov, 2019 1 commit
  4. 01 Nov, 2019 5 commits
  5. 29 Oct, 2019 4 commits
  6. 26 Oct, 2019 2 commits
  7. 25 Oct, 2019 2 commits
  8. 23 Oct, 2019 3 commits
  9. 22 Oct, 2019 1 commit
  10. 21 Oct, 2019 4 commits
  11. 17 Oct, 2019 1 commit
  12. 14 Oct, 2019 1 commit
  13. 11 Oct, 2019 1 commit
  14. 09 Oct, 2019 3 commits
    • Tony Lindgren's avatar
      ARM: dts: Use level interrupt for omap4 & 5 wlcore · 087a2b7e
      Tony Lindgren authored
      Commit 572cf7d7 ("ARM: dts: Improve omap l4per idling with wlcore edge
      sensitive interrupt") changed wlcore interrupts to use edge interrupt based
      on what's specified in the wl1835mod.pdf data sheet.
      
      However, there are still cases where we can have lost interrupts as
      described in omap_gpio_unidle(). And using a level interrupt instead of edge
      interrupt helps as we avoid the check for untriggered GPIO interrupts in
      omap_gpio_unidle().
      
      And with commit e6818d29 ("gpio: gpio-omap: configure edge detection
      for level IRQs for idle wakeup") GPIOs idle just fine with level interrupts.
      
      Let's change omap4 and 5 wlcore users back to using level interrupt
      instead of edge interrupt. Let's not change the others as I've only seen
      this on omap4 and 5, probably because the other SoCs don't have l4per idle
      independent of the CPUs.
      
      Fixes: 572cf7d7 ("ARM: dts: Improve omap l4per idling with wlcore edge sensitive interrupt")
      Depends-on: e6818d29 ("gpio: gpio-omap: configure edge detection for level IRQs for idle wakeup")
      Cc: Anders Roxell <anders.roxell@linaro.org>
      Cc: Eyal Reizer <eyalr@ti.com>
      Cc: Guy Mishol <guym@ti.com>
      Cc: John Stultz <john.stultz@linaro.org>
      Cc: Ulf Hansson <ulf.hansson@linaro.org>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      087a2b7e
    • Krzysztof Kozlowski's avatar
      ARM: multi_v7_defconfig: Enable Exynos bus and memory frequency scaling (devfreq) · 54e48a69
      Krzysztof Kozlowski authored
      Enable devfreq events along with drivers for scaling frequency and
      voltages of Exynos buses and Dynamic Memory Controller (DMC).  This
      usually brings energy saving benefits.
      
      So far devfreq was disabled because it was causing hangs during system
      reboot (voltage not matching reset frequency). This was already fixed.
      
      Occasionally, devfreq might negatively impact performance of certain SoC
      blocks, e.g. when a bus is scaled down but some block (like Mixer with
      two Full HD windows) wants to perform high-throughput DMA operations.
      Signed-off-by: default avatarKrzysztof Kozlowski <krzk@kernel.org>
      54e48a69
    • Krzysztof Kozlowski's avatar
      ARM: multi_v7_defconfig: Enable options for boards with Exynos SoC · 00265bee
      Krzysztof Kozlowski authored
      Sync with exynos_defconfig and enable following options for Samsung
      Exynos SoC based boards:
      1. NFC_S3FWRN5_I2C (with NFC stack): Samsung S3FWRN5 NCI NFC Controller,
         used for example on Exynos5433 (if booted in 32-bit mode),
      2. S3C2410_WATCHDOG: watchdog driver used on S3C, S5P and Exynos SoCs,
      3. REGULATOR_S2MPA01: Samsung S2MPA01 regulators driver present on
         Exynos5260 RexNos REX-RED board,
      4. SND_SOC_ARNDALE: sound support on Arndale boards,
      5. EXYNOS_IOMMU: IOMMU driver used on all Exynos SocS,,
      6. EXTCON_MAX14577, EXTCON_MAX77693 and EXTCON_MAX8997: extcon drivers
         for handling micro USB on mobile Samsung boards (Trats, Trats2,
         Rinato),
      7. PHY_EXYNOS5250_SATA: SATA phy for Exynos5250 present on Arndale and
         SMDK5250 boards.
      Signed-off-by: default avatarKrzysztof Kozlowski <krzk@kernel.org>
      00265bee
  15. 08 Oct, 2019 2 commits
  16. 06 Oct, 2019 2 commits
    • Linus Torvalds's avatar
      Linux 5.4-rc2 · da0c9ea1
      Linus Torvalds authored
      da0c9ea1
    • Linus Torvalds's avatar
      elf: don't use MAP_FIXED_NOREPLACE for elf executable mappings · b212921b
      Linus Torvalds authored
      In commit 4ed28639 ("fs, elf: drop MAP_FIXED usage from elf_map") we
      changed elf to use MAP_FIXED_NOREPLACE instead of MAP_FIXED for the
      executable mappings.
      
      Then, people reported that it broke some binaries that had overlapping
      segments from the same file, and commit ad55eac7 ("elf: enforce
      MAP_FIXED on overlaying elf segments") re-instated MAP_FIXED for some
      overlaying elf segment cases.  But only some - despite the summary line
      of that commit, it only did it when it also does a temporary brk vma for
      one obvious overlapping case.
      
      Now Russell King reports another overlapping case with old 32-bit x86
      binaries, which doesn't trigger that limited case.  End result: we had
      better just drop MAP_FIXED_NOREPLACE entirely, and go back to MAP_FIXED.
      
      Yes, it's a sign of old binaries generated with old tool-chains, but we
      do pride ourselves on not breaking existing setups.
      
      This still leaves MAP_FIXED_NOREPLACE in place for the load_elf_interp()
      and the old load_elf_library() use-cases, because nobody has reported
      breakage for those. Yet.
      
      Note that in all the cases seen so far, the overlapping elf sections
      seem to be just re-mapping of the same executable with different section
      attributes.  We could possibly introduce a new MAP_FIXED_NOFILECHANGE
      flag or similar, which acts like NOREPLACE, but allows just remapping
      the same executable file using different protection flags.
      
      It's not clear that would make a huge difference to anything, but if
      people really hate that "elf remaps over previous maps" behavior, maybe
      at least a more limited form of remapping would alleviate some concerns.
      
      Alternatively, we should take a look at our elf_map() logic to see if we
      end up not mapping things properly the first time.
      
      In the meantime, this is the minimal "don't do that then" patch while
      people hopefully think about it more.
      Reported-by: default avatarRussell King <linux@armlinux.org.uk>
      Fixes: 4ed28639 ("fs, elf: drop MAP_FIXED usage from elf_map")
      Fixes: ad55eac7 ("elf: enforce  MAP_FIXED on overlaying elf segments")
      Cc: Michal Hocko <mhocko@suse.com>
      Cc: Kees Cook <keescook@chromium.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      b212921b