[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1260888601.3591.552.camel@odin>
Date: Tue, 15 Dec 2009 14:50:01 +0000
From: Liam Girdwood <lrg@...mlogic.co.uk>
To: Alberto Panizzo <maramaopercheseimorto@...il.com>
Cc: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-arm-kernel-infradead <linux-arm-kernel@...ts.infradead.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
Sascha linux-arm <s.hauer@...gutronix.de>
Subject: Re: [PATCH 4/4] regulator: mc13783-regulator: correct the probing
time.
On Mon, 2009-12-14 at 18:53 +0100, Alberto Panizzo wrote:
> When the mc13783-regulator driver is built in kernel, probing it during
> the regulator subsystem initialisation result in a fault.
>
> That is because regulator subsystem is planned to be initialised very early
> in the boot process, before the mfd subsystem initialisation.
>
> The mc12783-regulator probing process need to access to the mc13783-core
> functionality to read/write mc13783 registers and so must be called after
> the mc13783-core driver initialisation.
>
> The way to do this is to let the kernel probe the mc13783-regulator driver when
> mc13783-core register his regulator subdevice.
>
> Signed-off-by: Alberto Panizzo <maramaopercheseimorto@...il.com>
Applied to 2.6.33
Thanks
Liam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists