Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 161
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 17 9月, 2013 2 次提交
  3. 30 7月, 2013 1 次提交
  5. 12 5月, 2013 1 次提交
  7. 02 12月, 2012 2 次提交
  9. 20 11月, 2012 4 次提交
  11. 11 9月, 2012 1 次提交
  13. 29 8月, 2012 1 次提交
  15. 18 6月, 2012 3 次提交
  17. 20 5月, 2012 1 次提交
    • M
      mfd: Convert wm831x to irq_domain · cd99758b
      由 Mark Brown 提交于 
      The modern idiom is to use irq_domain to allocate interrupts. This is
useful partly to allow further infrastructure to be based on the domains
and partly because it makes it much easier to allocate virtual interrupts
to devices as we don't need to allocate a contiguous range of interrupt
numbers.

Convert the wm831x driver over to this infrastructure, using a legacy
IRQ mapping if an irq_base is specified in platform data and otherwise
using a linear mapping, always registering the interrupts even if they
won't ever be used. Only boards which need to use the GPIOs as
interrupts should need to use an irq_base.

This means that we can't use the MFD irq_base management since the
unless we're using an explicit irq_base from platform data we can't rely
on a linear mapping of interrupts.  Instead we need to map things via
the irq_domain - provide a conveniencem function wm831x_irq() to save a
small amount of typing when doing so. Looking at this I couldn't clearly
see anything the MFD core could do to make this nicer.

Since we're not supporting device tree yet there's no meaningful
advantage if we don't do this conversion in one, the fact that the
interrupt resources are used for repeated IP blocks makes accessor
functions for the irq_domain more trouble to do than they're worth.
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      cd99758b
  19. 14 5月, 2012 1 次提交
  21. 10 5月, 2012 1 次提交
  23. 08 5月, 2012 1 次提交
  25. 24 4月, 2012 1 次提交
  27. 17 4月, 2012 2 次提交
  29. 09 4月, 2012 1 次提交
    • M
      regulator: core: Use a struct to pass in regulator runtime configuration · c172708d
      由 Mark Brown 提交于 
      Rather than adding new arguments to regulator_register() every time we
want to add a new bit of dynamic information at runtime change the function
to take these via a struct. By doing this we avoid needing to do further
changes like the recent addition of device tree support which required each
regulator driver to be updated to take an additional parameter.

The regulator_desc which should (mostly) be static data is still passed
separately as most drivers are able to configure this statically at build
time.
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      c172708d
  31. 01 4月, 2012 1 次提交
  33. 28 3月, 2012 1 次提交
  35. 27 3月, 2012 1 次提交
  37. 20 12月, 2011 1 次提交
  39. 24 11月, 2011 1 次提交
  41. 28 7月, 2011 6 次提交
  43. 27 5月, 2011 1 次提交
  45. 26 3月, 2011 2 次提交
  47. 25 2月, 2011 1 次提交
  49. 12 1月, 2011 2 次提交