From: Sergey Khimich <serghox@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mmc@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Shawn Lin <shawn.lin@rock-chips.com>,
Jyan Chou <jyanchou@realtek.com>
Subject: [PATCH v2 0/2] mmc: sdhci-of-dwcmshc: Add CQE support
Date: Tue, 26 Sep 2023 12:02:40 +0300 [thread overview]
Message-ID: <20230926090242.105020-1-serghox@gmail.com> (raw)
Hello!
This is implementation of SDHCI CQE support for sdhci-of-dwcmshc driver.
For enabling CQE support just set 'supports-cqe' in your DevTree file
for appropriate mmc node.
Also, while implementing CQE support for the driver, I faced with a problem
which I will describe below.
According to the IP block documentation CQE works only with "AMDA-2 only"
mode which is activated only with v4 mode enabled. I see in dwcmshc_probe()
function that v4 mode gets enabled only for 'sdhci_dwcmshc_bf3_pdata' platform data.
So my question is: is it correct to enable v4 mode for all platform data
if 'SDHCI_CAN_64BIT_V4' bit is set in hw?
Because I`m afraid that enabling v4 mode for some platforms could break
them down. On the other hand, if host controller says that it can do v4
(caps & SDHCI_CAN_64BIT_V4), lets do v4 or disable it manualy by some
quirk. Anyway - RFC.
v2:
- Added dwcmshc specific cqe_disable hook to prevent losing
in-flight cmd when an ioctl is issued and cqe_disable is called;
- Added processing 128Mb boundary for the host memory data buffer size
and the data buffer. For implementing this processing an extra
callback is added to the struct 'sdhci_ops'.
- Fixed typo.
Thanks in advance, Sergey.
Sergey Khimich (2):
mmc: cqhci: Add cqhci_set_tran_desc() callback
Implement SDHCI CQE support for DesignWare SDHCI.
drivers/mmc/host/Kconfig | 1 +
drivers/mmc/host/cqhci-core.c | 5 +
drivers/mmc/host/cqhci.h | 3 +
drivers/mmc/host/sdhci-of-dwcmshc.c | 233 +++++++++++++++++++++++++++-
4 files changed, 240 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2023-09-26 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 9:02 Sergey Khimich [this message]
2023-09-26 9:02 ` [PATCH v2 1/2] mmc: cqhci: Add cqhci_set_tran_desc() callback Sergey Khimich
2023-09-27 0:42 ` kernel test robot
2023-09-30 0:15 ` kernel test robot
2023-09-26 9:02 ` [PATCH v2 2/2] Implement SDHCI CQE support for DesignWare SDHCI Sergey Khimich
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=20230926090242.105020-1-serghox@gmail.com \
--to=serghox@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=jyanchou@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=shawn.lin@rock-chips.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