From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 05/10] ARM: shmobile: r8a7790: Register GPIO devices
Date: Mon, 08 Apr 2013 22:53:08 +0000 [thread overview]
Message-ID: <15036820.QTHSACIj4A@avalon> (raw)
In-Reply-To: <1365413782-17036-6-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Sergei,
On Monday 08 April 2013 16:06:59 Sergei Shtylyov wrote:
> On 08-04-2013 13:36, Laurent Pinchart wrote:
> > Move GPIOs handling from the PFC device to separate GPIO devices.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> >
> > arch/arm/mach-shmobile/setup-r8a7790.c | 35 +++++++++++++++++++++++++++-
> > 1 file changed, 34 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm/mach-shmobile/setup-r8a7790.c
> > b/arch/arm/mach-shmobile/setup-r8a7790.c index 49de2d5..eeef5f6 100644
> > --- a/arch/arm/mach-shmobile/setup-r8a7790.c
> > +++ b/arch/arm/mach-shmobile/setup-r8a7790.c
>
> [...]
>
> > @@ -31,13 +32,45 @@
> > static const struct resource pfc_resources[] = {
> > DEFINE_RES_MEM(0xe6060000, 0x250),
> > - DEFINE_RES_MEM(0xe6050000, 0x5050),
> > };
> >
> > +#define R8A7790_GPIO(idx) \
> > +static struct resource r8a7790_gpio##idx##_resources[] = { \
> > + DEFINE_RES_MEM(0xe6050000 + 0x1000 * (idx), 0x50), \
> > + DEFINE_RES_IRQ(gic_spi(4 + (idx))), \
>
> Aren't we supposed to abandon the use of gic_spi() for gic_iid() now?
I'll let the IRQ experts answer that. I've noticed that the index passed to
gic_spi() matches the datasheet, and the other devices in the file use
gic_spi(), so I went for gic_spi().
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-04-08 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 9:36 [PATCH 05/10] ARM: shmobile: r8a7790: Register GPIO devices Laurent Pinchart
2013-04-08 12:06 ` Sergei Shtylyov
2013-04-08 22:53 ` Laurent Pinchart [this message]
2013-04-09 8:40 ` Simon Horman
2013-04-09 9:26 ` Kuninori Morimoto
2013-04-09 12:13 ` Simon Horman
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=15036820.QTHSACIj4A@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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.