From: Mark Rutland <mark.rutland@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH] ARM: gic: Document Power and Clock Domain optional properties
Date: Wed, 29 Apr 2015 19:28:17 +0100 [thread overview]
Message-ID: <20150429182817.GC17775@leverpostej> (raw)
In-Reply-To: <CAMuHMdVao2jOV7kZrcTw9UMa4kvSRMhfN5KQgQ8V-4fPS6ouaQ@mail.gmail.com>
On Wed, Apr 29, 2015 at 07:12:32PM +0100, Geert Uytterhoeven wrote:
> On Wed, Apr 29, 2015 at 5:15 PM, Mark Rutland <mark.rutland@arm.com> wrote:
> >> > diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
> >> > index 7b315e3..02c8bb4 100644
> >> > --- a/drivers/irqchip/irq-gic.c
> >> > +++ b/drivers/irqchip/irq-gic.c
> >> > @@ -959,6 +959,7 @@ void __init gic_init_bases(unsigned int gic_nr, int irq_start,
> >> > irq_hw_number_t hwirq_base;
> >> > struct gic_chip_data *gic;
> >> > int gic_irqs, irq_base, i;
> >> > + unsigned long iidr;
> >> >
> >> > BUG_ON(gic_nr >= MAX_GIC_NR);
> >> >
> >> > @@ -996,6 +997,9 @@ void __init gic_init_bases(unsigned int gic_nr, int irq_start,
> >> > gic_set_base_accessor(gic, gic_get_common_base);
> >> > }
> >> >
> >> > + iidr = readl_relaxed(gic_data_dist_base(gic) + GIC_DIST_IIDR);
> >> > + pr_info("GICD_IIDR reports 0x%08lx\n", (unsigned long)iidr);
> >>
> >> No need for the cast.
> >
> > For arm64 there is ;)
>
> Why? iidr is already unsigned long.
Ah. indeed it is! For some reason I thought I'd left it as a u32.
Sorry about that; I'll drop the cast.
Thanks,
Mark.
prev parent reply other threads:[~2015-04-29 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 15:00 [PATCH] ARM: gic: Document Power and Clock Domain optional properties Geert Uytterhoeven
2015-04-27 15:25 ` Rob Herring
[not found] ` <CAL_JsqKjXuGp0SRFAVWskJRfyeoko6ybtceJQcDzymshuz9wPw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-27 16:26 ` Geert Uytterhoeven
[not found] ` <1430146811-29862-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-04-27 15:54 ` Mark Rutland
2015-04-27 16:43 ` Geert Uytterhoeven
2015-04-27 17:15 ` Mark Rutland
2015-04-28 8:28 ` Geert Uytterhoeven
[not found] ` <CAMuHMdVY5Oh7b9Pme2jiwtV4GBPqK-T5nfxnB9_1ufFzueUjLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-29 12:57 ` Mark Rutland
2015-04-29 14:09 ` Geert Uytterhoeven
2015-04-29 15:15 ` Mark Rutland
2015-04-29 18:12 ` Geert Uytterhoeven
2015-04-29 18:28 ` Mark Rutland [this message]
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=20150429182817.GC17775@leverpostej \
--to=mark.rutland@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).