From: Dhruva Gole <d-gole@ti.com>
To: Nishanth Menon <nm@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Julien Panis <jpanis@baylibre.com>, <bb@ti.com>
Subject: Re: [PATCH V3 1/2] arm64: dts: ti: k3-am62-wakeup: Introduce RTC node
Date: Tue, 21 Mar 2023 10:07:13 +0530 [thread overview]
Message-ID: <4a1f33bb-882a-ed49-9e0e-b463203e0ea9@ti.com> (raw)
In-Reply-To: <20230320165123.80561-2-nm@ti.com>
Hi,
On 20/03/23 22:21, Nishanth Menon wrote:
> Introduce digital RTC node in wakeup domain. Even though this has
> no specific battery backup supply, this on-chip RTC is used in
> cost-optimized board designs as a wakeup source.
>
> Reviewed-by: Dhruva Gole <d-gole@ti.com>
> Reviewed-by: Bryan Brattlof <bb@ti.com>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> Changes since v2:
> - Just reviewed-by pickups
>
> V2: https://lore.kernel.org/all/20230315170706.1598977-2-nm@ti.com/
> V1: https://lore.kernel.org/all/20230311105850.21811-2-nm@ti.com/
>
> arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
> index 38dced6b4fef..fec81546fbbd 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
> @@ -40,4 +40,14 @@ wkup_i2c0: i2c@2b200000 {
> clock-names = "fck";
> status = "disabled";
> };
> +
> + wkup_rtc0: rtc@2b1f0000 {
> + compatible = "ti,am62-rtc";
> + reg = <0x00 0x2b1f0000 0x00 0x100>;
> + interrupts = <GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&k3_clks 117 6> , <&k3_clks 117 0>;
> + clock-names = "vbus", "osc32k";
> + power-domains = <&k3_pds 117 TI_SCI_PD_EXCLUSIVE>;
> + wakeup-source;
> + };
> };
I was just wondering why some of the rtctests show failures on this platform:
https://gist.github.com/DhruvaG2000/5c6d8bb99b087308b916985d70f0c440
pass:5 fail:2
the test is compiled from tools/testing/selftests/rtc/rtctest.c for arm64 target
Is this expected?
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-21 4:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 16:51 [PATCH V3 0/2] arm64: dts: ti: k3-am62: Add watchdog and rtc nodes Nishanth Menon
2023-03-20 16:51 ` [PATCH V3 1/2] arm64: dts: ti: k3-am62-wakeup: Introduce RTC node Nishanth Menon
2023-03-21 4:37 ` Dhruva Gole [this message]
2023-03-21 12:59 ` Nishanth Menon
2023-03-20 16:51 ` [PATCH V3 2/2] arm64: dts: ti: k3-am62: Add watchdog nodes Nishanth Menon
2023-03-20 22:58 ` [PATCH V3 0/2] arm64: dts: ti: k3-am62: Add watchdog and rtc nodes 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=4a1f33bb-882a-ed49-9e0e-b463203e0ea9@ti.com \
--to=d-gole@ti.com \
--cc=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jpanis@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@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