[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <843ca735-d911-d514-60be-795c71a4e291@microchip.com>
Date: Tue, 14 Apr 2020 13:59:50 +0000
From: <Claudiu.Beznea@...rochip.com>
To: <alexandre.belloni@...tlin.com>
CC: <mark.rutland@....com>, <a.zummo@...ertech.it>,
<jason@...edaemon.net>, <devicetree@...r.kernel.org>,
<maz@...nel.org>, <linux-kernel@...r.kernel.org>,
<Ludovic.Desroches@...rochip.com>, <robh+dt@...nel.org>,
<tglx@...utronix.de>, <linux-arm-kernel@...ts.infradead.org>,
<linux-rtc@...r.kernel.org>
Subject: Re: [PATCH 4/5] ARM: dts: sam9x60: add rtt
On 14.04.2020 16:12, Alexandre Belloni wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> 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.
I was talking about mixing these:
+&gpbr {
+ status = "okay";
+};
+
+&rtt {
+ atmel,rtt-rtc-time-reg = <&gpbr 0x0>;
+ status = "okay";
+};
+
>
>
> --
> Alexandre Belloni, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
Powered by blists - more mailing lists