From: Heiner Kallweit <hkallweit1@gmail.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/2] mmc: add and use helpers mmc_regulator_enable/disable_vqmmc
Date: Sat, 11 Mar 2023 23:38:08 +0100 [thread overview]
Message-ID: <9ae6f90e-e1ea-d088-cdae-7dd8a541f00f@gmail.com> (raw)
There's a number of drivers (e.g. dw_mmc, meson-gx, mmci, sunxi) using
the same mechanism and a private flag vqmmc_enabled to deal with
enabling/disabling the vqmmc regulator.
Move this to the core and create new helpers mmc_regulator_enable_vqmmc
and mmc_regulator_disable_vqmmc. Make meson-gx the first user of the
new helpers.
Heiner Kallweit (2):
mmc: core: add helpers mmc_regulator_enable/disable_vqmmc
mmc: meson-gx: use new helpers mmc_regulator_enable/disable_vqmmc
drivers/mmc/core/regulator.c | 41 +++++++++++++++++++++++++++++++++
drivers/mmc/host/meson-gx-mmc.c | 18 ++-------------
include/linux/mmc/host.h | 3 +++
3 files changed, 46 insertions(+), 16 deletions(-)
--
2.39.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-03-11 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 22:38 Heiner Kallweit [this message]
2023-03-11 22:39 ` [PATCH 1/2] mmc: core: add helpers mmc_regulator_enable/disable_vqmmc Heiner Kallweit
2023-03-12 20:28 ` Martin Blumenstingl
2023-03-11 22:41 ` [PATCH 2/2] mmc: meson-gx: use new " Heiner Kallweit
2023-03-12 20:28 ` Martin Blumenstingl
2023-03-23 12:12 ` [PATCH 0/2] mmc: add and use " Ulf Hansson
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=9ae6f90e-e1ea-d088-cdae-7dd8a541f00f@gmail.com \
--to=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).