From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
tglx@linutronix.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 0/2] clocksource: sysctr: add nxp,no-divider property
Date: Tue, 20 Sep 2022 10:45:23 +0200 [thread overview]
Message-ID: <f55faad2-737d-2ff5-1f68-14a41b1dd500@linaro.org> (raw)
In-Reply-To: <20220902111207.2902493-1-peng.fan@oss.nxp.com>
On 02/09/2022 13:12, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Legacy design used in i.MX8M* has a internal divider, but new design
> used in i.MX9* not has that divider. So add a property to indicate
> the divider exists or not.
>
> I thought to extend the binding such as nxp,imx93-sysctr-timer, and
> update driver to support i.MX93, then no need to add nxp,no-divider.
> But this means we need to extend the binding again when add new SoC,
> saying imx9[x].
>
> Not very sure which is better, so just post the NXP downstream way.
>
Applied, thanks
--
<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:[~2022-09-20 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 11:12 [PATCH 0/2] clocksource: sysctr: add nxp,no-divider property Peng Fan (OSS)
2022-09-02 11:12 ` [PATCH 1/2] dt-bindings: timer: nxp,sysctr-timer: " Peng Fan (OSS)
2022-09-08 13:11 ` Krzysztof Kozlowski
2022-09-02 11:12 ` [PATCH 2/2] clocksource/drivers/imx-sysctr: handle " Peng Fan (OSS)
2022-09-20 8:45 ` 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=f55faad2-737d-2ff5-1f68-14a41b1dd500@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).