From: guodong.xu@linaro.org (Guodong Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: dts: hi6220: add acpu_sctrl
Date: Wed, 16 Aug 2017 11:01:15 +0800 [thread overview]
Message-ID: <CAFGCpxw0fNa5srmWuEZKTBN15LHeG4M-xPSiwuPnhwB-DQ2irA@mail.gmail.com> (raw)
In-Reply-To: <20170815150138.GL22218@golem.pkh.me>
On Tue, Aug 15, 2017 at 11:01 PM, Cl?ment B?sch <u@pkh.me> wrote:
> On Tue, Aug 15, 2017 at 02:32:43PM +0100, Wei Xu wrote:
>> Hi Zhangfei,
>>
>> On 2017/4/18 2:17, Zhangfei Gao wrote:
>> > Add acpu_sctrl clock node
>> >
>> > Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>> > Signed-off-by: Li Pengcheng <lipengcheng8@huawei.com>
>> > ---
>> > arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 6 ++++++
>> > 1 file changed, 6 insertions(+)
>> >
>> > diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
>> > index 470461d..710cc34 100644
>> > --- a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
>> > +++ b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
>> > @@ -262,6 +262,12 @@
>> > #clock-cells = <1>;
>> > };
>> >
>> > + acpu_sctrl: acpu_sctrl at f7032000 {
>
> I think the unit address is incorrect here (this value has been copied
> from the pm controller while it should match the 1st one the reg).
>
>> > + compatible = "hisilicon,hi6220-acpu-sctrl", "syscon";
>> > + reg = <0x0 0xf6504000 0x0 0x1000>;
>> > + #clock-cells = <1>;
>> > + };
>> > +
>> > medianoc_ade: medianoc_ade at f4520000 {
>> > compatible = "syscon";
>> > reg = <0x0 0xf4520000 0x0 0x4000>;
>> >
>
> Also I'm sorry I'm going to ask stupid questions:
>
> - why 's' in "sctrl" while all the other node controllers declared around
> seems to use "ctrl"?
>
> - is it possible to have access to the specs where those addresses can be
> found? The only public doc I could find is the "Hi6220V100 Multi-Mode
> Application Processor" one where this information doesn't seem present.
>
That's the only public doc. But if you need, welcome to discuss with
me off-line about referencing kernels for hikey.
> - is there any work pending adding the pmu counters node (interrupt
> GCI_SPI 99) ? AFAIK the ACPU controller added here can be used to enable
> the counters.
>
For hikey PMU, please have a look of this patchset:
- https://github.com/96boards/linux/pull/86/commits
Discussion is here:
- https://discuss.96boards.org/t/performance-monitoring-unit-pmu/293/4
Due to its implementation is not compatible with upstream, this
patchset was not upstreamed. If you are interested, welcome to adding
them LKML.
Appreciate your effort.
-Guodong
>>
>> Thanks!
>> Applied to the hisilicon dt tree since the driver part is in the mainline now.
>>
>
> Is this refering to https://github.com/hisilicon/linux-hisi/commits/next/dt64 ?
>
> [...]
>
> --
> Cl?ment B.
next prev parent reply other threads:[~2017-08-16 3:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 1:17 [PATCH 1/2] clk: hi6220: add acpu clock Zhangfei Gao
2017-04-18 1:17 ` [PATCH 2/2] arm64: dts: hi6220: add acpu_sctrl Zhangfei Gao
2017-06-15 15:46 ` Wei Xu
2017-08-15 13:32 ` Wei Xu
2017-08-15 15:01 ` Clément Bœsch
2017-08-16 3:01 ` Guodong Xu [this message]
2017-08-16 3:02 ` zhangfei
2017-04-20 15:57 ` [PATCH 1/2] clk: hi6220: add acpu clock Rob Herring
2017-05-17 1:31 ` zhangfei
2017-06-12 1:29 ` zhangfei
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=CAFGCpxw0fNa5srmWuEZKTBN15LHeG4M-xPSiwuPnhwB-DQ2irA@mail.gmail.com \
--to=guodong.xu@linaro.org \
--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).