From: Zhou Furong <furong.zhou@linux.intel.com>
To: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>,
daniel.lezcano@linaro.org, tglx@linutronix.de,
robh+dt@kernel.org, krzk+dt@kernel.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
dongsheng.qiu@ingenic.com, aric.pzqi@ingenic.com,
rick.tyliu@ingenic.com, sernia.zhou@foxmail.com,
zhenwenjin@gmail.com, reimu@sudomaker.com
Subject: Re: [PATCH v4 0/3] Add SMP/SMT support for Ingenic sysost driver.
Date: Tue, 12 Apr 2022 08:23:41 +0800 [thread overview]
Message-ID: <0957e2ef-2483-375d-e2bf-6dae4fa2e6b3@linux.intel.com> (raw)
In-Reply-To: <1649687597-74219-1-git-send-email-zhouyanjie@wanyeetech.com>
Hi,
On 2022/4/11 22:33, 周琰杰 (Zhou Yanjie) wrote:
> 1.On the hardware of X2000 SoC, the OST has been split into
> two parts, two 32bit timers for clockevent and one 64bit
> timer for clocksource (with different addresses), so it
> not appropriate to use only one "ingenic,x2000-ost", just
> remove it, then introduce "ingenic,x2000-ost32" and
> "ingenic,x2000-ost64".
> 2.The OST in Ingenic XBurst®2 SoCs has a global timer and
> up to 16 event timers, add support for the event timers.
> 3.Add dt-bindings and compatible strings for the X1600 SoC,
> the X1700 SoC, the X1830 SoC, the X2000 SoC, the X2500 SoC.
>
> 周琰杰 (Zhou Yanjie) (3):
Please consider config your git, Non-english characters may not always
display correctly.
Best regards,
Furong
prev parent reply other threads:[~2022-04-12 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 14:33 [PATCH v4 0/3] Add SMP/SMT support for Ingenic sysost driver 周琰杰 (Zhou Yanjie)
2022-04-11 14:33 ` [PATCH v4 1/3] dt-bindings: timer: Remove unreasonable binding 周琰杰 (Zhou Yanjie)
2022-04-11 14:33 ` [PATCH v4 2/3] dt-bindings: timer: Add bindings for new Ingenic SoCs 周琰杰 (Zhou Yanjie)
2022-04-11 14:33 ` [PATCH v4 3/3] clocksource: Ingenic: Add SMP/SMT support for sysost driver 周琰杰 (Zhou Yanjie)
2022-04-11 23:08 ` kernel test robot
2022-04-12 0:23 ` Zhou Furong [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=0957e2ef-2483-375d-e2bf-6dae4fa2e6b3@linux.intel.com \
--to=furong.zhou@linux.intel.com \
--cc=aric.pzqi@ingenic.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.qiu@ingenic.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reimu@sudomaker.com \
--cc=rick.tyliu@ingenic.com \
--cc=robh+dt@kernel.org \
--cc=sernia.zhou@foxmail.com \
--cc=tglx@linutronix.de \
--cc=zhenwenjin@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).