From: dev@lynxeye.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: beaver: allow SD card voltage to be changed
Date: Fri, 13 May 2016 09:25:31 +0200 [thread overview]
Message-ID: <1463124331.2459.0.camel@lynxeye.de> (raw)
In-Reply-To: <1456779678-20173-1-git-send-email-dev@lynxeye.de>
Am Montag, den 29.02.2016, 22:01 +0100 schrieb Lucas Stach:
> This allows to switch the card signal voltage level to 1.8V,
> which is needed for any ultra high speed modes to work.
>
> Signed-off-by: Lucas Stach <dev@lynxeye.de>
> ---
> This needs the SDMMC memcomp pad calibration patches I just
> sent out to be applied, otherwise the card voltage change will
> fail with a message in the kernel log and a fall back to
> high speed operation.
The patches this one depends on have been applied for some time now.
Please pick up this patch.
Thanks,
Lucas
> ---
> ?arch/arm/boot/dts/tegra30-beaver.dts | 3 ++-
> ?1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/tegra30-beaver.dts
> b/arch/arm/boot/dts/tegra30-beaver.dts
> index 1daed40..6b237f2 100644
> --- a/arch/arm/boot/dts/tegra30-beaver.dts
> +++ b/arch/arm/boot/dts/tegra30-beaver.dts
> @@ -1848,7 +1848,7 @@
> ?
> ? ldo5_reg: ldo5 {
> ? regulator-name =
> "vddio_sdmmc,avdd_vdac";
> - regulator-min-microvolt =
> <3300000>;
> + regulator-min-microvolt =
> <1800000>;
> ? regulator-max-microvolt =
> <3300000>;
> ? regulator-always-on;
> ? };
> @@ -1919,6 +1919,7 @@
> ?
> ? sdhci at 78000000 {
> ? status = "okay";
> + vqmmc-supply = <&ldo5_reg>;
> ? cd-gpios = <&gpio TEGRA_GPIO(I, 5) GPIO_ACTIVE_LOW>;
> ? wp-gpios = <&gpio TEGRA_GPIO(T, 3)
> GPIO_ACTIVE_HIGH>;
> ? power-gpios = <&gpio TEGRA_GPIO(D, 7)
> GPIO_ACTIVE_HIGH>;
next prev parent reply other threads:[~2016-05-13 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 21:01 [PATCH] ARM: tegra: beaver: allow SD card voltage to be changed Lucas Stach
2016-05-13 7:25 ` Lucas Stach [this message]
2016-05-13 17:27 ` Thierry Reding
2016-05-13 19:08 ` Lucas Stach
2016-05-19 14:29 ` Jon Hunter
2016-06-13 10:22 ` Jon Hunter
2016-06-14 6:20 ` Adrian Hunter
2016-06-14 8:23 ` Jon Hunter
2016-06-14 10:05 ` Adrian Hunter
2016-06-14 14:19 ` Jon Hunter
2016-06-24 9:14 ` Jon Hunter
2016-06-28 13:27 ` Adrian Hunter
2016-05-19 14:31 ` Jon Hunter
2016-05-19 16:12 ` Stephen Warren
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=1463124331.2459.0.camel@lynxeye.de \
--to=dev@lynxeye.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).