From: Kendall Willis <k-willis@ti.com>
To: Dhruva Gole <d-gole@ti.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<msp@baylibre.com>, <khilman@baylibre.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62a7-sk: Add alias for RTC
Date: Fri, 14 Feb 2025 16:37:03 -0600 [thread overview]
Message-ID: <b3e96184-e20c-4935-b86c-73c95b00b9fc@ti.com> (raw)
In-Reply-To: <20250214062141.gdmkepuuyqb22xuh@lcpd911>
On 2/14/25 00:21, Dhruva Gole wrote:
> On Feb 12, 2025 at 15:06:04 -0600, Kendall Willis wrote:
>> From: Vibhore Vardhan <vibhore@ti.com>
>>
>> Adds alias for SoC RTC so that it gets assigned rtc0. PMIC node is
>> assisgned rtc1 so that PMIC RTC gets probed as rtc1. This makes it
>
> Nit: Fix the spelling of assigned please.
>
>> consistent for testing rtcwake with other AM62 devices where rtc0
>> is SoC RTC.
>>
>> Signed-off-by: Vibhore Vardhan <vibhore@ti.com>
>> [k-willis@ti.com: Reworded commit message]
>> Signed-off-by: Kendall Willis <k-willis@ti.com>
>> ---
>> Tested with rtcwake on AM62A.
>
> Any test logs you can provide would be great!
>
>>
>> Original patch for AM62A existed in the TI Vendor tree with Vibhore's
>> authorship:
>> https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-6.6.y&id=f745d9063212d1088dcfb068ecb4b16648b96487
>> ---
>> arch/arm64/boot/dts/ti/k3-am62a7-sk.dts | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts b/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
>> index a6f0d87a50d8..51ea961f166e 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
>> +++ b/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
>> @@ -22,6 +22,8 @@ aliases {
>> serial3 = &main_uart1;
>> mmc0 = &sdhci0;
>> mmc1 = &sdhci1;
>> + rtc0 = &wkup_rtc0;
>> + rtc1 = &tps659312;
>> };
>>
>> chosen {
>>
>> base-commit: 2014c95afecee3e76ca4a56956a936e23283f05b
>
> It's nice that you've mentioned this, but it seems to be from Feb2.
> Can you please base it on latest linux-next when you send in future?
> This will avoid any merge conflicts in advance.
>
> For this though, you may get away with it because nobody else may have
> touched this file so far...
>
> If you do send a v2, feel free to pick:
> Reviewed-by: Dhruva Gole <d-gole@ti.com>
>
Hi Dhruva,
Thanks for the feedback and the review. I will be adding the changes
mentioned by you in v2 :)
Best,
Kendall Willis
prev parent reply other threads:[~2025-02-14 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 21:06 Kendall Willis
2025-02-14 6:21 ` Dhruva Gole
2025-02-14 22:37 ` Kendall Willis [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=b3e96184-e20c-4935-b86c-73c95b00b9fc@ti.com \
--to=k-willis@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--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
all inboxes | Powered by JetHome®