From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Simon <horms@verge.net.au>, Magnus <magnus.damm@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: Re: [PATCH 1/2][RFC] pinctrl: sh-pfc: Initial R8A7795 PFC support
Date: Mon, 31 Aug 2015 10:00:53 +0000 [thread overview]
Message-ID: <18242717.vkv89r6G4C@avalon> (raw)
In-Reply-To: <87y4gs2bqy.wl%kuninori.morimoto.gx@renesas.com>
Hello Morimoto-san,
On Monday 31 August 2015 06:53:36 Kuninori Morimoto wrote:
> Hi Laurent
>
> >> +#define CPU_ALL_PORT(fn, sfx) \
> >> + PORT_GP_32(0, fn, sfx), \
> >> + PORT_GP_32(1, fn, sfx), \
> >> + PORT_GP_32(2, fn, sfx), \
> >> + PORT_GP_32(3, fn, sfx), \
> >> + PORT_GP_32(4, fn, sfx), \
> >> + PORT_GP_32(5, fn, sfx), \
> >> + PORT_GP_32(6, fn, sfx), \
> >> + PORT_GP_32(7, fn, sfx)
> >
> > Not all GPIO banks include 32 pins. From a quick look at the datasheet the
> > following GPIO pins are available.
>
> Thanks. will fix in next version
>
> >> + { PINMUX_CFG_REG_VAR("MOD_SEL1", 0xe6060504, 32,
> >> + 2, 3, 1, 2, 3, 1, 1, 2, 1,
> >> + 2, 1, 1, 1, 1, 1, 2, 1, 1, 1, 1, 1, 1, 1) {
>
> (snip)
>
> >> + /* SEL_SCIF3 [1] */
> >> + FN_SEL_SCIF3_0, FN_SEL_SCIF3_1,
> >> + /* SEL_SCIF2 [1] */
> >> + FN_SEL_SCIF2_0, FN_SEL_SCIF2_1,
> >> + /* SEL_SCIF1 [1] */
> >> + FN_SEL_SCIF1_0, FN_SEL_SCIF1_1,
> >> + /* SEL_SCIF [1] */
> >> + FN_SEL_SCIF_0, FN_SEL_SCIF_1,
> >> + /* SEL_REMOCON [1] */
> >> + FN_SEL_REMOCON_0, FN_SEL_REMOCON_1,
> >> + /* RESERVED [2] */
> >> + 0, 0, 0, 0,
> >
> > According to the datasheet those two bits are supposed to control the RDS
> > clock and data pins (whatever they are).
>
> Thank you, but sorry.
> Latest version indicates these are reserved bit.
My bad, I had checked an older version of the datasheet.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-08-31 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 9:31 [PATCH 0/2][RFC] pinctrl: sh-pfc: r8a7795 support Kuninori Morimoto
2015-08-28 9:32 ` [PATCH 1/2][RFC] pinctrl: sh-pfc: Initial R8A7795 PFC support Kuninori Morimoto
2015-08-28 19:23 ` Laurent Pinchart
2015-08-31 6:53 ` Kuninori Morimoto
2015-08-31 10:00 ` Laurent Pinchart [this message]
2015-08-28 9:33 ` [PATCH 2/2][RFC] pinctrl: sh-pfc: r8a7795: add SCIFx support Kuninori Morimoto
2015-08-28 19:24 ` Laurent Pinchart
2015-08-31 0:06 ` Kuninori Morimoto
2015-08-31 8:59 ` Kuninori Morimoto
2015-08-31 10:53 ` Laurent Pinchart
2015-09-01 0:04 ` Kuninori Morimoto
2015-08-29 5:13 ` Magnus Damm
2015-08-31 0:04 ` Kuninori Morimoto
2015-08-31 4:46 ` Magnus Damm
2015-08-31 4:50 ` [PATCH 0/2][RFC] pinctrl: sh-pfc: r8a7795 support Magnus Damm
2015-08-31 5:58 ` Kuninori Morimoto
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=18242717.vkv89r6G4C@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).