From: Jisheng Zhang <jszhang@marvell.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Marc Zyngier <Marc.Zyngier@arm.com>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Mark Rutland <Mark.Rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: ARM: Fix the Generic Timers interrupt active level description
Date: Fri, 28 Nov 2014 18:51:43 +0800 [thread overview]
Message-ID: <20141128185143.00ee05b5@xhacker> (raw)
In-Reply-To: <20141128103843.GW828@e106497-lin.cambridge.arm.com>
On Fri, 28 Nov 2014 02:38:43 -0800
Liviu Dudau <Liviu.Dudau@arm.com> wrote:
> On Fri, Nov 28, 2014 at 03:12:52AM +0000, Jisheng Zhang wrote:
> > Dear Marc and Liviu,
> >
> > On Thu, 27 Nov 2014 10:39:28 -0800
> > Marc Zyngier <marc.zyngier@arm.com> wrote:
> >
> > > On 27/11/14 16:21, Liviu Dudau wrote:
> > > > The Cortex-A5x TRM states in paragraph "9.2 Generic Timer functional
> > > > description" that generic timers provide a level not edge interrupt
> > > > output. Fix the device trees to correctly describe this.
> > > >
> > > > While doing this update the CPU mask to match the number of described
> > > > CPUs as well as the DT bindings documentation for Generic Timers.
> > > >
> > > > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> > >
> > > Acked-by: Marc Zyngier <marc.zyngier@arm.com>
> > >
> > > M.
> > >
> > > > ---
> > > >
> > > > Arnd, Olof: This is on top of linux-next/master as it patches Juno's
> > > > as well as all the other ARM DTs.
> > > >
> > > > --
> > > >
> > > > Documentation/devicetree/bindings/arm/arch_timer.txt | 8 ++++----
> > > > arch/arm64/boot/dts/arm/foundation-v8.dts | 8 ++++----
> > > > arch/arm64/boot/dts/arm/juno.dts | 8 ++++----
> > > > arch/arm64/boot/dts/arm/rtsm_ve-aemv8a.dts | 8 ++++----
> > > > 4 files changed, 16 insertions(+), 16 deletions(-)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/arm/arch_timer.txt
> > > > b/Documentation/devicetree/bindings/arm/arch_timer.txt index
> > > > 37b2caf..6d2aa87 100644 ---
> > > > a/Documentation/devicetree/bindings/arm/arch_timer.txt +++
> > > > b/Documentation/devicetree/bindings/arm/arch_timer.txt @@ -27,10
> > > > +27,10 @@ Example: timer {
> > > > compatible = "arm,cortex-a15-timer",
> > > > "arm,armv7-timer";
> > > > - interrupts = <1 13 0xf08>,
> > > > - <1 14 0xf08>,
> > > > - <1 11 0xf08>,
> > > > - <1 10 0xf08>;
> > > > + interrupts = <1 13 0xf04>,
> > > > + <1 14 0xf04>,
> > > > + <1 11 0xf04>,
> > > > + <1 10 0xf04>;
> > > > clock-frequency = <100000000>;
> > > > };
> > > >
> >
> > Does it mean we also need to fix the interrupt level description under
> > arch/arm/boot/dts? I found they are also wrong or I misunderstand
> > something?
>
> Hi Jisheng,
>
> It looks like Marc and I managed to confuse ourselves. The TRM for GIC-500
> and GIC-400 (basically covering most of GICv1 and > GICv2) clearly says
> that for *PPIs* the level triggered interrupts are active-LOW.
>
> So, this patch is invalid and my v1 version is correct, but Marc tells that
> in that case the GIC driver needs patching (which I'm going to look into).
>
Got it. Thanks for clarification.
next prev parent reply other threads:[~2014-11-28 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 16:21 [PATCH v2] arm64: ARM: Fix the Generic Timers interrupt active level description Liviu Dudau
[not found] ` <1417105283-19575-1-git-send-email-Liviu.Dudau-5wv7dgnIgG8@public.gmane.org>
2014-11-27 18:39 ` Marc Zyngier
[not found] ` <54776FE0.8030600-5wv7dgnIgG8@public.gmane.org>
2014-11-28 3:12 ` Jisheng Zhang
2014-11-28 10:38 ` Liviu Dudau
2014-11-28 10:51 ` Jisheng Zhang [this message]
2014-11-28 10:56 ` Marc Zyngier
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=20141128185143.00ee05b5@xhacker \
--to=jszhang@marvell.com \
--cc=Liviu.Dudau@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Will.Deacon@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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).