From: Mason <slash.tmp@free.fr>
To: linux-mmc <linux-mmc@vger.kernel.org>
Cc: Michal Simek <michal.simek@xilinx.com>,
Soren Brinkmann <soren.brinkmann@xilinx.com>,
Suman Tripathi <stripathi@apm.com>, Arnd Bergmann <arnd@arndb.de>,
Ulf Hansson <ulf.hansson@linaro.org>,
Sebastian Frias <sf84@laposte.net>
Subject: mmc0: Invalid maximum block size, assuming 512 bytes
Date: Tue, 19 Jan 2016 16:33:46 +0100 [thread overview]
Message-ID: <569E575A.5070401@free.fr> (raw)
Hello,
My SoC provides an Arasan SDIO/eMMC controller supported by the
drivers/mmc/host/sdhci-of-arasan.c driver.
At init, the driver prints a warning to the console:
[ 0.887301] sdhci: Secure Digital Host Controller Interface driver
[ 0.893537] sdhci: Copyright(c) Pierre Ossman
[ 0.897928] sdhci-pltfm: SDHCI platform and OF driver helper
[ 0.903903] sdhci-arasan 21000.mmc: No vmmc regulator found
[ 0.909537] sdhci-arasan 21000.mmc: No vqmmc regulator found
[ 0.915247] mmc0: Invalid maximum block size, assuming 512 bytes
[ 0.953797] mmc0: SDHCI controller on 21000.mmc [21000.mmc] using ADMA
[ 0.961494] sdhci-arasan 21200.mmc: No vmmc regulator found
[ 0.967110] sdhci-arasan 21200.mmc: No vqmmc regulator found
Is "mmc0: Invalid maximum block size, assuming 512 bytes" something
serious which requires investigating, in your experience?
The corresponding DT is:
mmc0: mmc@21000 {
compatible = "arasan,sdhci-8.9a";
reg = <0x21000 0x200>;
clock-names = "clk_xin", "clk_ahb";
clocks = <&sdio_clk>, <&clkgen 1>;
interrupts = <60 IRQ_TYPE_LEVEL_HIGH>;
};
Regards.
next reply other threads:[~2016-01-19 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 15:33 Mason [this message]
2016-01-20 1:17 ` mmc0: Invalid maximum block size, assuming 512 bytes Shawn Lin
2016-01-21 15:00 ` Mason
2016-01-22 2:07 ` Shawn Lin
2016-01-22 7:17 ` Mason
2016-02-01 21:32 ` Mason
2016-02-02 8:58 ` Adrian Hunter
2016-02-02 10:12 ` Mason
2016-02-02 11:30 ` Adrian Hunter
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=569E575A.5070401@free.fr \
--to=slash.tmp@free.fr \
--cc=arnd@arndb.de \
--cc=linux-mmc@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=sf84@laposte.net \
--cc=soren.brinkmann@xilinx.com \
--cc=stripathi@apm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.