From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms@verge.net.au>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: r8a7792: add SDHI support
Date: Wed, 20 Jul 2016 16:57:05 +0300 [thread overview]
Message-ID: <772f56cd-15ad-e4d6-69c1-e96da2c50300@cogentembedded.com> (raw)
In-Reply-To: <CAMuHMdXez5KZMH=3=egqWWP9Dp9gSRKw=kqHBMPnNjwwAv=Jdg@mail.gmail.com>
On 07/20/2016 04:50 PM, Geert Uytterhoeven wrote:
>>> BTW, given SDHI on V2H doesn't support SDR50/SDR104, unlike the instances
>>> on other R-Car Gen2 SoCs, can you please tell us the version value, as
>>> read
>>> from CTL_VERSION in sh_mobile_sdhi_sdbuf_width()?
>>
>> It's 0xCB0D, the same as on other SoCs.
>
> Thanks!
>
> #define SDHI_VER_GEN2_SDR104 0xcb0d
Not seeing this #define, where is it?
> Not good, as it doesn't support SDR50/SDR104....
Does it have the register at 0x324 tho?
> Gr{oetje,eeting}s,
>
> Geert
MBR, Sergei
prev parent reply other threads:[~2016-07-20 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 21:09 [PATCH 0/2] Add R8A7792 SDHI support Sergei Shtylyov
2016-07-12 21:10 ` [PATCH 1/2] ARM: dts: r8a7792: add SD clocks Sergei Shtylyov
2016-07-13 1:29 ` Geert Uytterhoeven
2016-07-12 21:11 ` [PATCH 2/2] ARM: dts: r8a7792: add SDHI support Sergei Shtylyov
2016-07-13 1:37 ` Geert Uytterhoeven
2016-07-17 22:58 ` Simon Horman
2016-07-18 19:12 ` Sergei Shtylyov
2016-07-20 8:07 ` Geert Uytterhoeven
2016-07-20 13:40 ` Sergei Shtylyov
2016-07-20 13:50 ` Geert Uytterhoeven
2016-07-20 13:57 ` Sergei Shtylyov [this message]
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=772f56cd-15ad-e4d6-69c1-e96da2c50300@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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