Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 20 5月, 2012 2 次提交
    • 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
    • R
      mfd: Commonize tps65910 regmap access through header · 3f7e8275
      由 Rhyland Klein 提交于 
      This change removes the read/write callback functions in favor of common
regmap accessors inside the header file. This change also makes use of
regmap_read/write for single register access which maps better onto what this
driver actually needs.
Signed-off-by: NRhyland Klein <rklein@nvidia.com>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      3f7e8275
  3. 03 4月, 2012 1 次提交
    • S
      regulator: anatop: fix 'anatop_regulator' name collision · c0d78c23
      由 Shawn Guo 提交于 
      There is a name collision between 'struct platform_driver
anatop_regulator' and 'struct anatop_regulator', which causes some
section mismatch warnings like below.

WARNING: vmlinux.o(.data+0x154d4): Section mismatch in reference from the variable anatop_regulator to the function .devinit.text:anatop_regulator_probe()
The variable anatop_regulator references
the function __devinit anatop_regulator_probe()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*driver, *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

Rename 'struct platform_driver anatop_regulator' to
'struct platform_driver anatop_regulator_driver' to fix the warnings.
Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
Cc: Ying-Chun Liu (PaulLiu) <paul.liu@linaro.org>
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      c0d78c23
  5. 01 4月, 2012 1 次提交
  7. 31 3月, 2012 2 次提交
  9. 30 3月, 2012 1 次提交
  11. 29 3月, 2012 2 次提交
  13. 28 3月, 2012 5 次提交
  15. 27 3月, 2012 4 次提交
  17. 26 3月, 2012 1 次提交
  19. 17 3月, 2012 1 次提交
  21. 14 3月, 2012 12 次提交
  23. 13 3月, 2012 1 次提交
  25. 12 3月, 2012 7 次提交