[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250821-thundering-skylark-of-proficiency-a17ddd@sudeepholla>
Date: Thu, 21 Aug 2025 11:17:34 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Dan Carpenter <dan.carpenter@...aro.org>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Sudeep Holla <sudeep.holla@....com>,
open list <linux-kernel@...r.kernel.org>,
linux-clk <linux-clk@...r.kernel.org>, lkft-triage@...ts.linaro.org,
Linux Regressions <regressions@...ts.linux.dev>,
Anna-Maria Behnsen <anna-maria@...utronix.de>,
Frederic Weisbecker <frederic@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Liviu Dudau <liviu.dudau@....com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Mark Rutland <mark.rutland@....com>, Arnd Bergmann <arnd@...db.de>,
Anders Roxell <anders.roxell@...aro.org>
Subject: Re: Juno-r2 WARNING kernel time clockevents.c cev_delta2ns
clockevents_config.part
On Wed, Aug 20, 2025 at 05:24:14PM +0300, Dan Carpenter wrote:
> Hi Sudeep,
>
> Could we revert commit 1fa3ed04ac55 ("arm64: dts: arm: Drop the
> clock-frequency property from timer nodes")? We're still getting this
> warning on our Juno systems (with admittedly ancient firmware).
>
It was dropped to avoid further copy-paste into newer platforms that
need to get these right in the firmware. I am afraid keep it would just
not help and any strong reasons for not moving to newer firmware. It should
be really ancient one with no security fixes I guess. I strong prefer to
move to slightly newer firmware version if not the latest.
--
Regards,
Sudeep
Powered by blists - more mailing lists