All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: Aapo Vienamo <avienamo@nvidia.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh+dt@kernel.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,
	linux-tegra-owner@vger.kernel.org
Subject: Re: [PATCH v2 02/10] dt-bindings: mmc: tegra: Add nvidia,only-1-8-v property
Date: Thu, 26 Jul 2018 15:05:55 +0200	[thread overview]
Message-ID: <484a31bdaad6d76b4fbb7d6fa80cbb8d@agner.ch> (raw)
In-Reply-To: <1532607560-11253-3-git-send-email-avienamo@nvidia.com>

On 26.07.2018 14:19, Aapo Vienamo wrote:
> Add a property to mark controllers which operate at a 1.8 V fixed I/O
> voltage.
> 
> This feature of the hardware needs to be signaled this way because it
> cannot be probed at runtime or reliably derived from other properties.

Is this really needed? Can we not use vqmmc to determine which voltage
the controller runs on?

There is already some precedence in the SDHCI core to determine which
voltage levels are supported:
https://lkml.org/lkml/2018/7/5/342

--
Stefan

> 
> Signed-off-by: Aapo Vienamo <avienamo@nvidia.com>
> ---
>  Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git
> a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
> b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
> index 90c214d..95010cf 100644
> --- a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
> +++ b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
> @@ -45,6 +45,8 @@ Optional properties for Tegra210 and Tegra186:
>    for controllers supporting multiple voltage levels. The order of names
>    should correspond to the pin configuration states in pinctrl-0 and
>    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.
>  
>  Example:
>  sdhci@700b0000 {

  reply	other threads:[~2018-07-26 13:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 12:19 [PATCH v2 00/10] Tegra SDHCI enable 1.8 V signaling on Tegar210 and Tegra186 Aapo Vienamo
2018-07-26 12:19 ` Aapo Vienamo
2018-07-26 12:19 ` [PATCH v2 01/10] dt-bindings: mmc: tegra: Add pad voltage control properties Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo
2018-07-30 23:22   ` Rob Herring
2018-07-26 12:19 ` [PATCH v2 02/10] dt-bindings: mmc: tegra: Add nvidia,only-1-8-v property Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo
2018-07-26 13:05   ` Stefan Agner [this message]
2018-07-27  8:05     ` Aapo Vienamo
2018-07-27  8:05       ` Aapo Vienamo
2018-07-30 23:24       ` Rob Herring
2018-07-26 12:19 ` [PATCH v2 03/10] mmc: tegra: Reconfigure pad voltages during voltage switching Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo
2018-07-26 13:33   ` Stefan Agner
2018-07-27  8:44     ` Aapo Vienamo
2018-07-27  8:44       ` Aapo Vienamo
2018-07-26 12:19 ` [PATCH v2 04/10] arm64: dts: Add Tegra210 sdmmc pinctrl voltage states Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo
2018-07-26 12:19 ` [PATCH v2 05/10] arm64: dts: Add Tegra186 " Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo
2018-07-26 12:19 ` [PATCH v2 06/10] arm64: dts: tegra210-p2180: Allow ldo2 to go down to 1.8 V Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo
2018-07-26 12:19 ` [PATCH v2 07/10] arm64: dts: tegra210-p2180: Correct sdmmc4 vqmmc-supply Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo
2018-07-26 12:19 ` [PATCH v2 08/10] arm64: dts: tegra210-p2597: Remove no-1-8-v from sdmmc1 Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo
2018-07-26 12:19 ` [PATCH v2 09/10] arm64: dts: tegra210: Add nvidia,only-1-8-v to sdmmc4 Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo
2018-07-26 12:19 ` [PATCH v2 10/10] arm64: dts: tegra186: " Aapo Vienamo
2018-07-26 12:19   ` Aapo Vienamo

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=484a31bdaad6d76b4fbb7d6fa80cbb8d@agner.ch \
    --to=stefan@agner.ch \
    --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-owner@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mperttunen@nvidia.com \
    --cc=robh+dt@kernel.org \
    --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 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.