1. 25 Apr, 2016 1 commit
  2. 23 Apr, 2016 2 commits
  3. 22 Apr, 2016 4 commits
    • Kevin Hilman's avatar
      Merge tag 'imx-fixes-4.6' of... · e6d939bf
      Kevin Hilman authored
      Merge tag 'imx-fixes-4.6' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into fixes
      
      Merge "ARM: i.MX fixes for 4.6" from Shawn Guo:
      
      The i.MX fixes for 4.6:
       - The sdhci-esdhc-imx DMA support is broken due to commit 7b91369b
         ("mmc: sdhci: Set DMA mask when adding host").  It requires device's
         dma_mask be set up properly to get DMA work.  The fixing patch
         initializes the DMA mask to enable the access again.
      
      * tag 'imx-fixes-4.6' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux:
        ARM: mach-imx: sdhci-esdhc-imx: initialize DMA mask
      e6d939bf
    • Kevin Hilman's avatar
      Merge tag 'omap-for-v4.6/fixes-rc3' of... · 22c49e5a
      Kevin Hilman authored
      Merge tag 'omap-for-v4.6/fixes-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
      
      Merge "omap fixes for v4.6-rc cycle" from Tony Lindgren:
      
      Fixes for omaps for v4.6-rc cycle:
      
      - Clockdomain fix for dra7 timer interrupts
      
      - Two fixes for GPMC EDMA binding, I missed the need for a merge with
        GPMC changes and EDMA changes
      
      - Fix beagle-x15 eSATA by dropping misconfigured extcon_usb1
      
      - Fix occasional external aborts on 36xx with PM that we've been
        chasing for past few months. It turned out to be duplicate restore
        of INTC registers that can in some cases cause us to hit erratum 1.106.
      
      * tag 'omap-for-v4.6/fixes-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
        ARM: OMAP3: Fix external abort on 36xx waking from off mode idle
        ARM: dts: am57xx-beagle-x15: remove extcon_usb1
        ARM: dts: am437x: Fix GPMC dma properties
        ARM: dts: am33xx: Fix GPMC dma properties
        ARM: DRA7: clockdomain: Implement timer workaround for errata i874
      22c49e5a
    • Kevin Hilman's avatar
      Merge tag 'renesas-fixes-for-v4.6' of... · c95e2e7e
      Kevin Hilman authored
      Merge tag 'renesas-fixes-for-v4.6' of git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas into fixes
      
      Merge "Renesas ARM Based SoC Fixes for v4.6" from Simon Horman:
      
      Renesas ARM Based SoC Fixes for v4.6
      
      * Correct preset_lpj calculation which may lead to too short delays
      * Correct handling of optional clocks on r8a7791 to restore
        access to the serial port the porter board
      
      * tag 'renesas-fixes-for-v4.6' of git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas:
        ARM: shmobile: timer: Fix preset_lpj leading to too short delays
        Revert "ARM: dts: porter: Enable SCIF_CLK frequency and pins"
        ARM: dts: r8a7791: Don't disable referenced optional clocks
      c95e2e7e
    • Kevin Hilman's avatar
      Merge tag 'omap-for-v4.6/fixes-rc2-v2-signed' of... · c0e30913
      Kevin Hilman authored
      Merge tag 'omap-for-v4.6/fixes-rc2-v2-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
      
      Merge "omap fixes against v4.6-rc2" from Tony Lindgren
      
      Fixes for omaps against v4.6-rc2, mostly to fix suspend for beagle-x15
      that broke when we added runtime based SoC revision detection earlier.
      
      It seems suspend worked earlier as things were only partially initialized,
      while now we initialize things properly for dra7.
      
      Note that the "ARM: OMAP: Catch callers of revision information prior
      to it being populated" had to be reverted as it caused bogus warnings
      for other SoCs because omap initcalls bail out based on revision being
      set to 0 for other SoCs. These initcalls will mostly just disappear
      when we drop support for omap3 legacy booting.
      
      Also included is a fix for dra7 sys_32k_ck clock source that is not
      enabled on boot making system fall back to using emulated clock.
      
      * tag 'omap-for-v4.6/fixes-rc2-v2-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap: (198 commits)
        Revert "ARM: OMAP: Catch callers of revision information prior to it being populated"
        ARM: OMAP: Catch callers of revision information prior to it being populated
        ARM: dts: dra7: Correct clock tree for sys_32k_ck
        ARM: OMAP: DRA7: Provide proper class to omap2_set_globals_tap
        ARM: OMAP: DRA7: wakeupgen: Skip SAR save for wakeupgen
        Linux 4.6-rc2
        v4l2-mc: avoid warning about unused variable
        Convert straggling drivers to new six-argument get_user_pages()
        .mailmap: add Christophe Ricard
        Make CONFIG_FHANDLE default y
        mm/page_isolation.c: fix the function comments
        oom, oom_reaper: do not enqueue task if it is on the oom_reaper_list head
        mm/page_isolation: fix tracepoint to mirror check function behavior
        mm/rmap: batched invalidations should use existing api
        x86/mm: TLB_REMOTE_SEND_IPI should count pages
        mm: fix invalid node in alloc_migrate_target()
        include/linux/huge_mm.h: return NULL instead of false for pmd_trans_huge_lock()
        mm, kasan: fix compilation for CONFIG_SLAB
        MAINTAINERS: orangefs mailing list is subscribers-only
        net: mvneta: fix changing MTU when using per-cpu processing
        ...
      c0e30913
  4. 19 Apr, 2016 4 commits
  5. 14 Apr, 2016 2 commits
    • Kevin Hilman's avatar
      Merge tag 'v4.6-soc-fixes' of https://github.com/mbgg/linux-mediatek into fixes · 2193a3fd
      Kevin Hilman authored
      - fix boot error reverting commit cc8ed769
      ("soc: mediatek: SCPSYS: Fix double enabling of regulators")
      
      * tag 'v4.6-soc-fixes' of https://github.com/mbgg/linux-mediatek:
        Revert "soc: mediatek: SCPSYS: Fix double enabling of regulators"
      2193a3fd
    • Dave Gerlach's avatar
      ARM: OMAP3: Fix external abort on 36xx waking from off mode idle · 1560d158
      Dave Gerlach authored
      Depending on timing during the resume path from off mode on 36xx, we may
      see external aborts. These seem to be caused by the following:
      
      - OMAP3 Advisory 1.62 "MPU Cannot Exit from Standby" says we need to
        disable intc autoidle before WFI
      
      - DM3730 Advisory 1.106 "MPU Leaves MSTANDBY State Before IDLEREQ of
        Interrupt Controller is Released" says we need to wait before
        accessing intc
      
      omap3_intc_resume_idle restores the intc autoidle for all resume paths,
      however in the resume path from off mode only it is also being restored
      by omap_intc_restore_context before this call to omap3_intc_resume_idle
      happens. The second restore of the intc autoidle in this path is what
      appears to be causing the external abort so for the off mode resume path
      let's rely on omap_intc_restore_context to restore intc autoidle, and
      for all other paths let omap3_intc_resume_idle handle it as it is now.
      Signed-off-by: default avatarDave Gerlach <d-gerlach@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      1560d158
  6. 13 Apr, 2016 6 commits
  7. 12 Apr, 2016 6 commits
  8. 10 Apr, 2016 1 commit
    • Keerthy's avatar
      ARM: DRA7: clockdomain: Implement timer workaround for errata i874 · 1cbabcb9
      Keerthy authored
      Errata Title:
      i874: TIMER5/6/7/8 interrupts not propagated
      
      Description:
      When TIMER5, TIMER6, TIMER7, or TIMER8 clocks are enabled
      (CM_IPU_TIMER5/6/7/8_CLKCTRL[0:1]MODULEMODE=0x2:ENABLE) and the CD-IPU
      is in HW_AUTO mode (CM_IPU_CLKSTCTRL[0:1]CLKTRCTRL=0x3:HW_AUTO) the
      corresponding TIMER will continue counting, but enabled interrupts
      will not be propagated to the destinations (MPU, DSP, etc) in the
      SoC until the TIMER registers are accessed from the CPUs (MPU, DSP
      etc.). This can result in missed timer interrupts.
      
      Workaround:
      In order for TIMER5/6/7/8 interrupts to be propagated and serviced
      correctly the CD_IPU domain should be set to SW_WKUP mode
      (CM_IPU_CLKSTCTRL[0:1]CLKTRCTRL=0x2:SW_WKUP).
      
      The above workaround is achieved by switching the IPU clockdomain
      flags from HWSUP_SWSUP to SWSUP only.
      Signed-off-by: default avatarKeerthy <j-keerthy@ti.com>
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      1cbabcb9
  9. 08 Apr, 2016 6 commits
    • Kevin Hilman's avatar
      Merge tag 'meson8-dt-fix' of https://github.com/carlocaione/linux-meson into fixes · 309fdeb5
      Kevin Hilman authored
      With http://www.spinics.net/lists/devicetree/msg116771.html we split / refactor
      the pinctrl driver to have two different pinctrl devices for each bus on the
      Amlogic Meson8 / Meson8b SoCs.
      These are the missing patches for documentation and DT that weren't pulled into
      mainline with the driver changes.
      
      * tag 'meson8-dt-fix' of https://github.com/carlocaione/linux-meson:
        documentation: Fix pinctrl documentation for Meson8 / Meson8b
        ARM: dts: amlogic: Split pinctrl device for Meson8 / Meson8b
      309fdeb5
    • Tony Lindgren's avatar
      19e831b2
    • Nishanth Menon's avatar
      ARM: OMAP: Catch callers of revision information prior to it being populated · 571afb4c
      Nishanth Menon authored
      omap_rev is used to detect various SoC types, however any misuse of
      the usage by invoking it earlier than it being populated will result
      in invalid results. Lets flag them as early as possible to prevent
      unintended side effects taking place. We get 0 if it is uninitialized
      and -1 when detection is done using device tree (as the case was for
      DRA7 as the case was prior to commit 06c2d368 ("ARM: OMAP: DRA7:
      Make use of omap_revision information for soc_is* calls")
      Signed-off-by: default avatarNishanth Menon <nm@ti.com>
      Tested-by: default avatarKeerthy <j-keerthy@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      571afb4c
    • Keerthy's avatar
      ARM: dts: dra7: Correct clock tree for sys_32k_ck · eea08802
      Keerthy authored
      This is w.r.t J6/J6eco: 32clk is pseudo (erratum i856) - clock source.
      Errata i856 for the AM572x (DRA7xx) points out that the 32.768KHz external
      crystal is not enabled at power up. Instead the CPU falls back to using
      an emulation for the 32KHz clock which is SYSCLK1/610.  SYSCLK1 is usually
      20MHz on boards so far (which gives an emulated frequency of 32.786KHz)
      
      Modelling the same in device tree.
      Acked-by: default avatarTero Kristo <t-kristo@ti.com>
      Signed-off-by: default avatarKeerthy <j-keerthy@ti.com>
      Signed-off-by: default avatarLokesh Vutla <lokeshvutla@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      eea08802
    • Nishanth Menon's avatar
      ARM: OMAP: DRA7: Provide proper class to omap2_set_globals_tap · ec490f6f
      Nishanth Menon authored
      When commit 06c2d368 ("ARM: OMAP: DRA7: Make use of omap_revision
      information for soc_is* calls") introduced SoC check using
      omap_revision, it missed providing DRA7 as class for initializing
      the omap_version variable. Without doing this, soc_is_dra7xx() will
      fail and as a result, omap4_pm_init_early never initializes the dra7
      erratum for CPU power state. This causes the suspend path to fail
      on DRA7 devices.
      
      Fixes: 06c2d368 ("ARM: OMAP: DRA7: Make use of omap_revision information for soc_is* calls")
      Signed-off-by: default avatarNishanth Menon <nm@ti.com>
      Tested-by: default avatarKeerthy <j-keerthy@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      ec490f6f
    • Nishanth Menon's avatar
      ARM: OMAP: DRA7: wakeupgen: Skip SAR save for wakeupgen · c783e6fd
      Nishanth Menon authored
      DRA7 has no SAR region for automated save and restore of wakeupgen,
      which does not make real since the SoC really does not do legacy OFF
      mode anymore. Further wakeupgen should never loose context in CSWR
      retention mode for MPU domain on DRA7 since that is the deepest state
      we will enter.
      
      So, just skip, instead of oopsing as follows while attemptint to enter
      suspend on BeagleBoard-X15.
      [   55.589771] Unable to handle kernel paging request at virtual address 00002684
      [   55.589771] pgd = ec69c000
      [...]
      [   55.589771] [<c0123cc8>] (irq_notifier) from [<c015ad70>] (notifier_call_chain+0x4c/0x8c)
      [   55.589771] [<c015ad70>] (notifier_call_chain) from [<c021469c>] (cpu_cluster_pm_enter+0x2c/0x78)
      [   55.589771] [<c021469c>] (cpu_cluster_pm_enter) from [<c0514508>] (syscore_suspend+0xb8/0x31c)
      [   55.589771] [<c0514508>] (syscore_suspend) from [<c0197d24>] (suspend_devices_and_enter+0x308/0x9e4)
      [   55.589771] [<c0197d24>] (suspend_devices_and_enter) from [<c0198a40>] (pm_suspend+0x640/0x75c)
      [   55.589771] [<c0198a40>] (pm_suspend) from [<c0196bcc>] (state_store+0x64/0xb8)
      [   55.589771] [<c0196bcc>] (state_store) from [<c0307914>] (kernfs_fop_write+0xc0/0x1bc)
      [   55.589771] [<c0307914>] (kernfs_fop_write) from [<c028ac80>] (__vfs_write+0x1c/0xd8)
      [   55.589771] [<c028ac80>] (__vfs_write) from [<c028bb70>] (vfs_write+0x90/0x16c)
      [   55.589771] [<c028bb70>] (vfs_write) from [<c028c890>] (SyS_write+0x44/0x9c)
      [   55.589771] [<c028c890>] (SyS_write) from [<c0107840>] (ret_fast_syscall+0x0/0x1c)
      [...]
      Signed-off-by: default avatarNishanth Menon <nm@ti.com>
      Tested-by: default avatarKeerthy <j-keerthy@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      c783e6fd
  10. 03 Apr, 2016 7 commits
  11. 02 Apr, 2016 1 commit