From: Simon Horman <horms@verge.net.au>
To: Chris Brandt <Chris.Brandt@renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: r7s72100: fix sdhi clock define
Date: Fri, 13 Jan 2017 09:35:22 +0100 [thread overview]
Message-ID: <20170113083522.GD2269@verge.net.au> (raw)
In-Reply-To: <SG2PR06MB1165F25FA9498C3AAD03D7698A790@SG2PR06MB1165.apcprd06.prod.outlook.com>
On Thu, Jan 12, 2017 at 08:34:26PM +0000, Chris Brandt wrote:
> Hi Geert,
>
> On Thursday, January 12, 2017, Geert Uytterhoeven wrote:
> > This is strange. There are two SDHI channels, but the STBCR12
> > documentation (all versions up to rev. 3.00) says the register has MSTP
> > bits for four SD host interfaces?
> >
> > Can you please enlighten me? Thanks!
>
> Ya, I saw that. There are 2 bits per SDHI channel. I did check and just
> enabling the one works fine.
>
> Honestly, I'm not sure why there are two clock enables.
>
> I'll go back and ask the design team if they can tell me why there are 2.
>
> As I said, I just re-tested and it works fine, but you can hold off on the
> patch if you want until I come up with a real explanation.
I'd prefer to hold off on this for now.
next prev parent reply other threads:[~2017-01-13 8:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:11 [PATCH] ARM: dts: r7s72100: fix sdhi clock define Chris Brandt
2017-01-12 18:11 ` Chris Brandt
2017-01-12 19:57 ` Geert Uytterhoeven
2017-01-12 20:34 ` Chris Brandt
2017-01-12 20:34 ` Chris Brandt
2017-01-13 8:35 ` Simon Horman [this message]
2017-01-13 14:44 ` Chris Brandt
2017-01-13 14:44 ` Chris Brandt
2017-01-13 15:10 ` Geert Uytterhoeven
2017-01-13 15:10 ` Geert Uytterhoeven
2017-01-13 17:16 ` Chris Brandt
2017-01-13 17:16 ` Chris Brandt
2017-01-13 17:31 ` Geert Uytterhoeven
2017-01-13 17:56 ` Chris Brandt
2017-01-13 17:56 ` Chris Brandt
2017-01-16 10:36 ` Geert Uytterhoeven
2017-01-16 10:36 ` Geert Uytterhoeven
2017-01-16 11:40 ` Wolfram Sang
2017-01-17 4:27 ` Chris Brandt
2017-01-17 4:27 ` Chris Brandt
2017-01-17 8:21 ` Wolfram Sang
2017-01-17 8:21 ` Wolfram Sang
2017-01-17 9:16 ` Geert Uytterhoeven
2017-01-17 9:16 ` Geert Uytterhoeven
2017-01-17 9:45 ` Wolfram Sang
2017-01-17 9:52 ` Geert Uytterhoeven
2017-01-17 9:57 ` Wolfram Sang
2017-01-17 9:57 ` Wolfram Sang
2017-01-17 10:00 ` Geert Uytterhoeven
2017-01-17 10:00 ` Geert Uytterhoeven
2017-01-17 14:48 ` Chris Brandt
2017-01-17 18:42 ` Chris Brandt
2017-01-17 19:23 ` Wolfram Sang
2017-01-17 19:23 ` Wolfram Sang
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=20170113083522.GD2269@verge.net.au \
--to=horms@verge.net.au \
--cc=Chris.Brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.