From: "Kumar, Udit" <u-kumar1@ti.com>
To: Eric Chanudet <echanude@redhat.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, J Keerthi <j-keerthy@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Andrew Halaney <ahalaney@redhat.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j784s4-main: align watchdog clocks
Date: Tue, 27 Aug 2024 00:01:27 +0530 [thread overview]
Message-ID: <a3902df3-024d-4a0a-810a-0a9b24cfada5@ti.com> (raw)
In-Reply-To: <20240805174330.2132717-2-echanude@redhat.com>
On 8/5/2024 11:12 PM, Eric Chanudet wrote:
> assigned-clock sets DEV_RTIx_RTI_CLK(id:0) whereas clocks sets
> DEV_RTIx_RTI_CLK_PARENT_GLUELOGIC_HFOSC0_CLKOUT(id:1)[1]. This does not
> look right, the timers in the driver assume a max frequency of 32kHz for
> the heartbeat (HFOSC0 is 19.2MHz on j784s4-evm).
>
> With this change, WDIOC_GETTIMELEFT return coherent time left
> (DEFAULT_HEARTBEAT=60, reports 60s upon opening the cdev).
>
> [1] http://downloads.ti.com/tisci/esd/latest/5_soc_doc/j784s4/clocks.html#clocks-for-rti0-device
>
> Fixes: caae599de8c6 ("arm64: dts: ti: k3-j784s4-main: Add the main domain watchdog instances")
> Suggested-by: Andrew Halaney <ahalaney@redhat.com>
> Signed-off-by: Eric Chanudet <echanude@redhat.com>
> ---
> I could not get the watchdog to do more than reporting 0x32 in
> RTIWDSTATUS. Setting RTIWWDRXCTRL[0:3] to generate a reset instead of an
> interrupt (0x5) didn't trigger a reset either when the window expired.
Tested-by: Udit Kumar <u-kumar1@ti.com>
Able to reset the board
https://gist.github.com/uditkumarti/1d1b66b250949a911b008728445db9c2
> arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 38 +++++++++++-----------
> 1 file changed, 19 insertions(+), 19 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> index f170f80f00c1..6c014d335f2c 100644
> --- a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> @@ -2429,7 +2429,7 @@ main_esm: esm@700000 {
> watchdog0: watchdog@2200000 {
> compatible = "ti,j7-rti-wdt";
> reg = <0x00 0x2200000 0x00 0x100>;
> - clocks = <&k3_clks 348 1>;
> + clocks = <&k3_clks 348 0>;
> power-domains = <&k3_pds 348 TI_SCI_PD_EXCLUSIVE>;
> [...]
next prev parent reply other threads:[~2024-08-26 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 17:42 [PATCH] arm64: dts: ti: k3-j784s4-main: align watchdog clocks Eric Chanudet
2024-08-20 22:01 ` Eric Chanudet
2024-08-26 16:48 ` Andrew Halaney
2024-08-26 18:23 ` Kumar, Udit
2024-08-26 22:20 ` Eric Chanudet
2024-08-27 4:11 ` Kumar, Udit
2024-08-26 18:31 ` Kumar, Udit [this message]
2024-08-27 21:56 ` Andrew Halaney
2024-08-28 18:39 ` Nishanth Menon
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=a3902df3-024d-4a0a-810a-0a9b24cfada5@ti.com \
--to=u-kumar1@ti.com \
--cc=ahalaney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=echanude@redhat.com \
--cc=j-keerthy@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.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