From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC][PATCH v2] ARM: shmobile: R-Car: add gic_iid macro for ICCIAR / interrupt ID
Date: Wed, 20 Feb 2013 11:41:47 +0000 [thread overview]
Message-ID: <20130220114146.GE3882@linux-sh.org> (raw)
In-Reply-To: <87wqu4el91.wl%kuninori.morimoto.gx@renesas.com>
On Tue, Feb 19, 2013 at 04:14:31PM -0800, Kuninori Morimoto wrote:
>
> Hi Magnus
>
> Thank you for your reply
>
> > > diff --git a/arch/arm/mach-shmobile/board-marzen.c b/arch/arm/mach-shmobile/board-marzen.c
> > > index cdcb799..2338d4b 100644
> > > --- a/arch/arm/mach-shmobile/board-marzen.c
> > > +++ b/arch/arm/mach-shmobile/board-marzen.c
> > > @@ -66,7 +66,7 @@ static struct resource smsc911x_resources[] = {
> > > .flags = IORESOURCE_MEM,
> > > },
> > > [1] = {
> > > - .start = gic_spi(28), /* IRQ 1 */
> > > + .start = gic_iid(0x3c), /* IRQ 1 */
> > > .flags = IORESOURCE_IRQ,
> > > },
> > > };
> >
> > In general we're moving over to DT so for this case I can't say that I
> > care very much. However, if you want to change things around why don't
> > you just do the following?
> >
> > > + .start = 0x3c, /* IRQ 1 */
>
> Actually, I considered this "direct value" style,
> but I thought that it seems un-understandable.
> This gic_iid(xxx) shows some kind of "GIC" value.
>
Agreed. The direct mapping works fine if its understood that the value
being assigned is a direct IRQ number. In the case that it's some other
value that's being adapted, it should go through a canonicalization
wrapper to make the use obvious. Whether there is a 1:1 correlation or
not doesn't particularly matter, as it's still adopting a non-IRQ
resource as an IRQ value.
next prev parent reply other threads:[~2013-02-20 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 8:55 [RFC][PATCH v2] ARM: shmobile: R-Car: add gic_iid macro for ICCIAR / interrupt ID Kuninori Morimoto
2013-02-19 10:15 ` Magnus Damm
2013-02-20 0:14 ` Kuninori Morimoto
2013-02-20 11:41 ` Paul Mundt [this message]
2013-02-22 20:40 ` Simon Horman
2013-02-25 0:05 ` Kuninori Morimoto
2013-02-25 4:41 ` 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=20130220114146.GE3882@linux-sh.org \
--to=lethal@linux-sh.org \
--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