From: Daniel Kurtz <djkurtz@chromium.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Dylan Reid <dgreid@chromium.org>,
Jimmy Cheng-Yi Chiang <cychiang@google.com>,
Daniel Kurtz <djkurtz@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org (open list:VOLTAGE AND CURRENT
REGULATOR FRAMEWORK)
Subject: [PATCH 1/2] regulator: allow drivers in modules to register fixed regulators
Date: Tue, 17 Jul 2018 18:49:08 -0600 [thread overview]
Message-ID: <20180718004909.213735-2-djkurtz@chromium.org> (raw)
In-Reply-To: <20180718004909.213735-1-djkurtz@chromium.org>
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.
Change-Id: I2906f96df278b5fa65d40d3a777bf6d3d91841d2
Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
---
drivers/regulator/fixed-helper.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/fixed-helper.c b/drivers/regulator/fixed-helper.c
index 777fac6fb4cb0a..f53fbda043f525 100644
--- a/drivers/regulator/fixed-helper.c
+++ b/drivers/regulator/fixed-helper.c
@@ -60,3 +60,4 @@ struct platform_device *regulator_register_always_on(int id, const char *name,
return &data->pdev;
}
+EXPORT_SYMBOL_GPL(regulator_register_always_on);
--
2.18.0.203.gfac676dfb9-goog
next parent reply other threads:[~2018-07-18 0:49 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 [this message]
2018-07-18 10:42 ` Mark Brown
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=20180718004909.213735-2-djkurtz@chromium.org \
--to=djkurtz@chromium.org \
--cc=broonie@kernel.org \
--cc=cychiang@google.com \
--cc=dgreid@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®