From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh-pfc: r8a7779: fixup INDTx address
Date: Wed, 06 Mar 2013 01:58:48 +0000 [thread overview]
Message-ID: <20130306015847.GG20819@verge.net.au> (raw)
In-Reply-To: <87lia3pn80.wl%kuninori.morimoto.gx@renesas.com>
On Tue, Mar 05, 2013 at 04:51:28PM -0800, Kuninori Morimoto wrote:
>
> Hi Phil
>
> Thank you for your reply
>
> > > static struct pinmux_data_reg pinmux_data_regs[] = {
> > > - { PINMUX_DATA_REG("INDT0", 0xffc40008, 32) { GP_INDT(0) } },
> > > - { PINMUX_DATA_REG("INDT1", 0xffc41008, 32) { GP_INDT(1) } },
> > > - { PINMUX_DATA_REG("INDT2", 0xffc42008, 32) { GP_INDT(2) } },
> > > - { PINMUX_DATA_REG("INDT3", 0xffc43008, 32) { GP_INDT(3) } },
> > > - { PINMUX_DATA_REG("INDT4", 0xffc44008, 32) { GP_INDT(4) } },
> > > - { PINMUX_DATA_REG("INDT5", 0xffc45008, 32) { GP_INDT(5) } },
> > > - { PINMUX_DATA_REG("INDT6", 0xffc46008, 32) {
> > > + { PINMUX_DATA_REG("INDT0", 0xffc4000c, 32) { GP_INDT(0) } },
> > > + { PINMUX_DATA_REG("INDT1", 0xffc4100c, 32) { GP_INDT(1) } },
> > > + { PINMUX_DATA_REG("INDT2", 0xffc4200c, 32) { GP_INDT(2) } },
> > > + { PINMUX_DATA_REG("INDT3", 0xffc4300c, 32) { GP_INDT(3) } },
> > > + { PINMUX_DATA_REG("INDT4", 0xffc4400c, 32) { GP_INDT(4) } },
> > > + { PINMUX_DATA_REG("INDT5", 0xffc4500c, 32) { GP_INDT(5) } },
> > > + { PINMUX_DATA_REG("INDT6", 0xffc4600c, 32) {
> > > 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> > > 0, 0, 0, 0, 0, 0, 0, GP_6_8_DATA,
> > > GP_6_7_DATA, GP_6_6_DATA, GP_6_5_DATA, GP_6_4_DATA,
> >
> > Hmm, this isn't what you want. I sent a similar patch on this a while back
> > before realising that the problem is that the pfc driver doesn't support
> > separate input and output data registers, only one reg for both input and
> > output. With the code as it is, the gpio pins act as outputs. Changing the
> > addresses as per this patch means the gpios act now as inputs.
>
> This patch ?
> [sh: pfc: Add ability to use separate read & write GPIO data regs]
>
> I need more information about this, because my previous R-Car M1 GPIO is
> using INPUT address like above
>
> - Is your patch (above patch ?) applied to Simon's branch ?
No, it is not in my tree.
I would be happy to add it if Laurent is happy with it.
Or for him to include it in his forthcoming pinctrl patch set(s).
> - Is some SoC (= H1 ?) using it ?
>
> I need sample code
next prev parent reply other threads:[~2013-03-06 1:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 8:45 [PATCH] sh-pfc: r8a7779: fixup INDTx address Kuninori Morimoto
2013-03-05 3:18 ` Simon Horman
2013-03-05 4:11 ` Paul Mundt
2013-03-05 4:14 ` Kuninori Morimoto
2013-03-05 8:58 ` Simon Horman
2013-03-05 17:51 ` phil.edworthy
2013-03-06 0:39 ` Laurent Pinchart
2013-03-06 0:51 ` Kuninori Morimoto
2013-03-06 1:58 ` Simon Horman [this message]
2013-03-06 1:59 ` Simon Horman
2013-03-06 7:18 ` phil.edworthy
2013-03-06 7:29 ` Simon Horman
2013-03-06 7:53 ` Magnus Damm
2013-03-06 7:58 ` Kuninori Morimoto
2013-03-06 8:50 ` phil.edworthy
2013-03-06 8:54 ` Magnus Damm
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=20130306015847.GG20819@verge.net.au \
--to=horms@verge.net.au \
--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 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.