From: Rob Herring <robh@kernel.org>
To: Aapo Vienamo <avienamo@nvidia.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 05/10] dt-bindings: Add Tegra SDHCI pad pdpu offset bindings
Date: Mon, 30 Jul 2018 17:31:21 -0600 [thread overview]
Message-ID: <20180730233121.GA21962@rob-hp-laptop> (raw)
In-Reply-To: <1532608016-14319-6-git-send-email-avienamo@nvidia.com>
On Thu, Jul 26, 2018 at 03:26:51PM +0300, Aapo Vienamo wrote:
> Add bindings documentation for pad pull up and pull down offset values to be
> programmed before executing automatic pad drive strength calibration.
>
> Signed-off-by: Aapo Vienamo <avienamo@nvidia.com>
> ---
> .../bindings/mmc/nvidia,tegra20-sdhci.txt | 34 ++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
> index 95010cf..c3d8a15 100644
> --- a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
> +++ b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
> @@ -24,6 +24,7 @@ Required properties:
> Optional properties:
> - power-gpios : Specify GPIOs for power control
>
> +Optional properties for Tegra210 and Tegra186:
> Example:
>
> sdhci@c8000200 {
> @@ -47,6 +48,35 @@ Optional properties for Tegra210 and Tegra186:
> pinctrl-1.
> - nvidia,only-1-8-v : The presence of this property indicates that the
> controller operates at a 1.8 V fixed I/O voltage.
> +- nvidia,pad-autocal-pull-up-offset-3v3,
> + nvidia,pad-autocal-pull-down-offset-3v3 : Specify drive strength
> + calibration offsets for 3.3 V signaling modes.
Perhaps a single property with 2 values?
> +- nvidia,pad-autocal-pull-up-offset-1v8,
> + nvidia,pad-autocal-pull-down-offset-1v8 : Specify drive strength
> + calibration offsets for 1.8 V signaling modes.
> +- nvidia,pad-autocal-pull-up-offset-3v3-timeout,
> + nvidia,pad-autocal-pull-down-offset-3v3-timeout : Specify drive
> + strength used as a fallback in case the automatic calibration times
> + out on a 3.3 V signaling mode.
> +- nvidia,pad-autocal-pull-up-offset-1v8-timeout,
> + nvidia,pad-autocal-pull-down-offset-1v8-timeout : Specify drive
> + strength used as a fallback in case the automatic calibration times
> + out on a 1.8 V signaling mode.
> +- nvidia,pad-autocal-pull-up-offset-sdr104,
> + nvidia,pad-autocal-pull-down-offset-sdr104 : Specify drive strength
> + calibration offsets for SDR104 mode.
> +- nvidia,pad-autocal-pull-up-offset-hs400,
> + nvidia,pad-autocal-pull-down-offset-hs400 : Specify drive strength
> + calibration offsets for HS400 mode.
> +
> + Notes on the pad calibration pull up and pulldown offset values:
> + - The property values are drive codes which are programmed into the
> + PD_OFFSET and PU_OFFSET sections of the
> + SDHCI_TEGRA_AUTO_CAL_CONFIG register.
> + - A higher value corresponds to higher drive strength. Please refer
> + to the reference manual of the SoC for correct values.
> + - The SDR104 and HS400 timing specific values are used in
> + corresponding modes if specified.
>
> Example:
> sdhci@700b0000 {
> @@ -60,5 +90,9 @@ sdhci@700b0000 {
> pinctrl-names = "sdmmc-3v3", "sdmmc-1v8";
> pinctrl-0 = <&sdmmc1_3v3>;
> pinctrl-1 = <&sdmmc1_1v8>;
> + pad-autocal-pull-up-offset-3v3 = <0x00>;
> + pad-autocal-pull-down-offset-3v3 = <0x7d>;
> + pad-autocal-pull-up-offset-1v8 = <0x7b>;
> + pad-autocal-pull-down-offset-1v8 = <0x7b>;
Doesn't match the doc.
> status = "disabled";
> };
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-07-30 23:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 12:26 [PATCH v2 00/10] Tegra SDHCI update the pad autocal procedure Aapo Vienamo
2018-07-26 12:26 ` [PATCH v2 01/10] mmc: tegra: Poll for calibration completion Aapo Vienamo
2018-07-26 12:26 ` [PATCH v2 02/10] mmc: tegra: Set calibration pad voltage reference Aapo Vienamo
2018-07-26 12:26 ` [PATCH v2 03/10] mmc: tegra: Power on the calibration pad Aapo Vienamo
2018-07-31 9:41 ` Stefan Agner
2018-07-26 12:26 ` [PATCH v2 04/10] mmc: tegra: Disable card clock during pad calibration Aapo Vienamo
2018-07-26 12:26 ` [PATCH v2 05/10] dt-bindings: Add Tegra SDHCI pad pdpu offset bindings Aapo Vienamo
2018-07-30 23:31 ` Rob Herring [this message]
2018-07-26 12:26 ` [PATCH v2 06/10] mmc: tegra: Program pad autocal offsets from dt Aapo Vienamo
2018-07-26 12:26 ` [PATCH v2 07/10] arm64: dts: tegra186: Add sdmmc pad auto calibration offsets Aapo Vienamo
2018-07-26 12:26 ` [PATCH v2 08/10] arm64: dts: tegra210: " Aapo Vienamo
2018-07-26 12:26 ` [PATCH v2 09/10] mmc: tegra: Perform pad calibration after voltage switch Aapo Vienamo
2018-07-26 12:26 ` [PATCH v2 10/10] mmc: tegra: Enable pad calibration on Tegra210 and Tegra186 Aapo Vienamo
2018-07-30 15:07 ` [PATCH v2 00/10] Tegra SDHCI update the pad autocal procedure Ulf Hansson
2018-07-30 15:43 ` Aapo Vienamo
2018-07-31 9:33 ` Stefan Agner
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=20180730233121.GA21962@rob-hp-laptop \
--to=robh@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=avienamo@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mperttunen@nvidia.com \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox