linux-toradex.git/drivers/mfd/asic3.c, branch v3.11

mfd: asic3: Convert to managed resources for allocating memory

2013-06-13T10:11:41+00:00

Signed-off-by: Lee Jones 
Signed-off-by: Samuel Ortiz

mfd: remove use of __devexit

2012-11-28T20:22:27+00:00

CONFIG_HOTPLUG is going away as an option so __devexit is no
longer needed.

Signed-off-by: Bill Pemberton 
Cc: Srinidhi Kasagar 
Cc: Peter Tyser 
Cc: Daniel Walker 
Cc: Bryan Huntsman 
Acked-by: David Brown 
Acked-by: Linus Walleij 
Acked-by: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

mfd: remove use of __devexit_p

2012-11-28T20:16:42+00:00

CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
needed.

Signed-off-by: Bill Pemberton 
Cc: Srinidhi Kasagar 
Cc: Peter Tyser 
Cc: Daniel Walker 
Cc: Bryan Huntsman 
Acked-by: David Brown 
Acked-by: Linus Walleij 
Acked-by: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

mfd: core: Push irqdomain mapping out into devices

2012-09-15T21:22:04+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/asic3: fix asic3_mfd_probe return value

2012-08-08T19:13:00+00:00

In commit 4f304245b "mfd: Set asic3 DS1WM clock_rate", a possible
path through asic3_mfd_probe was introduced that would lead to
an unpredictable return value, if everything succeeds but there
are pdata->leds is NULL. This was reported correctly by gcc.

Without this patch, building magician_defconfig results in:

drivers/mfd/asic3.c: In function 'asic3_mfd_probe':
drivers/mfd/asic3.c:940:2: warning: 'ret' may be used uninitialized in this function [-Wuninitialized]

Signed-off-by: Arnd Bergmann 
Cc: Paul Parsons 
Cc: Philipp Zabel 
Cc: Samuel Ortiz

mfd: No need to check for the GPIO offset from asic3_gpio_to_irq

2012-05-01T10:00:23+00:00

The gpiolib code will only call our gpio_to_irq ops for our registered
GPIO range.

Signed-off-by: Samuel Ortiz

mfd: Avoid unbalanced asic3 irq wakeup enables/disables

2012-05-01T10:00:22+00:00

The mfd/asic3 driver does not currently define a irq_set_wake() handler.
Consequently any attempt to configure the 3 ASIC3 GPIO buttons - RECORD,
CALENDAR, HOME - as wakeup sources results in Unbalanced IRQ warnings
when the system is woken from sleep mode:

WARNING: at kernel/irq/manage.c:520 irq_set_irq_wake+0xc4/0xf8()
Unbalanced IRQ 342 wake disable
...
WARNING: at kernel/irq/manage.c:520 irq_set_irq_wake+0xc4/0xf8()
Unbalanced IRQ 337 wake disable
...
WARNING: at kernel/irq/manage.c:520 irq_set_irq_wake+0xc4/0xf8()
Unbalanced IRQ 339 wake disable
...

This patch adds a irq_set_wake() handler to the mfd/asic3 driver.

Signed-off-by: Paul Parsons 
Cc: Philipp Zabel 
Signed-off-by: Samuel Ortiz

mfd: Set asic3 DS1WM clock_rate

2012-05-01T10:00:22+00:00

The mfd/asic3 driver does not set the ds1wm_driver_data clock_rate field
before passing the structure to the DS1WM w1 busmaster driver.
This was not noticed before commit 26a6afb, because ds1wm_find_divisor()
unintentionally returned the correct divisor when a zero clock_rate was
passed in. However after that commit DS1WM fails a zero clock_rate:

ds1wm ds1wm: no suitable divisor for 0Hz clock

This patch sets the ds1wm_driver_data clock_rate field.

Signed-off-by: Paul Parsons 
Acked-by: Philipp Zabel 
Signed-off-by: Samuel Ortiz

mfd: Add PCMCIA/CF support to asic3

2012-05-01T10:00:22+00:00

This patch is part of a set which adds PCMCIA/CF support for the hx4700.
This patch adds asic3_set_register() calls to:
1. Enable the PCMCIA/CF in asic3_probe().
2. Disable the PCMCIA/CF in asic3_remove().

Signed-off-by: Paul Parsons 
Acked-by: Philipp Zabel 
Signed-off-by: Samuel Ortiz

mfd: Fix asic3_gpio_to_irq

2012-04-16T16:57:26+00:00

Assumption that irq numbers of asic3 gpios start at
IRQ_BOARD_START is certainly wrong - driver may as well
use any other base for its irqs (consider for example
the imaginary case of two ASIC3 chips onboard)

Furthermore, some platforms even don't have IRQ_BOARD_START
defined, so driver will fail to build on them:
-------------------------------------------------------
drivers/mfd/asic3.c: In function 'asic3_gpio_to_irq':
drivers/mfd/asic3.c:530: error: 'IRQ_BOARD_START' undeclared (first use in this function)
drivers/mfd/asic3.c:530: error: (Each undeclared identifier is reported only once
drivers/mfd/asic3.c:530: error: for each function it appears in.)
-------------------------------------------------------

Fix it by using irq_base from driver data.

Signed-off-by: Dmitry Artamonow 
Signed-off-by: Samuel Ortiz