[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4f4766a2-5c94-40bf-9016-2e5412796c1a@mleia.com>
Date: Thu, 11 Sep 2025 03:19:24 +0300
From: Vladimir Zapolskiy <vz@...ia.com>
To: Javier Carrasco <javier.carrasco.cruz@...il.com>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Piotr Wojtaszczyk <piotr.wojtaszczyk@...esys.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND] arm: dts: nxp: lpc: lpc32xx: drop 'clocks' form
rtc
Hi Javier.
On 10/16/24 20:14, Javier Carrasco wrote:
> The RTC does not provide a controllable clock signal (it uses a fixed
> 32768 Hz crystal, the input clock of the SoC). Remove the 'clocks'
> property to better describe the device and avoid errors when checking
> the dts against the nxp,lpc3220-rtc binding.
>
This dts change as well as a counterpart documentation change won't be
applied, since it breaks dtb/Linux ABI, unfortunately.
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@...il.com>
> ---
> This patch used to belong to a series that converted the affected RTC
> into dtschema[1] (effectively moving it to trivial-rtc), and dropped
> the signal clock as it uses a fixed 32768 Hz crystal.
>
> The rest of that series was merged, but I did not get any feedback for
> this one. I sent a little reminder ~2 months later that might have gone
> unnoticed too, and as a few more months passed since then, I opted for a
> resend with the single pending patch. It is of course not urgent, but
> still relevant.
>
> Link: https://lore.kernel.org/all/20240413-rtc_dtschema-v3-0-eff368bcc471@gmail.com/ [1]
--
Best wishes,
Vladimir
Powered by blists - more mailing lists