On 2016/1/19 23:33, Mason wrote:
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?
you can look into this commit 0633f654241
From <SD host controller simplified specfication version 3.00>
sdhci doesn't support blocks of 4096 bytes.
But at least check my arasan-5.1 databook, it supports 4096 from
the capabilities register. So, you don't force arasan to use
SDHCI_QUIRK_FORCE_BLK_SZ_2048, then sdhci core force it to be 512 bytes.
Not serious problem, just a proper warn.
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Best Regards
Shawn Lin
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
