From: Mark Brown <broonie@kernel.org>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: Dylan Reid <dgreid@chromium.org>,
Jimmy Cheng-Yi Chiang <cychiang@google.com>,
Liam Girdwood <lgirdwood@gmail.com>,
"open list:VOLTAGE AND CURRENT REGULATOR FRAMEWORK"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] regulator: allow drivers in modules to register fixed regulators
Date: Wed, 18 Jul 2018 11:42:53 +0100 [thread overview]
Message-ID: <20180718104253.GB5700@sirena.org.uk> (raw)
In-Reply-To: <20180718004909.213735-2-djkurtz@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On Tue, Jul 17, 2018 at 06:49:08PM -0600, Daniel Kurtz wrote:
> Sound machine drivers tend to live in modules. Sometimes such a machine
> driver needs to register a fixed regulator to provide to a codec.
>
> Export regulator_register_always_on() such that this is possible.
Given that your driver is for a device you shouldn't be using this
function, anything you're creating should be parented off that device
and so you should be registering normally.
> Change-Id: I2906f96df278b5fa65d40d3a777bf6d3d91841d2
Please don't include noise like this in upstream submissions.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-18 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180718004909.213735-1-djkurtz@chromium.org>
2018-07-18 0:49 ` Daniel Kurtz
2018-07-18 10:42 ` Mark Brown [this message]
2018-07-18 0:49 ` [PATCH 2/2] ASoC: AMD: Add an always on fixed 1.8V regulator for da7219 VDDIO Daniel Kurtz
2018-07-18 10:46 ` 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=20180718104253.GB5700@sirena.org.uk \
--to=broonie@kernel.org \
--cc=cychiang@google.com \
--cc=dgreid@chromium.org \
--cc=djkurtz@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®