public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Mark Brown" <broonie@kernel.org>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, "Caesar Wang" <wxt@rock-chips.com>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Stephen Barber" <smbarber@chromium.org>,
	"Douglas Anderson" <dianders@chromium.org>,
	"Brian Norris" <briannorris@chromium.org>
Subject: Re: [PATCH] regulator: reorder initialization steps in regulator_register()
Date: Thu, 14 Apr 2016 18:21:37 +0200	[thread overview]
Message-ID: <20160414182137.3257fa82@bbrezillon> (raw)
In-Reply-To: <20160413064140.GJ14664@sirena.org.uk>

Hi Thierry,

On Wed, 13 Apr 2016 07:41:40 +0100
Mark Brown <broonie@kernel.org> wrote:

> On Tue, Apr 12, 2016 at 12:31:00PM +0200, Boris Brezillon wrote:
> > device_register() is calling ->get_voltage() as part of is sysfs attribute
> > initialization process, and this functions might need to know the regulator
> > constraints to return a valid value.

I realize you were not CCed for this patch, but if we want all the
pwm-atomic support changes (including the pwm-regulator ones) to go
through your tree, you'll have to pull the following branch before
applying "regulator: pwm: retrieve correct voltage".

> 
> I've pushed this as a signed tag:
> 
> The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
> 
>   Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-sysfs-init-order
> 
> for you to fetch changes up to 469b640e4f4a28bdd50f0ac1d2b310907afb464c:
> 
>   regulator: reorder initialization steps in regulator_register() (2016-04-13 07:33:44 +0100)
> 
> ----------------------------------------------------------------
> regulator: Pull the sysfs init after constraint setup
> 
> The sysfs attributes can indirectly use information from the constraints
> so can trigger warnings with some systems.
> 
> ----------------------------------------------------------------
> Boris Brezillon (1):
>       regulator: reorder initialization steps in regulator_register()
> 
>  drivers/regulator/core.c | 20 ++++++++++----------
>  1 file changed, 10 insertions(+), 10 deletions(-)


Thanks,

Boris

-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2016-04-14 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 10:31 [PATCH] regulator: reorder initialization steps in regulator_register() Boris Brezillon
2016-04-12 10:39 ` Boris Brezillon
2016-04-12 11:02 ` Caesar Wang
2016-04-13  6:41 ` Applied "regulator: reorder initialization steps in regulator_register()" to the regulator tree Mark Brown
2016-04-13  6:41 ` [PATCH] regulator: reorder initialization steps in regulator_register() Mark Brown
2016-04-14 16:21   ` Boris Brezillon [this message]

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=20160414182137.3257fa82@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=briannorris@chromium.org \
    --cc=broonie@kernel.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smbarber@chromium.org \
    --cc=thierry.reding@gmail.com \
    --cc=wxt@rock-chips.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox