From: Ulf Hansson <ulf.hansson@linaro.org>
To: Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
Dmitry Osipenko <digetx@gmail.com>,
linux-tegra <linux-tegra@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] sdhci: tegra: Avoid reading autocal timeout values when not applicable
Date: Mon, 25 May 2020 10:47:47 +0200 [thread overview]
Message-ID: <CAPDyKFoV93OdjfuupYgFDegqBVjJpTnSeR3s8WOUaUmM19S4EA@mail.gmail.com> (raw)
In-Reply-To: <1590005337-1087-1-git-send-email-skomatineni@nvidia.com>
On Wed, 20 May 2020 at 22:09, Sowjanya Komatineni
<skomatineni@nvidia.com> wrote:
>
> When auto calibration timeouts, calibration is disabled and fail-safe
> drive strength values are programmed based on the signal voltage.
>
> Different fail-safe drive strength values based on voltage are
> applicable only for SoCs supporting 3V3 and 1V8 pad controls.
>
> So, this patch avoids reading these properties from the device tree
> for SoCs not using pad controls and the warning of missing properties
> will not show up on these SoC platforms.
>
> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
Applied for next and by fixing the misspelled "properies", thanks!
Kind regards
Uffe
> ---
> drivers/mmc/host/sdhci-tegra.c | 57 ++++++++++++++++++++++++------------------
> 1 file changed, 33 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
> index 3e2c510..141b49b 100644
> --- a/drivers/mmc/host/sdhci-tegra.c
> +++ b/drivers/mmc/host/sdhci-tegra.c
> @@ -605,6 +605,39 @@ static void tegra_sdhci_parse_pad_autocal_dt(struct sdhci_host *host)
> autocal->pull_down_1v8 = 0;
>
> err = device_property_read_u32(host->mmc->parent,
> + "nvidia,pad-autocal-pull-up-offset-sdr104",
> + &autocal->pull_up_sdr104);
> + if (err)
> + autocal->pull_up_sdr104 = autocal->pull_up_1v8;
> +
> + err = device_property_read_u32(host->mmc->parent,
> + "nvidia,pad-autocal-pull-down-offset-sdr104",
> + &autocal->pull_down_sdr104);
> + if (err)
> + autocal->pull_down_sdr104 = autocal->pull_down_1v8;
> +
> + err = device_property_read_u32(host->mmc->parent,
> + "nvidia,pad-autocal-pull-up-offset-hs400",
> + &autocal->pull_up_hs400);
> + if (err)
> + autocal->pull_up_hs400 = autocal->pull_up_1v8;
> +
> + err = device_property_read_u32(host->mmc->parent,
> + "nvidia,pad-autocal-pull-down-offset-hs400",
> + &autocal->pull_down_hs400);
> + if (err)
> + autocal->pull_down_hs400 = autocal->pull_down_1v8;
> +
> + /*
> + * Different fail-safe drive strength values based on the signaling
> + * voltage are applicable for SoCs supporting 3V3 and 1V8 pad controls.
> + * So, avoid reading below device tree properies for SoCs that don't
> + * have NVQUIRK_NEEDS_PAD_CONTROL.
> + */
> + if (!(tegra_host->soc_data->nvquirks & NVQUIRK_NEEDS_PAD_CONTROL))
> + return;
> +
> + err = device_property_read_u32(host->mmc->parent,
> "nvidia,pad-autocal-pull-up-offset-3v3-timeout",
> &autocal->pull_up_3v3_timeout);
> if (err) {
> @@ -647,30 +680,6 @@ static void tegra_sdhci_parse_pad_autocal_dt(struct sdhci_host *host)
> mmc_hostname(host->mmc));
> autocal->pull_down_1v8_timeout = 0;
> }
> -
> - err = device_property_read_u32(host->mmc->parent,
> - "nvidia,pad-autocal-pull-up-offset-sdr104",
> - &autocal->pull_up_sdr104);
> - if (err)
> - autocal->pull_up_sdr104 = autocal->pull_up_1v8;
> -
> - err = device_property_read_u32(host->mmc->parent,
> - "nvidia,pad-autocal-pull-down-offset-sdr104",
> - &autocal->pull_down_sdr104);
> - if (err)
> - autocal->pull_down_sdr104 = autocal->pull_down_1v8;
> -
> - err = device_property_read_u32(host->mmc->parent,
> - "nvidia,pad-autocal-pull-up-offset-hs400",
> - &autocal->pull_up_hs400);
> - if (err)
> - autocal->pull_up_hs400 = autocal->pull_up_1v8;
> -
> - err = device_property_read_u32(host->mmc->parent,
> - "nvidia,pad-autocal-pull-down-offset-hs400",
> - &autocal->pull_down_hs400);
> - if (err)
> - autocal->pull_down_hs400 = autocal->pull_down_1v8;
> }
>
> static void tegra_sdhci_request(struct mmc_host *mmc, struct mmc_request *mrq)
> --
> 2.7.4
>
prev parent reply other threads:[~2020-05-25 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 20:08 [PATCH] sdhci: tegra: Avoid reading autocal timeout values when not applicable Sowjanya Komatineni
2020-05-21 12:40 ` Dmitry Osipenko
2020-05-22 12:26 ` Thierry Reding
2020-05-22 12:42 ` Dmitry Osipenko
2020-05-22 12:52 ` Thierry Reding
2020-05-22 15:11 ` Sowjanya Komatineni
2020-05-22 12:28 ` Dmitry Osipenko
2020-05-24 15:33 ` Adrian Hunter
2020-05-25 8:47 ` Ulf Hansson [this message]
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=CAPDyKFoV93OdjfuupYgFDegqBVjJpTnSeR3s8WOUaUmM19S4EA@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=skomatineni@nvidia.com \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).