summaryrefslogtreecommitdiff
path: root/drivers/mmc/core
diff options
context:
space:
mode:
authorPhil Edworthy <Phil.Edworthy@renesas.com>2018-03-13 17:26:40 +0300
committerUlf Hansson <ulf.hansson@linaro.org>2018-05-02 16:08:28 +0300
commit57aac3377f6a9dc9c4882c344b00e8a876cb44dd (patch)
treed06d22dbab90f517fdaf4e24de23ac0683645f07 /drivers/mmc/core
parent6da6c0db5316275015e8cc2959f12a17584aeb64 (diff)
downloadlinux-57aac3377f6a9dc9c4882c344b00e8a876cb44dd.tar.xz
mmc: sdhci-of-arasan: Add quirk to avoid unexpected interrupt msgs
On SD 2.00 cards we get lots of these messages: "mmc0: Got data interrupt 0x00000002 even though no data operation was in progress" By applying the SDHCI_QUIRK2_STOP_WITH_TC quirk, the messages no longer happen. A single card claiming to be SD 3.00 compliant also generates the interrupts, but since the card's manfacturing date is 2002 mar, it's unlikely to really be SD 3.00. This card is a 8GB SanDisk 'SU08G' 8.0 (SDHC class 4). This has been reported on Xilinx devices that also use the Arasan IP. See https://patchwork.kernel.org/patch/8062871/ This has been tested on the Renesas RZ/ND-DB board with the RZ/N1 SoC. The Arasan IP in this device is version 1.39a and uses a max SD clock of 50MHz and does not support DDR modes. Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com> Acked-by: Adrian Hunter <adrian.hunter@intel.com> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'drivers/mmc/core')
0 files changed, 0 insertions, 0 deletions