linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm64: dts: Add dts files for Hisilicon Hi6220 SoC
Date: Fri, 06 Feb 2015 09:07:10 +0000	[thread overview]
Message-ID: <54D4843E.7060201@arm.com> (raw)
In-Reply-To: <CAAS=xmgsuY=c8-n_pDiZjLe2u+SPX7msRje7h0sNkRtT3HLfQA@mail.gmail.com>

On 06/02/15 08:42, Brent Wang wrote:

[...]

>>
>>> +                   <0x0 0xf6802000 0x0 0x2000>, /* GICC */
>>> +                   <0x0 0xf6804000 0x0 0x2000>, /* GICH */
>>> +                   <0x0 0xf6806000 0x0 0x2000>; /* GICV */
>>
>> I guess no-one's bothered to consider 64k pages?
>>
>> Given GICH and GICV, I hope that this platform is booted at EL2?
> Transfer from EL3 to EL1 directly, keep these two just for future use.

That's a real shame, as it keeps users away from some key aspects of the
ARMv8 architecture.

>>
>>> +             #interrupt-cells = <3>;
>>> +             #address-cells = <0>;
>>> +             interrupt-controller;

And if you're keeping GICH/GICV, where is the maintenance interrupt?

>>> +     };
>>> +
>>> +
>>> +     timer {
>>> +             compatible = "arm,armv8-timer";
>>> +             interrupt-parent = <&gic>;
>>> +             interrupts = <1 13 0xff08>,
>>> +                          <1 14 0xff08>,
>>> +                          <1 11 0xff08>,
>>> +                          <1 10 0xff08>;
>>> +             clock-frequency = <1200000>;
>>> +     };
>>
>> NAK. Fix your firmware to configure CNTFRQ, on all CPUs.
> Fix in next version, maybe it will take some time to change firmware.

While you're at it, make sure CNTVOFF_EL2 is set to zero on all CPUs
before dropping to EL1. This tends to be overlooked.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2015-02-06  9:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05  9:24 [PATCH 0/3] arm64,hi6220: Enable Hisilicon Hi6220 SoC Bintian Wang
2015-02-05  9:24 ` [PATCH 1/3] arm64: Enable Hisilicon ARMv8 SoC family in Kconfig and defconfig Bintian Wang
2015-02-05  9:24 ` [PATCH 2/3] clk: hi6220: Clock driver support for Hisilicon hi6220 SoC Bintian Wang
2015-02-05 19:25   ` Mark Rutland
2015-02-06  7:32     ` Brent Wang
2015-02-06 18:10   ` Tyler Baker
2015-02-07  2:05     ` Brent Wang
2015-02-07 22:05       ` Tyler Baker
2015-02-05  9:24 ` [PATCH 3/3] arm64: dts: Add dts files for Hisilicon Hi6220 SoC Bintian Wang
2015-02-05 19:30   ` Mark Rutland
2015-02-06  8:42     ` Brent Wang
2015-02-06  9:07       ` Marc Zyngier [this message]
2015-02-06 10:31         ` Mark Rutland
2015-02-09  3:26         ` Brent Wang
2015-02-06 10:44       ` Mark Rutland
2015-02-06 15:37         ` Brent Wang
2015-02-10 13:37           ` Mark Rutland
2015-02-10 14:20             ` Brent Wang
2015-02-10 15:27               ` Mark Rutland
2015-02-11  1:49                 ` Brent Wang
2015-04-12  6:40       ` Brent Wang
2015-04-12 10:57         ` Marc Zyngier
2015-04-12 13:07           ` Brent Wang
2015-02-05 18:46 ` [PATCH 0/3] arm64,hi6220: Enable " Tyler Baker
2015-02-05 19:02   ` Olof Johansson
2015-02-05 23:52     ` Tyler Baker
     [not found]       ` <CAAS=xmhj8UMwooYrXQBqzR=J5ernj+EWGV1AqEtHHoWiBgw8gA@mail.gmail.com>
2015-02-06  6:18         ` Olof Johansson
2015-02-06  6:35           ` Brent Wang

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=54D4843E.7060201@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).