1. 05 May, 2016 1 commit
  2. 01 May, 2016 1 commit
    • Marek Szyprowski's avatar
      drivers: amba: properly handle devices with power domains · 3385af8c
      Marek Szyprowski authored
      To read pid/cid registers, the probed device need to be properly turned on.
      When it is inside a power domain, the bus code should ensure that the
      given power domain is enabled before trying to access device's registers.
      However in some cases power domain (or clocks) might not be yet available.
      Returning -EPROBE_DEFER is not a solution in such case, because callers
      don't handle this special error code. Instead such devices are added to the
      special list and their registration is retried from periodic worker until
      all resources are available.
      Signed-off-by: default avatarMarek Szyprowski <m.szyprowski@samsung.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      3385af8c
  3. 24 Nov, 2015 1 commit
  4. 02 Apr, 2015 2 commits
    • Paul Walmsley's avatar
      ARM: 8334/1: amba: tegra-ahb: detect and correct bogus base address · ce7a10b0
      Paul Walmsley authored
      amba: tegra-ahb: detect and correct bogus base address
      
      From a hardware SoC integration point of view, the starting address of
      this IP block in the existing Tegra SoC DT files is off by 4 bytes
      from the actual base address.  Since we attempt to make old DT files
      forward-compatible with newer kernels, we cannot fix the IP block base
      address in old DT data. This patch works around the problem by
      detecting the four byte base address offset in the driver code, and
      correcting it if it's detected.  (In general, IP block base addresses
      almost always have a null low byte.)
      
      Future SoC DT data for Tegra AHB should use the correct Tegra AHB base
      address, in cases where there is no DT data backward compatibility
      requirement.
      
      This patch is a revision of the patch originally titled
      "amba: tegra-ahb: use correct base address for future chip support".
      This revision implements changes requested by Russell King:
      
      http://marc.info/?l=linux-tegra&m=142658851825062&w=2
      http://marc.info/?l=linux-tegra&m=142658873925178&w=2Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Paul Walmsley <pwalmsley@nvidia.com>
      Cc: Alexandre Courbot <gnurou@gmail.com>
      Cc: Hiroshi DOYU <hdoyu@nvidia.com>
      Cc: Stephen Warren <swarren@wwwdotorg.org>
      Cc: Thierry Reding <thierry.reding@gmail.com>
      Cc: linux-kernel@vger.kernel.org
      Acked-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      ce7a10b0
    • Paul Walmsley's avatar
      ARM: 8333/1: amba: tegra-ahb: fix register offsets in the macros · 049e4b3f
      Paul Walmsley authored
      amba: tegra-ahb: fix register offsets in the macros
      
      From a hardware SoC integration point of view, the offsets of the
      Tegra AHB registers that are currently defined in tegra-ahb.c macros
      are all off by four bytes.  Similarly, the starting address of this IP
      block in our existing DT files is also off by four bytes.  Since we
      attempt to make old DT files forward-compatible with newer kernels, we
      cannot fix the IP block base address in old DT data.  However, we can
      fix the offsets in the driver so that they are correct with respect to
      the hardware, which is what this patch does.  And a subsequent patch
      will allow the offset to be removed for DT 'compatible' strings used
      in future DT files for newer Tegra chips that the kernel does not yet
      support.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Paul Walmsley <pwalmsley@nvidia.com>
      Cc: Alexandre Courbot <gnurou@gmail.com>
      Cc: Hiroshi DOYU <hdoyu@nvidia.com>
      Cc: Stephen Warren <swarren@wwwdotorg.org>
      Cc: Thierry Reding <thierry.reding@gmail.com>
      Cc: linux-kernel@vger.kernel.org
      Acked-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      049e4b3f
  5. 10 Feb, 2015 1 commit
  6. 03 Dec, 2014 1 commit
  7. 26 Nov, 2014 2 commits
  8. 17 Nov, 2014 1 commit
  9. 07 Nov, 2014 1 commit
    • Pratik Patel's avatar
      coresight: add CoreSight core layer framework · a06ae860
      Pratik Patel authored
      CoreSight components are compliant with the ARM CoreSight
      architecture specification and can be connected in various
      topologies to suit a particular SoC tracing needs. These trace
      components can generally be classified as sources, links and
      sinks. Trace data produced by one or more sources flows through
      the intermediate links connecting the source to the currently
      selected sink.
      
      The CoreSight framework provides an interface for the CoreSight trace
      drivers to register themselves with. It's intended to build up a
      topological view of the CoreSight components and configure the
      correct serie of components on user input via sysfs.
      
      For eg., when enabling a source, the framework builds up a path
      consisting of all the components connecting the source to the
      currently selected sink(s) and enables all of them.
      
      The framework also supports switching between available sinks
      and provides status information to user space applications
      through the debugfs interface.
      Signed-off-by: default avatarPratik Patel <pratikp@codeaurora.org>
      Signed-off-by: default avatarMathieu Poirier <mathieu.poirier@linaro.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      a06ae860
  10. 20 Oct, 2014 1 commit
  11. 29 Sep, 2014 1 commit
  12. 22 Sep, 2014 1 commit
  13. 17 Jul, 2014 1 commit
  14. 18 Feb, 2014 1 commit
  15. 05 Feb, 2014 1 commit
  16. 09 Dec, 2013 3 commits
  17. 31 Oct, 2013 1 commit
  18. 03 Jun, 2013 1 commit
  19. 15 Mar, 2013 1 commit
  20. 21 Feb, 2013 1 commit
  21. 25 Jan, 2013 1 commit
  22. 03 Jan, 2013 1 commit
    • Greg Kroah-Hartman's avatar
      Drivers: amba: remove __dev* attributes. · c571b211
      Greg Kroah-Hartman authored
      CONFIG_HOTPLUG is going away as an option.  As a result, the __dev*
      markings need to be removed, as well as the use of CONFIG_HOTPLUG.
      
      This patch does both, removing the use of CONFIG_HOTPLUG in the
      amba/bus.c file, and __devinit and __devinitconst in the tegra-ahb.c
      driver.
      
      Cc: Bill Pemberton <wfp5p@virginia.edu>
      Cc: Russell King <linux@arm.linux.org.uk>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c571b211
  23. 03 Dec, 2012 1 commit
  24. 26 Nov, 2012 1 commit
  25. 05 Nov, 2012 1 commit
  26. 28 Jun, 2012 1 commit
  27. 11 Jun, 2012 1 commit
  28. 08 May, 2012 2 commits
  29. 03 May, 2012 1 commit
  30. 19 Apr, 2012 1 commit
  31. 13 Apr, 2012 1 commit
    • Mark Brown's avatar
      ARM: 7366/3: amba: Remove AMBA level regulator support · 1e45860f
      Mark Brown authored
      The AMBA bus regulator support is being used to model on/off switches
      for power domains which isn't terribly idiomatic for modern kernels with
      the generic power domain code and creates integration problems on platforms
      which don't use regulators for their power domains as it's hard to tell
      the difference between a regulator that is needed but failed to be provided
      and one that isn't supposed to be there (though DT does make that easier).
      
      Platforms that wish to use the regulator API to manage their power domains
      can indirect via the power domain interface.
      
      This feature is only used with the vape supply of the db8500 PRCMU
      driver which supplies the UARTs and MMC controllers, none of which have
      support for managing vcore at runtime in mainline (only pl022 SPI
      controller does).  Update that supply to have an always_on constraint
      until the power domain support for the system is updated so that it is
      enabled for these users, this is likely to have no impact on practical
      systems as probably at least one of these devices will be active and
      cause AMBA to hold the supply on anyway.
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Tested-by: default avatarShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      1e45860f
  32. 25 Jan, 2012 3 commits
  33. 21 Dec, 2011 1 commit