1. 26 4月, 2018 5 次提交
  2. 19 10月, 2017 1 次提交
    • R
      drivers: flag buses which demand DMA configuration · d89e2378
      Robin Murphy 提交于
      We do not want the common dma_configure() pathway to apply
      indiscriminately to all devices, since there are plenty of buses which
      do not have DMA capability, and if their child devices were used for
      DMA API calls it would only be indicative of a driver bug. However,
      there are a number of buses for which DMA is implicitly expected even
      when not described by firmware - those we whitelist with an automatic
      opt-in to dma_configure(), assuming that the DMA address space and the
      physical address space are equivalent if not otherwise specified.
      
      Commit 72328883 ("of: restrict DMA configuration") introduced a
      short-term fix by comparing explicit bus types, but this approach is far
      from pretty, doesn't scale well, and fails to cope at all with bus
      drivers which may be built as modules, like host1x. Let's refine things
      by making that opt-in a property of the bus type, which neatly addresses
      those problems and lets the decision of whether firmware description of
      DMA capability should be optional or mandatory stay internal to the bus
      drivers themselves.
      Signed-off-by: NRobin Murphy <robin.murphy@arm.com>
      Acked-by: NRob Herring <robh@kernel.org>
      Acked-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Acked-by: NThierry Reding <treding@nvidia.com>
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      d89e2378
  3. 09 6月, 2017 1 次提交
  4. 12 8月, 2016 1 次提交
  5. 06 5月, 2016 1 次提交
  6. 02 5月, 2016 1 次提交
  7. 10 2月, 2015 1 次提交
  8. 04 12月, 2014 1 次提交
  9. 18 11月, 2014 1 次提交
  10. 08 11月, 2014 1 次提交
    • P
      coresight: add CoreSight core layer framework · a06ae860
      Pratik Patel 提交于
      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: NPratik Patel <pratikp@codeaurora.org>
      Signed-off-by: NMathieu Poirier <mathieu.poirier@linaro.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      a06ae860
  11. 30 9月, 2014 1 次提交
  12. 22 9月, 2014 1 次提交
  13. 19 2月, 2014 1 次提交
  14. 10 12月, 2013 3 次提交
  15. 31 10月, 2013 1 次提交
  16. 04 6月, 2013 1 次提交
  17. 04 1月, 2013 1 次提交
    • G
      Drivers: amba: remove __dev* attributes. · c571b211
      Greg Kroah-Hartman 提交于
      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: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c571b211
  18. 03 12月, 2012 1 次提交
  19. 29 6月, 2012 1 次提交
  20. 03 5月, 2012 1 次提交
  21. 20 4月, 2012 1 次提交
  22. 13 4月, 2012 1 次提交
    • M
      ARM: 7366/3: amba: Remove AMBA level regulator support · 1e45860f
      Mark Brown 提交于
      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: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Tested-by: NShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      1e45860f
  23. 25 1月, 2012 3 次提交
  24. 22 12月, 2011 1 次提交
  25. 22 11月, 2011 1 次提交
    • D
      ARM: amba: Auto-generate AMBA driver module aliases during modpost · 523817bd
      Dave Martin 提交于
      This patch adds the necessary support in file2alias.c to define
      suitable aliases based on the amba_id table in AMBA driver modules.
      
      This should be sufficient to allow such modules to be auto-loaded
      via udev.  The AMBA bus driver's uevent hotplug code is also
      modified to pass an approriate MODALIAS string in the event.
      
      For simplicity, the AMBA ID is treated an an opaque 32-bit numeber.
      Module alises use patterns as appropriate to describe the value-
      mask pairs described in the driver's amba_id list.
      
      The proposed alias format is (extended regex):
      
          ^amba:d(HEX){8}$
      
      Where HEX is a single upper-case HEX digit or a pattern (? or []
      expression) matching a single upper-case HEX digit, as expected by
      udev.
      
      "d" is short for "device", following existing alias naming
      conventions for other device types.  This adds some flexibility for
      unambiguously extending the alias format in the future by adding
      additional leading and trailing fields, if this turns out to be
      necessary.
      Signed-off-by: NDave Martin <dave.martin@linaro.org>
      Acked-by: NPawel Moll <pawel.moll@arm.com>
      523817bd
  26. 27 9月, 2011 1 次提交
  27. 22 9月, 2011 1 次提交
  28. 26 5月, 2011 1 次提交
  29. 12 4月, 2011 1 次提交
    • R
      PM / Hibernate: Introduce CONFIG_HIBERNATE_CALLBACKS · 1f112cee
      Rafael J. Wysocki 提交于
      Xen save/restore is going to use hibernate device callbacks for
      quiescing devices and putting them back to normal operations and it
      would need to select CONFIG_HIBERNATION for this purpose.  However,
      that also would cause the hibernate interfaces for user space to be
      enabled, which might confuse user space, because the Xen kernels
      don't support hibernation.  Moreover, it would be wasteful, as it
      would make the Xen kernels include a substantial amount of code that
      they would never use.
      
      To address this issue introduce new power management Kconfig option
      CONFIG_HIBERNATE_CALLBACKS, such that it will only select the code
      that is necessary for the hibernate device callbacks to work and make
      CONFIG_HIBERNATION select it.  Then, Xen save/restore will be able to
      select CONFIG_HIBERNATE_CALLBACKS without dragging the entire
      hibernate code along with it.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Tested-by: NShriram Rajagopalan <rshriram@cs.ubc.ca>
      1f112cee
  30. 31 3月, 2011 1 次提交
  31. 24 2月, 2011 2 次提交