From: Wolfram Sang <wsa@the-dreams.de>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: devicetree@vger.kernel.org,
Takeshi Kihara <takeshi.kihara.df@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org,
Simon Horman <horms+renesas@verge.net.au>,
linux-arm-kernel@lists.infradead.org,
Marek Vasut <marek.vasut+renesas@gmail.com>
Subject: Re: [PATCH 2/2] arm64: dts: r8a77990: ebisu: Enable SDHI interfaces
Date: Tue, 6 Nov 2018 09:34:50 +0100 [thread overview]
Message-ID: <20181106083450.GB1054@kunai> (raw)
In-Reply-To: <20181105214117.11734-2-marek.vasut+renesas@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 360 bytes --]
> + sdhi3_pins: sd3 {
> + groups = "sdhi3_data8", "sdhi3_ctrl";
> + function = "sdhi3";
> + power-source = <1800>;
> + };
> +
> + sdhi3_pins_uhs: sd3_uhs {
> + groups = "sdhi3_data8", "sdhi3_ctrl";
> + function = "sdhi3";
> + power-source = <1800>;
> + };
Shouldn't we have only one pinctrl config here, like you did recently
for the other Gen3 SoCs?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-11-06 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 21:41 [PATCH 1/2] arm64: dts: r8a77990: Add SDHI device nodes Marek Vasut
2018-11-05 21:41 ` [PATCH 2/2] arm64: dts: r8a77990: ebisu: Enable SDHI interfaces Marek Vasut
2018-11-06 5:29 ` Yoshihiro Shimoda
2018-11-06 9:17 ` Marek Vasut
2018-11-06 8:34 ` Wolfram Sang [this message]
2018-11-06 9:18 ` Marek Vasut
2018-11-06 5:26 ` [PATCH 1/2] arm64: dts: r8a77990: Add SDHI device nodes Yoshihiro Shimoda
2018-11-06 9:42 ` Marek Vasut
2018-11-06 10:35 ` Geert Uytterhoeven
2018-11-06 12:17 ` Simon Horman
2018-11-06 20:47 ` Marek Vasut
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=20181106083450.GB1054@kunai \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=takeshi.kihara.df@renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.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).