[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160413064140.GJ14664@sirena.org.uk>
Date: Wed, 13 Apr 2016 07:41:40 +0100
From: Mark Brown <broonie@...nel.org>
To: Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
Caesar Wang <wxt@...k-chips.com>,
Heiko Stübner <heiko@...ech.de>,
Stephen Barber <smbarber@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
Brian Norris <briannorris@...omium.org>
Subject: Re: [PATCH] regulator: reorder initialization steps in
regulator_register()
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'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(-)
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists