On 4/06/19 6:34 PM, Thierry Reding wrote:
> From: Thierry Reding <treding@xxxxxxxxxx>
>
> Recent changes have made it much more probably that clocks are not
> available yet when the SDHCI driver is first probed. However, that
> is a situation that the driver can cope with just fine.
>
> To avoid confusion, don't output an error when this happens.
>
> Signed-off-by: Thierry Reding <treding@xxxxxxxxxx>
Acked-by: Adrian Hunter <adrian.hunter@xxxxxxxxx>
> ---
> drivers/mmc/host/sdhci-tegra.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
> index 10d7aaf68bab..8a6a51bc038b 100644
> --- a/drivers/mmc/host/sdhci-tegra.c
> +++ b/drivers/mmc/host/sdhci-tegra.c
> @@ -1550,8 +1550,11 @@ static int sdhci_tegra_probe(struct platform_device *pdev)
>
> clk = devm_clk_get(mmc_dev(host->mmc), NULL);
> if (IS_ERR(clk)) {
> - dev_err(mmc_dev(host->mmc), "clk err\n");
> rc = PTR_ERR(clk);
> +
> + if (rc != -EPROBE_DEFER)
> + dev_err(&pdev->dev, "failed to get clock: %d\n", rc);
> +
> goto err_clk_get;
> }
> clk_prepare_enable(clk);
>
