From: Ludovic Barre <ludovic.Barre@st.com>
To: Ulf Hansson <ulf.hansson@linaro.org>, Rob Herring <robh+dt@kernel.org>
Cc: <srinivas.kandagatla@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-mmc@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Ludovic Barre <ludovic.barre@st.com>
Subject: [PATCH 0/5] mmc: mmci: add get_datactrl_cfg callback
Date: Mon, 4 Mar 2019 11:17:00 +0100 [thread overview]
Message-ID: <1551694625-6414-1-git-send-email-ludovic.Barre@st.com> (raw)
From: Ludovic Barre <ludovic.barre@st.com>
This patch series adds get_datactrl_cfg callback in mmci_host_ops
to allow to get datactrl configuration specific at variant.
Ludovic Barre (5):
mmc: mmci: add get_datactrl_cfg callback
mmc: mmci: define get_dctrl_cfg for legacy variant
mmc: mmci: qcom: define get_dctrl_cfg
mmc: mmci: stm32: define get_dctrl_cfg
mmc: mmci: replace blksz_datactrlXX by get_datactrl_cfg callback
drivers/mmc/host/mmci.c | 51 ++++++++++++++++++++++++-------------
drivers/mmc/host/mmci.h | 11 ++++----
drivers/mmc/host/mmci_qcom_dml.c | 8 ++++++
drivers/mmc/host/mmci_stm32_sdmmc.c | 21 +++++++++++++++
4 files changed, 68 insertions(+), 23 deletions(-)
--
2.7.4
next reply other threads:[~2019-03-04 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 10:17 Ludovic Barre [this message]
2019-03-04 10:17 ` [PATCH 1/5] " Ludovic Barre
2019-03-04 10:17 ` [PATCH 2/5] mmc: mmci: define get_dctrl_cfg for legacy variant Ludovic Barre
2019-03-04 10:17 ` [PATCH 3/5] mmc: mmci: qcom: define get_dctrl_cfg Ludovic Barre
2019-03-06 13:31 ` Ulf Hansson
2019-03-04 10:17 ` [PATCH 4/5] mmc: mmci: stm32: " Ludovic Barre
2019-03-06 13:31 ` Ulf Hansson
2019-03-06 17:01 ` Ludovic BARRE
2019-03-04 10:17 ` [PATCH 5/5] mmc: mmci: replace blksz_datactrlXX by get_datactrl_cfg callback Ludovic Barre
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=1551694625-6414-1-git-send-email-ludovic.Barre@st.com \
--to=ludovic.barre@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@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
all inboxes | Powered by JetHome®