From: Wojciech Bartczak <wbartczak@marvell.com>
To: <linux-mmc@vger.kernel.org>
Cc: <ulf.hansson@linaro.org>, <beanhuo@micron.com>,
<tanxiaofei@huawei.com>, <robh+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<wbartczak@marvell.com>
Subject: [PATCH 0/2] mmc: cavium: Fix MMC supply switching for cards
Date: Wed, 17 Nov 2021 14:27:59 -0800 [thread overview]
Message-ID: <cover.1637186803.git.wbartczak@marvell.com> (raw)
Following series of patches fix code related to switching
voltage regulators used by multiple cards in Octeon/OcteonTX2
systems.
Change is necessary to support cards with different voltages,
which is common case in modern configuration where the mix of SD cards
and MMC memory chips is used as main storage.
Aside custom system, the change is required to support reference designs
for CN96xx and CN98xx systems.
First patch contains mid-size rework of do_switch() routine that
includes:
- separation of vmmc/vqmmc switch logic
- separation of register accesses to functions for better readibility
- forming do_switch() as high-level function that controls the flow of
switch operation.
Second patch adds extended description of device-tree usage to
enable code contained in former patch.
Wojciech Bartczak (2):
mmc: cavium: Fix voltage reg. switching for card slots
dt-bindings: mmc: Add vmmc/vqmmc for Cavium driver
.../devicetree/bindings/mmc/cavium-mmc.txt | 47 ++++-
drivers/mmc/host/cavium.c | 168 ++++++++++++++++--
drivers/mmc/host/cavium.h | 8 +-
3 files changed, 202 insertions(+), 21 deletions(-)
--
2.17.1
next reply other threads:[~2021-11-17 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 22:27 Wojciech Bartczak [this message]
2021-11-17 22:28 ` [PATCH 1/2] mmc: cavium: Fix voltage reg. switching for card slots Wojciech Bartczak
2021-11-19 3:50 ` kernel test robot
2021-11-17 22:28 ` [PATCH 2/2] dt-bindings: mmc: Add vmmc/vqmmc for Cavium driver Wojciech Bartczak
2021-11-23 11:51 ` 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=cover.1637186803.git.wbartczak@marvell.com \
--to=wbartczak@marvell.com \
--cc=beanhuo@micron.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tanxiaofei@huawei.com \
--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