From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>,
wim@linux-watchdog.org
Cc: linux@roeck-us.net, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org, S32@nxp.com,
ghennadi.procopciuc@nxp.com, thomas.fossati@linaro.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: watchdog: Add NXP Software Watchdog Timer
Date: Thu, 3 Apr 2025 17:10:10 +0200 [thread overview]
Message-ID: <c570c99d-53f5-4f77-a730-42e5a2016dc5@linaro.org> (raw)
In-Reply-To: <64b6d599-fe67-586a-e4b0-73d9b73499de@oss.nxp.com>
On 03/04/2025 08:19, Ghennadi Procopciuc wrote:
> On 4/2/2025 6:49 PM, Daniel Lezcano wrote:
> [ ... ]
>> +examples:
>> + - |
>> + watchdog@0x40100000 {
>> + compatible = "nxp,s32g2-swt";
>> + reg = <0x40100000 0x1000>;
>> + clocks = <&clks 0x3a>;
>> + timeout-sec = <10>;
>> + };
>
> The S32G reference manual specifies two clocks for the SWT module: one
> for the registers and another for the counter itself. Shouldn't both
> clocks be represented in the bindings?
AFAICS, there are two clocks as described in the documentation for the
s32g2 page 846, section 23.7.3.3 SWT clocking.
The module and the register clock are fed by the XBAR_DIV3_CLK which is
an system clock always-on.
The counter is fed by the FIRC_CLK which described as "FIRC_CLK is the
default clock for the entire system at power-up."
From my understanding, we should not describe the XBAR_DIV3_CLK as it
is a system clock.
And the FIRC_CLK is only there to get the clock rate in the driver.
--
<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
next prev parent reply other threads:[~2025-04-03 15:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 15:49 [PATCH v2 0/2] Add the NXP S32 Watchdog Daniel Lezcano
2025-04-02 15:49 ` [PATCH v2 1/2] dt-bindings: watchdog: Add NXP Software Watchdog Timer Daniel Lezcano
2025-04-02 15:56 ` Krzysztof Kozlowski
2025-04-02 23:01 ` Daniel Lezcano
2025-04-03 14:16 ` Krzysztof Kozlowski
2025-04-03 15:33 ` Daniel Lezcano
2025-04-03 15:35 ` Krzysztof Kozlowski
2025-04-03 21:52 ` Daniel Lezcano
2025-04-02 18:56 ` Rob Herring (Arm)
2025-04-03 6:19 ` Ghennadi Procopciuc
2025-04-03 15:10 ` Daniel Lezcano [this message]
2025-04-04 6:35 ` Ghennadi Procopciuc
2025-04-06 20:33 ` Daniel Lezcano
2025-04-07 4:53 ` Ghennadi Procopciuc
2025-04-02 15:49 ` [PATCH v2 2/2] watchdog: Add the Watchdog Timer for the NXP S32 platform Daniel Lezcano
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=c570c99d-53f5-4f77-a730-42e5a2016dc5@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=S32@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ghennadi.procopciuc@nxp.com \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=thomas.fossati@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=wim@linux-watchdog.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