From: Anand Moon <linux.amoon@gmail.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org,
Kevin Hilman <khilman@baylibre.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] ARM: dts: meson8b: odroidc1: enable the SDHC controller
Date: Mon, 22 Jun 2020 18:17:10 +0530 [thread overview]
Message-ID: <CANAwSgQC_sf2Hvuf29aeSttF5JmJqBoXLOa=HybFys_hmBns3g@mail.gmail.com> (raw)
In-Reply-To: <20200620163654.37207-4-martin.blumenstingl@googlemail.com>
Hi Martin,
On Sat, 20 Jun 2020 at 22:08, Martin Blumenstingl
<martin.blumenstingl@googlemail.com> wrote:
>
> Odroid-C1 has an eMMC connector where users can optionally install an
> eMMC module. The eMMC modules run off a 1.8V VQMMC supply which means
> that HS-200 mode can be used (this is the highest mode that the SDHC
> controller supports). Enable the SDHC controller so eMMC modules can be
> accessed.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Please add my
Reviewed-by: Anand Moon <linux.amoon@gmail.com>
-Anand
> ---
> arch/arm/boot/dts/meson8b-odroidc1.dts | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/arch/arm/boot/dts/meson8b-odroidc1.dts b/arch/arm/boot/dts/meson8b-odroidc1.dts
> index cb21ac9f517c..0c26467de4d0 100644
> --- a/arch/arm/boot/dts/meson8b-odroidc1.dts
> +++ b/arch/arm/boot/dts/meson8b-odroidc1.dts
> @@ -15,6 +15,7 @@ / {
> aliases {
> serial0 = &uart_AO;
> mmc0 = &sd_card_slot;
> + mmc1 = &sdhc;
> };
>
> chosen {
> @@ -26,6 +27,11 @@ memory {
> reg = <0x40000000 0x40000000>;
> };
>
> + emmc_pwrseq: emmc-pwrseq {
> + compatible = "mmc-pwrseq-emmc";
> + reset-gpios = <&gpio BOOT_9 GPIO_ACTIVE_LOW>;
> + };
> +
> leds {
> compatible = "gpio-leds";
> blue {
> @@ -310,6 +316,26 @@ &saradc {
> vref-supply = <&vcc_1v8>;
> };
>
> +&sdhc {
> + status = "okay";
> +
> + pinctrl-0 = <&sdxc_c_pins>;
> + pinctrl-names = "default";
> +
> + bus-width = <8>;
> + max-frequency = <100000000>;
> +
> + disable-wp;
> + cap-mmc-highspeed;
> + mmc-hs200-1_8v;
> + no-sdio;
> +
> + mmc-pwrseq = <&emmc_pwrseq>;
> +
> + vmmc-supply = <&vcc_3v3>;
> + vqmmc-supply = <&vcc_1v8>;
> +};
> +
> &sdio {
> status = "okay";
>
> --
> 2.27.0
>
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-06-22 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 16:36 [PATCH 0/3] ARM: dts: use the SDHC MMC controller for eMMC Martin Blumenstingl
2020-06-20 16:36 ` [PATCH 1/3] ARM: dts: meson: add the SDHC MMC controller Martin Blumenstingl
2020-06-22 12:47 ` Anand Moon
2020-06-20 16:36 ` [PATCH 2/3] ARM: dts: meson8b: ec100: enable the SDHC controller Martin Blumenstingl
2020-06-20 16:36 ` [PATCH 3/3] ARM: dts: meson8b: odroidc1: " Martin Blumenstingl
2020-06-22 12:47 ` Anand Moon [this message]
2020-07-13 19:03 ` [PATCH 0/3] ARM: dts: use the SDHC MMC controller for eMMC Kevin Hilman
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='CANAwSgQC_sf2Hvuf29aeSttF5JmJqBoXLOa=HybFys_hmBns3g@mail.gmail.com' \
--to=linux.amoon@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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).