[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1907403.Lds1hseITe@avalon>
Date: Tue, 25 Feb 2014 19:02:29 +0100
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Linus Walleij <linus.walleij@...aro.org>,
Linux-sh list <linux-sh@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Geert Uytterhoeven <geert+renesas@...ux-m68k.org>
Subject: Re: [PATCH 2/2] pinctrl: sh-pfc: r8a7791: Add alternative MSIOF pin groups
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists