From: Mark Brown <broonie@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linaro-kernel@lists.linaro.org,
Jean Delvare <khali@linux-fr.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] ACPI: Flag use of ACPI and ACPI idioms for power supplies to regulator API
Date: Mon, 27 Jan 2014 00:44:34 +0000 [thread overview]
Message-ID: <20140127004434.GT11727@sirena.org.uk> (raw)
In-Reply-To: <2348079.FWLATJ4QDO@vostro.rjw.lan>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
On Mon, Jan 27, 2014 at 01:54:49AM +0100, Rafael J. Wysocki wrote:
> On Monday, January 27, 2014 12:32:14 AM Mark Brown wrote:
> > @@ -509,6 +510,14 @@ void __init acpi_early_init(void)
> > goto error0;
> > }
> >
> > + /*
> > + * If the system is using ACPI then we can be reasonably
> > + * confident that any regulators are managed by the firmware
> > + * so tell the regulator core it has everything it needs to
> > + * know.
> > + */
> > + regulator_has_full_constraints();
> > +
> That's going to be called earlier than it use to be in 3.13 and before.
> No problems with that?
All that function does is to set a flag - so long as we can assign to a
static variable it should be OK.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-27 0:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 0:32 [PATCH] ACPI: Flag use of ACPI and ACPI idioms for power supplies to regulator API Mark Brown
2014-01-27 0:54 ` Rafael J. Wysocki
2014-01-27 0:44 ` Mark Brown [this message]
2014-01-27 12:54 ` Rafael J. Wysocki
2014-01-27 13:21 ` Mark Brown
2014-01-28 0:06 ` Rafael J. Wysocki
2014-01-28 12:21 ` Mark Brown
2014-01-28 21:55 ` Rafael J. Wysocki
2014-01-27 8:25 ` Jean Delvare
2014-01-27 10:43 ` Mark Brown
2014-01-27 14:58 ` Guenter Roeck
2014-01-27 16:25 ` Mark Brown
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=20140127004434.GT11727@sirena.org.uk \
--to=broonie@kernel.org \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rjw@rjwysocki.net \
/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