[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200414131255.GK34509@piout.net>
Date: Tue, 14 Apr 2020 15:12:55 +0200
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: Claudiu.Beznea@...rochip.com
Cc: a.zummo@...ertech.it, robh+dt@...nel.org, mark.rutland@....com,
Nicolas.Ferre@...rochip.com, Ludovic.Desroches@...rochip.com,
tglx@...utronix.de, jason@...edaemon.net, maz@...nel.org,
linux-rtc@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/5] ARM: dts: sam9x60: add rtt
On 14/04/2020 13:05:03+0000, Claudiu.Beznea@...rochip.com wrote:
> >>> But this is very unlikely to happen because this would be limited to a
> >>> single board device tree instead of impact every sam9x60 based boards.
> >>
> >> Very unlikely but a having a patch with diff like this:
> >>
> >> +&gpbr {
> >> + status = "okay";
> >> +};
> >> +
> >> +&rtt {
> >> + atmel,rtt-rtc-time-reg = <&gpbr 0x0>;
> >> + status = "okay";
> >> +};
> >> +
> >>
> >> and reverting it may affect the other users of gpbr in sam9x60ek.dts.
> >>
> >
> > Again, this affects only sam9x60ek.dts instead of possibly multiple DTs
> > that may be out of tree. So the risk of doing that is null.
>
> Anyway... I'll merge it although I don't consider is the right way.
>
Do as you wish but a board DT change mixed with a dtsi is a no go.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Powered by blists - more mailing lists