[PATCH 04/15] mfd: ab8500: Register devices using the newly DT:ed MFD API
Samuel Ortiz
sameo at linux.intel.com
Fri Jun 29 14:50:47 EDT 2012
Hi Lee,
On Fri, Jun 29, 2012 at 05:04:34PM +0100, Lee Jones wrote:
> On 29/06/12 16:09, Samuel Ortiz wrote:
> >Hi Lee,
> >
> >On Wed, Jun 20, 2012 at 01:56:40PM +0100, Lee Jones wrote:
> >>Now the MFD API is Device Tree aware we can use it for platform
> >>registration again, even when booting with DT enabled. To aid in
> >>Device Node pointer allocation we provide each cell with the
> >>associative compatible string.
> >>
> >>Cc: Samuel Ortiz <sameo at linux.intel.com>
> >>Signed-off-by: Lee Jones <lee.jones at linaro.org>
> >>---
> >> arch/arm/mach-ux500/board-mop500.c | 1 -
> >> drivers/input/misc/ab8500-ponkey.c | 6 ----
> >> drivers/mfd/ab8500-core.c | 64 ++++++++++++++++++++++--------------
> >> drivers/mfd/ab8500-debugfs.c | 6 ----
> >> drivers/mfd/ab8500-gpadc.c | 6 ----
> >> drivers/mfd/ab8500-sysctrl.c | 6 ----
> >> drivers/misc/ab8500-pwm.c | 6 ----
> >> drivers/regulator/ab8500.c | 6 ----
> >> drivers/rtc/rtc-ab8500.c | 7 ----
> >> drivers/usb/otg/ab8500-usb.c | 6 ----
> >> 10 files changed, 39 insertions(+), 75 deletions(-)
> >This one does not apply properly against my for-next branch. Could you please
> >generate a new one for me ?
>
> Hmm... we have a problem.
>
> I have the new patch based on -next, but I can't test it, as -next
> is broken for Snowball. Hence why I'm still using rc2. Do you want
> it anyway?
Yes. And once Snowball is working with -next, I'll take a patch fix from you
if necessary.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
More information about the linux-arm-kernel
mailing list