From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Sergiu.Moga@microchip.com
Cc: a.zummo@towertech.it, robh+dt@kernel.org,
krzysztof.kozlowski@canonical.com, Nicolas.Ferre@microchip.com,
Claudiu.Beznea@microchip.com, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] ARM: dts: at91: Add the required `atmel,rtt-rtc-time-reg` property
Date: Fri, 4 Mar 2022 16:43:16 +0100 [thread overview]
Message-ID: <YiIzlN3GpuVTsikk@piout.net> (raw)
In-Reply-To: <8f5d56ba-1a51-f9ab-43a2-86d7c938fbe2@microchip.com>
On 04/03/2022 15:29:45+0000, Sergiu.Moga@microchip.com wrote:
> On 04.03.2022 16:53, Alexandre Belloni wrote:
> > On 04/03/2022 16:27:42+0200, Sergiu Moga wrote:
> >> Add the required `atmel,rtt-rtc-time-reg` property to the `rtt` nodes
> >> of the board files that were missing it.
> >>
> >> Signed-off-by: Sergiu Moga <sergiu.moga@microchip.com>
> >> ---
> >> arch/arm/boot/dts/at91sam9261ek.dts | 4 ++++
> >> arch/arm/boot/dts/at91sam9263ek.dts | 8 ++++++++
> >> arch/arm/boot/dts/at91sam9rlek.dts | 4 ++++
> >> 3 files changed, 16 insertions(+)
> >>
> >> diff --git a/arch/arm/boot/dts/at91sam9261ek.dts b/arch/arm/boot/dts/at91sam9261ek.dts
> >> index beed819609e8..3c1f40b4a13e 100644
> >> --- a/arch/arm/boot/dts/at91sam9261ek.dts
> >> +++ b/arch/arm/boot/dts/at91sam9261ek.dts
> >> @@ -178,6 +178,10 @@ dbgu: serial@fffff200 {
> >> status = "okay";
> >> };
> >>
> >> + rtc@fffffd20 {
> >> + atmel,rtt-rtc-time-reg = <&gpbr 0x0>;
> >> + };
> >> +
> >> watchdog@fffffd40 {
> >> status = "okay";
> >> };
> >> diff --git a/arch/arm/boot/dts/at91sam9263ek.dts b/arch/arm/boot/dts/at91sam9263ek.dts
> >> index 71f60576761a..1208bb580d14 100644
> >> --- a/arch/arm/boot/dts/at91sam9263ek.dts
> >> +++ b/arch/arm/boot/dts/at91sam9263ek.dts
> >> @@ -102,6 +102,14 @@ mtd_dataflash@0 {
> >> };
> >> };
> >>
> >> + rtc@fffffd20 {
> >> + atmel,rtt-rtc-time-reg = <&gpbr 0x0>;
> >> + };
> >> +
> >> + rtc@fffffd50 {
> >> + atmel,rtt-rtc-time-reg = <&gpbr 0x4>;
> >> + };
> > Do we really need two RTCs with the exact same features on that board?
> > Is there a check failure hen the property is not there and the node is
> > disabled?
> >
> I can understand your point here. No, it is indeed not really needed
> since, from what I can see, they are both disabled in the SoC file. The
> reason why I added both was that I thought it would have been more
> consistent. Do you think I should remove both in this file and keep the
> changes in the other 2 files only?
>
Well, I would keep the first node but not the second so that you have a
good example, ready to be enabled.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-03-04 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 14:27 [PATCH v3 0/5] dt-bindings: rtc: convert at91sam9 bindings to Sergiu Moga
2022-03-04 14:27 ` [PATCH v3 1/5] ARM: dts: at91: Add the required `atmel,rtt-rtc-time-reg` property Sergiu Moga
2022-03-04 14:53 ` Alexandre Belloni
2022-03-04 15:29 ` Sergiu.Moga
2022-03-04 15:43 ` Alexandre Belloni [this message]
2022-03-04 14:27 ` [PATCH v3 2/5] ARM: dts: at91: Use the generic "rtc" node name for the rtt IPs Sergiu Moga
2022-03-04 14:27 ` [PATCH v3 3/5] dt-bindings: rtc: convert at91sam9 bindings to json-schema Sergiu Moga
2022-03-04 14:42 ` Krzysztof Kozlowski
2022-03-04 14:27 ` [PATCH v3 4/5] dt-bindings: rtc: at91: Use macros for the IRQ type Sergiu Moga
2022-03-04 14:44 ` Krzysztof Kozlowski
2022-03-04 15:52 ` Sergiu.Moga
2022-03-04 14:27 ` [PATCH v3 5/5] dt-bindings: rtc: at91: Add SAMA7G5 compatible strings list Sergiu Moga
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=YiIzlN3GpuVTsikk@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Sergiu.Moga@microchip.com \
--cc=a.zummo@towertech.it \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).