From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] regulator: mc13783-regulator: correct the probing time.
Date: Tue, 15 Dec 2009 14:52:25 +0000 [thread overview]
Message-ID: <20091215145225.GA29034@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1260813215.2022.171.camel@climbing-alby>
On Mon, Dec 14, 2009 at 06:53:35PM +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@gmail.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alberto Panizzo <maramaopercheseimorto@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel-infradead <linux-arm-kernel@lists.infradead.org>,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Liam Girdwood" <lrg@slimlogic.co.uk>,
"Sascha linux-arm" <s.hauer@pengutronix.de>
Subject: Re: [PATCH 4/4] regulator: mc13783-regulator: correct the probing time.
Date: Tue, 15 Dec 2009 14:52:25 +0000 [thread overview]
Message-ID: <20091215145225.GA29034@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1260813215.2022.171.camel@climbing-alby>
On Mon, Dec 14, 2009 at 06:53:35PM +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@gmail.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2009-12-15 14:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 16:41 [PATCH 0/4 v2] Patch series for introduce voltage selecting for mc13783 regulators Alberto Panizzo
2009-12-14 16:41 ` Alberto Panizzo
2009-12-14 17:12 ` [PATCH 1/4] mfd: mc13783: Take care of semantic inversion between read and write value of two bits in POWER_MISCELLANEUS register Alberto Panizzo
2009-12-14 17:12 ` Alberto Panizzo
2009-12-14 17:18 ` [PATCH 2/4] mfd: mc13783: When probing, unlock the mc13783 before subsystems initialisation Alberto Panizzo
2009-12-14 17:18 ` Alberto Panizzo
2009-12-14 17:26 ` [PATCH 3/4] regulator: add voltage selection capability to mc13783 regulators v2 Alberto Panizzo
2009-12-14 17:26 ` Alberto Panizzo
2009-12-14 17:53 ` [PATCH 4/4] regulator: mc13783-regulator: correct the probing time Alberto Panizzo
2009-12-14 17:53 ` Alberto Panizzo
2009-12-15 14:50 ` Liam Girdwood
2009-12-15 14:50 ` Liam Girdwood
2009-12-15 14:52 ` Mark Brown [this message]
2009-12-15 14:52 ` Mark Brown
2009-12-15 14:54 ` [PATCH 3/4] regulator: add voltage selection capability to mc13783 regulators v2 Liam Girdwood
2009-12-15 14:54 ` Liam Girdwood
2009-12-18 16:12 ` [PATCH 2/4] mfd: mc13783: When probing, unlock the mc13783 before subsystems initialisation Alberto Panizzo
2009-12-18 16:12 ` Alberto Panizzo
2009-12-19 20:18 ` Uwe Kleine-König
2009-12-19 20:18 ` Uwe Kleine-König
2009-12-20 13:48 ` Alberto Panizzo
2009-12-20 13:48 ` Alberto Panizzo
2009-12-20 18:49 ` Uwe Kleine-König
2009-12-20 18:49 ` Uwe Kleine-König
2009-12-20 22:50 ` Alberto Panizzo
2009-12-20 22:50 ` Alberto Panizzo
2010-01-08 11:13 ` Alberto Panizzo
2010-01-08 11:13 ` Alberto Panizzo
2010-01-08 11:44 ` Samuel Ortiz
2010-01-08 11:44 ` Samuel Ortiz
2009-12-14 17:45 ` [PATCH 1/4] mfd: mc13783: Take care of semantic inversion between read and write value of two bits in POWER_MISCELLANEUS register Sergei Shtylyov
2009-12-14 17:59 ` Alberto Panizzo
2009-12-14 17:59 ` Alberto Panizzo
2010-01-05 18:15 ` Samuel Ortiz
2010-01-05 18:15 ` Samuel Ortiz
2010-01-05 19:55 ` Uwe Kleine-König
2010-01-05 19:55 ` Uwe Kleine-König
2010-01-08 10:53 ` Alberto Panizzo
2010-01-08 10:53 ` Alberto Panizzo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091215145225.GA29034@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.