From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Ian Molton <ian@mnementh.co.uk>,
Ulf Hansson <ulf.hansson@linaro.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-mmc@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Ben Hutchings <ben.hutchings@codethink.co.uk>
Subject: Re: [PATCH/RFC 3/3] ARM: dts: r8a7790: lager: Enable UHS-I SDR-104
Date: Thu, 12 May 2016 08:11:27 +0900 [thread overview]
Message-ID: <20160511231126.GA15521@verge.net.au> (raw)
In-Reply-To: <CANqRtoRjZjC=uEBvJsWYwu0EMEZwO3zS0JWNwVoBR8zjakMpnA@mail.gmail.com>
On Tue, May 10, 2016 at 06:13:55PM +0900, Magnus Damm wrote:
> On Tue, May 10, 2016 at 2:52 PM, Simon Horman
> <horms+renesas@verge.net.au> wrote:
> > Add the sd-uhs-sdr104 property to SDHI0.
> >
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > ---
> > arch/arm/boot/dts/r8a7790-lager.dts | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm/boot/dts/r8a7790-lager.dts b/arch/arm/boot/dts/r8a7790-lager.dts
> > index 749ba02b6a53..05d1ff7acee2 100644
> > --- a/arch/arm/boot/dts/r8a7790-lager.dts
> > +++ b/arch/arm/boot/dts/r8a7790-lager.dts
> > @@ -559,6 +559,7 @@
> > vqmmc-supply = <&vccq_sdhi0>;
> > cd-gpios = <&gpio3 6 GPIO_ACTIVE_LOW>;
> > sd-uhs-sdr50;
> > + sd-uhs-sdr104;
> > status = "okay";
>
> Hi Simon,
>
> Thanks for this - interesting to see!! From what I can tell this code
> is targeting r8a7790 Lager, and based on the data sheet and the DTS
> there are four SDHI channels for the r8a7790 SoC. All R-Car Gen2 SDHI
> channels are not identical, so on r8a7790 it looks like SDHI0 and
> SDHI1 have extended capabilities for the clocks (and probably support
> SDR104) while SDHI2 and SDHI3 do not have this hardware feature. How
> is this difference handled today? In my mind it would make sense to
> have different compat strings, but I think we differentiate with
> resource size today?
Probably I am missing the point somehow but my understanding is that that
with this and other recent changes these differences are described by DT
properties rather than the compatibility string. In particular the presence
or absence of sd-uhs-sdr50 and sd-uhs-sdr104, and the value of
max-frequency.
Now you mention this I do wonder if sd-uhs-sdr50 and sd-uhs-sdr104 are
SoC properties and thus should be present in r8a7790.dtsi rather than
r8a7790-lager.dts.
> So with this patches I can see that you enable SDR104 on SDHI0 on
> Lager which makes sense, but is SDHI2 support still OK?
I will double check but I think so.
next prev parent reply other threads:[~2016-05-11 23:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 5:52 [PATCH/RFC 0/3] UHS-I SDR-104 support for sh_mobile_sdhi Simon Horman
2016-05-10 5:52 ` [PATCH/RFC 1/3] mmc: tmio: Add tuning support Simon Horman
2016-05-12 6:12 ` Yoshihiro Shimoda
2016-05-13 2:36 ` Simon Horman
2016-05-12 16:50 ` Wolfram Sang
2016-05-13 2:28 ` Simon Horman
2016-05-13 3:31 ` Simon Horman
2016-05-10 5:52 ` [PATCH/RFC 2/3] mmc: sh_mobile_sdhi: " Simon Horman
2016-05-10 6:25 ` Kuninori Morimoto
2016-05-11 23:13 ` Simon Horman
2016-05-12 16:50 ` Wolfram Sang
2016-05-10 5:52 ` [PATCH/RFC 3/3] ARM: dts: r8a7790: lager: Enable UHS-I SDR-104 Simon Horman
2016-05-10 9:13 ` Magnus Damm
2016-05-11 12:44 ` Wolfram Sang
2016-05-11 23:11 ` Simon Horman [this message]
2016-05-12 6:30 ` [PATCH/RFC 0/3] UHS-I SDR-104 support for sh_mobile_sdhi Yoshihiro Shimoda
2016-05-12 6:45 ` Geert Uytterhoeven
2016-05-12 7:45 ` Yoshihiro Shimoda
2016-05-12 7:47 ` Geert Uytterhoeven
2016-05-12 8:09 ` Yoshihiro Shimoda
2016-05-12 8:32 ` Geert Uytterhoeven
[not found] ` <SG2PR06MB0919824AFCAE20C395E50738D8730@SG2PR06MB0919.apcprd06.prod.outlook.com>
2016-05-12 12:32 ` Geert Uytterhoeven
2016-05-12 12:41 ` Wolfram Sang
2016-05-12 12:53 ` Geert Uytterhoeven
2016-05-13 2:32 ` Simon Horman
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=20160511231126.GA15521@verge.net.au \
--to=horms@verge.net.au \
--cc=ben.hutchings@codethink.co.uk \
--cc=ian@mnementh.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.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).