From: Romain Perier <romain.perier@gmail.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
DTML <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/6] clocksource: msc313e: Add support for ssd20xd-based platforms
Date: Thu, 16 Dec 2021 19:18:28 +0100 [thread overview]
Message-ID: <CABgxDoLtD6fAj-c_+gcjJBoe9HLQYxrhSZZdjEC0YJqDssP6SA@mail.gmail.com> (raw)
In-Reply-To: <CAFr9PXki8LVdjQC_4eDSuB1dmEmv2K00bWOy92cOXENEoEyeqw@mail.gmail.com>
Hi Daniel,
What do you think about the following description ? : "
clocksource: msc313e: Add support for ssd20xd-based platforms
On SSD20X family SoCs bootrom sets the divider for timer0 to run at
12Mhz, while timer1 and timer2 are kept unchanged and defaut to ~432Mhz.
There are no ways to reduce or divide these clocks in the clktree.
However, These SoCs provide an internal "timer_divide" register that can
act on this input clock. This commit adds support for this register,
as timer1 and timer2 are used as clockevents these will run at 48Mhz.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
"
Romain
Le mer. 15 déc. 2021 à 13:00, Daniel Palmer <daniel@0x0f.com> a écrit :
>
> Hi Romain,
>
> On Mon, 13 Dec 2021 at 03:19, Romain Perier <romain.perier@gmail.com> wrote:
> >
> > SSD20X family SoCs have an oscillator running at ~432Mhz for timer1 and
> > timer2, while timer0 is running at 12Mhz.
>
> I don't think this is technically true. I think the boot rom sets the
> divider for timer0 so that it runs at ~12MHz.
> I think the current change to only configure timer1 and timer2 is ok
> but maybe the commit message should say that timer0 is configured to
> be backwards compatible at boot.
>
> Cheers,
>
> Daniel
next prev parent reply other threads:[~2021-12-16 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 18:19 [PATCH v2 0/6] Add timers for Mstar SoCs Romain Perier
2021-12-12 18:19 ` [PATCH v2 1/6] clocksource: Add MStar MSC313e timer support Romain Perier
2021-12-12 18:19 ` [PATCH v2 2/6] clocksource: msc313e: Add support for ssd20xd-based platforms Romain Perier
2021-12-15 12:00 ` Daniel Palmer
2021-12-16 18:18 ` Romain Perier [this message]
2021-12-17 9:00 ` Daniel Palmer
2021-12-12 18:19 ` [PATCH v2 3/6] ARM: mstar: Select MSC313E_TIMER Romain Perier
2021-12-12 18:19 ` [PATCH v2 4/6] dt-bindings: timer: Add Mstar MSC313e timer devicetree bindings documentation Romain Perier
2021-12-15 20:08 ` Rob Herring
2021-12-12 18:19 ` [PATCH v2 5/6] ARM: dts: mstar: Add timers device nodes Romain Perier
2021-12-12 18:19 ` [PATCH v2 6/6] ARM: dts: mstar: Switch to compatible "sstar,ssd20xd-timer" on infinity2m Romain Perier
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=CABgxDoLtD6fAj-c_+gcjJBoe9HLQYxrhSZZdjEC0YJqDssP6SA@mail.gmail.com \
--to=romain.perier@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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).