From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Paul Cercueil" <paul@opendingux.net>, 周琰杰 <zhouyanjie@wanyeetech.com>
Cc: Paul Cercueil <paul@crapouillou.net>,
tglx@linutronix.de, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, dongsheng.qiu@ingenic.com,
aric.pzqi@ingenic.com, rick.tyliu@ingenic.com,
sihui.liu@ingenic.com, jun.jiang@ingenic.com,
sernia.zhou@foxmail.com
Subject: Re: [PATCH v2 2/2] clocksource: Ingenic: Add SMP/SMT support for sysost driver.
Date: Wed, 16 Jun 2021 16:57:39 +0200 [thread overview]
Message-ID: <f1f6562d-d871-ffeb-e058-0891d6ab4ec8@linaro.org> (raw)
In-Reply-To: <QEAPUQ.HGLUYKP0W4ZH@opendingux.net>
Hi,
On 14/06/2021 18:42, Paul Cercueil wrote:
> Hi Zhou,
[ please trim ... ]
>>> >> The DT documentation only mentions one memory resource. Here, you
>>> >> map \x7fa second one, which is not used anywhere. I'm really confused
>>> >> about \x7fwhat you're trying to do here.
>>> >>
>>> >
>>> > X2000 and X2100 divide the OST into two parts. The global timer is
>>> > the first part, which is still located at the address of 0x12000000,
>>> > and the percpu timers are the second part, the starting address is
>>> > 0x12100000, and each timer is offset by 0x100 (percpu timer0 is at
>>> > 0x12100000, percpu timer1 is at 0x12100100, percpu timer2 is at
>>> > 0x12100200, percpu timer3 is at 0x12100300). This one is used in
>>> > line 593 of the code.
>>>
>>> Then you need two different DT nodes, one at each start address.
>>> Either use different drivers (since the register sets are different),
>>> or *if* it can be implemented cleanly in ingenic-sysost.c, different
>>> compatible strings - one for the global timer and one for the percpu
>>> timers.
>>
>> Sorry, I did not describe it clearly. Although the global timer and
>> percpu timers are divided into two parts, they still belong to the same
>> hardware module. The base address of the entire module is 0x12000000,
>> but the control register of the global timer is not shifted. The percpu
>> timers are shifted by 0x100000 as a whole (the situation here is
>> similar to PDMA, which is also divided into two parts: the
>> channel-related registers are not shifted, while the system
>> control-related registers are shifted by 0x1000 as a whole). I think
>> maybe we can follow PDMA's approach and add corresponding instructions
>> in the DT documentation. This can avoid confusion caused by splitting
>> different parts of the same hardware module into two nodes, and at the
>> same time keep the code of the devicetree as simple and clear as
>> possible.
>>
>> What do you think about that?
>
> Looking at the programming manual, these are not the same hardware
> module. They are on different addresses, are functionally independent,
> and are even described in different chapters of the PM; so I stick to
> what I said earlier.
>
> Cheers,
> -Paul
>
>> Thanks and best regards!
>>
>>>
>>> -Paul
[ ... ]
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2021-06-16 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 16:31 周琰杰 (Zhou Yanjie)
2021-06-04 16:31 ` [PATCH v2 1/2] clocksource: Ingenic: Rename unreasonable array names 周琰杰 (Zhou Yanjie)
2021-06-16 13:56 ` Daniel Lezcano
2021-06-18 16:03 ` [tip: timers/core] clocksource/drivers/ingenic: " tip-bot2 for 周琰杰
2021-06-04 16:31 ` [PATCH v2 2/2] clocksource: Ingenic: Add SMP/SMT support for sysost driver 周琰杰 (Zhou Yanjie)
2021-06-10 15:30 ` Paul Cercueil
2021-06-11 15:31 ` Zhou Yanjie
2021-06-11 15:44 ` Paul Cercueil
2021-06-12 15:48 ` 周琰杰
2021-06-14 16:42 ` Paul Cercueil
2021-06-16 14:57 ` Daniel Lezcano [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=f1f6562d-d871-ffeb-e058-0891d6ab4ec8@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=aric.pzqi@ingenic.com \
--cc=dongsheng.qiu@ingenic.com \
--cc=jun.jiang@ingenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=paul@opendingux.net \
--cc=rick.tyliu@ingenic.com \
--cc=sernia.zhou@foxmail.com \
--cc=sihui.liu@ingenic.com \
--cc=tglx@linutronix.de \
--cc=zhouyanjie@wanyeetech.com \
/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
all inboxes | Powered by JetHome®