linux-toradex.git/drivers/mfd/max8925-core.c, branch v3.7

mfd: max8925: Remove array in regulator platform data

2012-09-19T10:39:13+00:00

Remove array in parent's platform data. Use struct regulator_init_data
as regulator device's platform data directly. So a lot of pdata are
added into parent's platform data. And voltage out register offset
is used as IORESOURCE_REG to distinguish different regualtor devices.

Signed-off-by: Haojian Zhuang 
Signed-off-by: Samuel Ortiz

mfd: max8925: Use register offset as REG in backlight

2012-09-19T10:39:13+00:00

Remove the register offset definition. All these register offset
are transfered as IORESOURCE_REG resources.

Signed-off-by: Haojian Zhuang 
Signed-off-by: Samuel Ortiz

mfd: Use IRQF_ONESHOT for max8925

2012-09-19T10:13:44+00:00

Generated by: scripts/coccinelle/misc/irqf_oneshot.cocci

Make sure threaded IRQs without a primary handler are always request
with IRQF_ONESHOT.

Signed-off-by: Fengguang Wu 
Signed-off-by: Samuel Ortiz

mfd: core: Push irqdomain mapping out into devices

2012-09-14T07:51:54+00:00

Currently the MFD core supports remapping MFD cell interrupts using an
irqdomain but only if the MFD is being instantiated using device tree
and only if the device tree bindings use the pattern of registering IPs
in the device tree with compatible properties.  This will be actively
harmful for drivers which support non-DT platforms and use this pattern
for their DT bindings as it will mean that the core will silently change
remapping behaviour and it is also limiting for drivers which don't do
DT with this particular pattern.  There is also a potential fragility if
there are interrupts not associated with MFD cells and all the cells are
omitted from the device tree for some reason.

Instead change the code to take an IRQ domain as an optional argument,
allowing drivers to take the decision about the parent domain for their
interrupts.  The one current user of this feature is ab8500-core, it has
the domain lookup pushed out into the driver.

Signed-off-by: Mark Brown 
Signed-off-by: Samuel Ortiz

mfd: max8925: Convert to IORESOURCE_REG

2012-09-11T08:15:03+00:00

Signed-off-by: Mark Brown 
Acked-by: Arnd Bergmann 
Acked-by: Haojian Zhuang 
Tested-by: Haojian Zhuang 
Signed-off-by: Samuel Ortiz

mfd: max8925: Move _IO resources out of ioport_ioresource

2012-09-11T08:15:02+00:00

The removal of mach/io.h from most ARM platforms also set the range of
valid IO ports to be empty for most platforms when previously any 32
bit integer had been valid. This makes it impossible to add IO resources
as the added range is smaller than that of the root resource for IO ports.

Since we're not really using IO memory at all fix this by defining our
own root resource outside the normal tree and make that the parent of
all IO resources. This also ensures we won't conflict with read IO ports
if we ever run on a platform which happens to use them.

Signed-off-by: Mark Brown 
Acked-by: Haojian Zhuang 
Tested-by: Haojian Zhuang 
Cc: stable@vger.kernel.org (v3.4+)
Signed-off-by: Samuel Ortiz

mfd: Transfer rtc max8925 irq from MFD defined resources

2012-07-08T22:16:10+00:00

MAX8925 rtc irq is transfered from mfd resources now.

Signed-off-by: Haojian Zhuang 
Signed-off-by: Samuel Ortiz

max8925_power: Remove support for irq bits that do not exist

2011-11-25T19:24:45+00:00

The max8925 cannot return usb status.  The bits

       [MAX8925_IRQ_VCHG_USB_OVP] = {
               .reg            = MAX8925_CHG_IRQ1,
               .mask_reg       = MAX8925_CHG_IRQ1_MASK,
               .offs           = 1 << 3,
       },
       [MAX8925_IRQ_VCHG_USB_F] =  {
               .reg            = MAX8925_CHG_IRQ1,
               .mask_reg       = MAX8925_CHG_IRQ1_MASK,
               .offs           = 1 << 4,
       },
       [MAX8925_IRQ_VCHG_USB_R] = {
               .reg            = MAX8925_CHG_IRQ1,
               .mask_reg       = MAX8925_CHG_IRQ1_MASK,
               .offs           = 1 << 5,
       },

do not exist in the irq register.

Signed-off-by: Philip Rakity 
Signed-off-by: Anton Vorontsov

mfd: Remove checking on max8925 regulator[0]

2011-05-26T17:45:37+00:00

Since regulator[0] is always checking in mfd driver, it results in
registration failure without regulator[0].

Signed-off-by: Haojian Zhuang 
Reviewed-by: Mark Brown 
Signed-off-by: Samuel Ortiz

mfd: Cleanup irq namespace

2011-03-26T23:09:51+00:00

Converted with coccinelle.

Signed-off-by: Thomas Gleixner 
Acked-by: Mark Brown 
Signed-off-by: Samuel Ortiz