1. 18 Oct, 2018 11 commits
    • Tony Lindgren's avatar
      ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc · 87fc89ce
      Tony Lindgren authored
      With l4 interconnect hierarchy and ti-sysc interconnect target module
      data in place, we can simply move all the related child devices to
      their proper location and enable probing using ti-sysc.
      
      In general the first child device address range starts at range 0
      from the ti-sysc interconnect target so the move involves adjusting
      the child device reg properties for that.
      
      In case of any regressions, problem devices can be reverted to probe
      with legacy platform data as needed by moving them back and removing
      the related interconnect target module node.
      
      Note that we are not yet moving dss or wkup_m3, those will be moved
      later after some related driver changes.
      
      Cc: Dave Gerlach <d-gerlach@ti.com>
      Cc: Keerthy <j-keerthy@ti.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      87fc89ce
    • Tony Lindgren's avatar
      ARM: dts: am335x: Add l4 interconnect hierarchy and ti-sysc data · f711c575
      Tony Lindgren authored
      Similar to commit 8f42cb7f ("ARM: dts: omap4: Add l4 interconnect
      hierarchy and ti-sysc data"), let's add proper interconnect hierarchy
      for l4 interconnect instances with the related ti-sysc interconnect
      module data as in Documentation/devicetree/bindings/bus/ti-sysc.txt.
      
      Using ti-sysc driver binding allows us to start dropping legacy platform
      data in arch/arm/mach-omap2/omap*hwmod*data.c files later on in favor of
      ti-sysc dts data.
      
      This data is generated based on platform data from a booted system
      and the interconnect acces protection registers for ranges. To avoid
      regressions, we initially validate the device tree provided data
      against the existing platform data on boot.
      
      Note that we cannot yet include this file from the SoC dtsi file until
      the child devices are moved to their proper locations in the
      interconnect hierarchy in the following patch. Otherwise we would have
      the each module probed twice.
      
      Cc: Dave Gerlach <d-gerlach@ti.com>
      Cc: Keerthy <j-keerthy@ti.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      f711c575
    • Tony Lindgren's avatar
      ARM: dts: am437x: Move l4 child devices to probe them with ti-sysc · d95adfd4
      Tony Lindgren authored
      With l4 interconnect hierarchy and ti-sysc interconnect target module
      data in place, we can simply move all the related child devices to
      their proper location and enable probing using ti-sysc.
      
      In general the first child device address range starts at range 0
      from the ti-sysc interconnect target so the move involves adjusting
      the child device reg properties for that.
      
      In case of any regressions, problem devices can be reverted to probe
      with legacy platform data as needed by moving them back and removing
      the related interconnect target module node.
      
      Note that we are not yet moving dss or wkup_m3, those will be moved
      later after some related driver changes.
      
      Cc: Dave Gerlach <d-gerlach@ti.com>
      Cc: Keerthy <j-keerthy@ti.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      d95adfd4
    • Tony Lindgren's avatar
      ARM: dts: am437x: Add l4 interconnect hierarchy and ti-sysc data · 21c0607c
      Tony Lindgren authored
      Similar to commit 8f42cb7f ("ARM: dts: omap4: Add l4 interconnect
      hierarchy and ti-sysc data"), let's add proper interconnect hierarchy
      for l4 interconnect instances with the related ti-sysc interconnect
      module data as in Documentation/devicetree/bindings/bus/ti-sysc.txt.
      
      Using ti-sysc driver binding allows us to start dropping legacy platform
      data in arch/arm/mach-omap2/omap*hwmod*data.c files later on in favor of
      ti-sysc dts data.
      
      This data is generated based on platform data from a booted system
      and the interconnect acces protection registers for ranges. To avoid
      regressions, we initially validate the device tree provided data
      against the existing platform data on boot.
      
      Note that we cannot yet include this file from the SoC dtsi file until
      the child devices are moved to their proper locations in the
      interconnect hierarchy in the following patch. Otherwise we would have
      the each module probed twice.
      
      Cc: Dave Gerlach <d-gerlach@ti.com>
      Cc: Keerthy <j-keerthy@ti.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      21c0607c
    • Tero Kristo's avatar
      ARM: dts: dra7: convert to use new clkctrl layout · b5f8ffbb
      Tero Kristo authored
      Convert DRA7xx to use the new clockdomain based layout. Previously the
      clkctrl split was based on CM isntance boundaries. The new layout
      helps with introducing the interconnect driver instances.
      Signed-off-by: default avatarTero Kristo <t-kristo@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      b5f8ffbb
    • Tero Kristo's avatar
      ARM: dts: am43xx: convert to use new clkctrl layout · 23298c33
      Tero Kristo authored
      Convert AM43xx to use the new clockdomain based layout. Previously the
      clkctrl split was based on CM isntance boundaries. The new layout
      helps with introducing the interconnect driver instances.
      Signed-off-by: default avatarTero Kristo <t-kristo@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      23298c33
    • Tero Kristo's avatar
      ARM: dts: am33xx: convert to use new clkctrl layout · 69fd70c7
      Tero Kristo authored
      Convert AM33xx to use the new clockdomain based layout. Previously the
      clkctrl split was based on CM instance boundaries. The new layout
      helps with introducing the interconnect driver instances.
      Signed-off-by: default avatarTero Kristo <t-kristo@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      69fd70c7
    • Tony Lindgren's avatar
      Merge tag 'omap-for-v4.20/ti-sysc-take2-signed' into omap-for-v4.21/dt-ti-sysc · cdb07cce
      Tony Lindgren authored
      TI sysc driver changes for v4.20 merge window
      
      This series gets rid of the SYSC_QUIRK_RESOURCE_PROVIDER to make device
      detection happen mostly only if #define DEBUG is set. Few core devices still
      need to be detected to set legacy quirks.
      
      We also add support for booting am335x, am437x and dra7 SoCs with L4 devices
      defined in device tree instead of legacy platform data.
      
      And finally we simplify suspend with just SET_NOIRQ_SYSTEM_SLEEP_PM_OPS
      and dropping the custom functions that were attempting to work around
      issues that really turned out to be child device driver related issues.
      
      Apologies for a late pull request, debugging the suspend issues took a while
      and I did not want to send these changes until that got sorted out.
      cdb07cce
    • Tony Lindgren's avatar
    • Tony Lindgren's avatar
      a35f408e
    • Tony Lindgren's avatar
      4f1985af
  2. 03 Oct, 2018 14 commits
  3. 01 Oct, 2018 1 commit
  4. 28 Sep, 2018 10 commits
  5. 27 Sep, 2018 1 commit
  6. 24 Sep, 2018 3 commits