From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linus Walleij <linus.walleij@linaro.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: Re: [PATCH 2/2] pinctrl: sh-pfc: r8a7791: Add alternative MSIOF pin groups
Date: Tue, 25 Feb 2014 18:02:29 +0000 [thread overview]
Message-ID: <1907403.Lds1hseITe@avalon> (raw)
In-Reply-To: <CAMuHMdWt2OZaLT3Z9KODkxcAqtqS27BpOaKFmLDKdxk68KW2Zg@mail.gmail.com>
Hi Geert,
On Tuesday 25 February 2014 18:50:21 Geert Uytterhoeven wrote:
> On Tue, Feb 25, 2014 at 6:19 PM, Laurent Pinchart wrote:
> >> +static const unsigned int msiof1_rx_d_pins[] = {
> >> + /* RXD */
> >> + RCAR_GP_PIN(0, 26),
> >
> > This should be (0, 27).
>
> Wow, nice catch. Thanks a lot!
You're welcome. This is why I dislike reviewing PFC patches though, it's lots
of small numbers that need to be checked.
> >> +static const unsigned int msiof2_ss2_d_pins[] = {
> >> + /* SS2 */
> >> + RCAR_GP_PIN(2, 18),
> >
> > This should be (2, 19).
>
> p. 4-16 of Rev. 0.31 of the R-Car M2 datasheet states that GP2_18 can be
> both MSIOF2_SS2_D (function 3) and MSIOF2_RXD_D (function 5),
> but p. 5-37 disagrees?
> It seems the whole function 3 column on p. 4-16 is offset by one,
> compared to p. 5-37.
>
> Well, (2, 19) sounds more logical, so let's assume p. 5-37 is correct for
> now.
Sounds good to me.
> > > +};
> > > +static const unsigned int msiof2_ss2_d_mux[] = {
> > > + MSIOF2_SS2_D_MARK,
> > > +};
> > > +static const unsigned int msiof2_rx_d_pins[] = {
> > > + /* RXD */
> > > + RCAR_GP_PIN(2, 18),
> > > +};
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-02-25 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 19:53 [PATCH 1/2] pinctrl: sh-pfc: r8a7790: Add alternative MSIOF pin groups Geert Uytterhoeven
2014-02-20 19:53 ` [PATCH 2/2] pinctrl: sh-pfc: r8a7791: " Geert Uytterhoeven
2014-02-25 17:19 ` Laurent Pinchart
2014-02-25 17:50 ` Geert Uytterhoeven
2014-02-25 18:02 ` Laurent Pinchart [this message]
2014-02-25 8:53 ` [PATCH 1/2] pinctrl: sh-pfc: r8a7790: " Linus Walleij
2014-02-25 17:20 ` Laurent Pinchart
2014-02-25 17:07 ` Laurent Pinchart
2014-03-05 1:16 ` Linus Walleij
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=1907403.Lds1hseITe@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.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;
as well as URLs for NNTP newsgroup(s).