From: Sergey Lisov <sleirsgoevy@gmail.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] *** SUBJECT HERE ***
Date: Sat, 11 Mar 2023 15:54:59 +0300 [thread overview]
Message-ID: <640c80e8.050a0220.2cfb3.0ba7@mx.google.com> (raw)
DesignWare MMC cores have a configurable data bus width of either 16, 32, or 64
bytes. It is possible, and some vendors actually do it, to ship a DW MMC core
configured for 32-bit data bus within a 64-bit SoC. In this case the kernel
will attempt 64-bit (readq) accesses to certain 64-bit MMIO registers, while
the core will expect pairs of 32-bit accesses.
It seems that currently the only register for which the kernel performs 64-bit
accesses is the FIFO. The symptom is that the DW MMC core never receives a read
on the second half of the register, does not register the datum as being read,
and thus not advancing its internal FIFO pointer, breaking further reads. It
also seems that this FIFO is only used for small (less than 16 bytes)
transfers, which probably means that only some SDIO cards are affected.
Sergey Lisov (2):
devicetree: synopsys-dw-mshc-common: add "fifo-access-32bit" property
dw_mmc: add an option to force 32-bit accesses to 64-bit device
registers
.../bindings/mmc/synopsys-dw-mshc-common.yaml | 6 +
drivers/mmc/host/dw_mmc.c | 125 +++++++++++++++++-
drivers/mmc/host/dw_mmc.h | 2 +
3 files changed, 131 insertions(+), 2 deletions(-)
--
2.38.3
next reply other threads:[~2023-03-11 13:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 12:54 Sergey Lisov [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-24 3:26 [PATCH 0/2] *** SUBJECT HERE *** Meiker Gao
2026-03-24 6:20 ` Meiker Gao (高俊)
2026-03-24 2:47 Meiker Gao
2021-04-16 8:07 Tao Zhang
2021-04-16 8:11 ` Greg Kroah-Hartman
2016-03-13 19:50 Andrew Pinski
2013-06-19 0:05 Anders Hammarquist
2013-06-19 22:53 ` Greg KH
2013-06-21 23:08 ` Anders Hammarquist
2013-06-21 23:56 ` Greg KH
2013-06-22 18:54 ` Anders Hammarquist
2013-06-25 23:39 ` Greg KH
2013-06-26 8:29 ` Anders Hammarquist
2013-06-26 10:39 ` Johan Hovold
2013-06-27 21:50 ` Anders Hammarquist
2013-06-28 10:23 ` Johan Hovold
2013-07-01 23:22 ` Anders Hammarquist
2013-07-02 9:46 ` Johan Hovold
2010-11-29 17:56 Arnaldo Carvalho de Melo
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=640c80e8.050a0220.2cfb3.0ba7@mx.google.com \
--to=sleirsgoevy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.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