From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh-pfc: r8a7779: fixup INDTx address
Date: Tue, 05 Mar 2013 03:18:52 +0000 [thread overview]
Message-ID: <20130305031850.GN16128@verge.net.au> (raw)
In-Reply-To: <87lia3pn80.wl%kuninori.morimoto.gx@renesas.com>
[ Cc: Linus Walleij ]
Hi Linus, Hi Paul, Hi Laurent,
I'm a little unsure how everyone would like to handle
drivers/pinctrl/sh-pfc/ updates.
I'm happy to create a pfc branch and send pull requests to Linus.
Or for Paul to handle things. Or for Laurent to handle things.
Or for other suggestions.
To confuse things, I believe there are a batch of PFC changes that
will make sense to take through the arm-soc tree due to dependencies.
Morimoto-san,
could you comment on how critical this change is.
Does anything in 3.9-rc1 depend on it?
On Mon, Mar 04, 2013 at 12:45:39AM -0800, Kuninori Morimoto wrote:
> INDTn address is 0xFFC4x000C. 0xFFC4x0008 is OUTDTn
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> drivers/pinctrl/sh-pfc/pfc-r8a7779.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a7779.c b/drivers/pinctrl/sh-pfc/pfc-r8a7779.c
> index 13feaa0..cb97fb6 100644
> --- a/drivers/pinctrl/sh-pfc/pfc-r8a7779.c
> +++ b/drivers/pinctrl/sh-pfc/pfc-r8a7779.c
> @@ -2585,13 +2585,13 @@ static struct pinmux_cfg_reg pinmux_config_regs[] = {
> };
>
> 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,
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-03-05 3:18 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 [this message]
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
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=20130305031850.GN16128@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox