[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250818-righteous-numbat-of-champagne-d5b71c@sudeepholla>
Date: Mon, 18 Aug 2025 11:26:33 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: Cristian Marussi <cristian.marussi@....com>,
Sudeep Holla <sudeep.holla@....com>, linux-kernel@...r.kernel.org,
james.quinlan@...adcom.com, "Rafael J. Wysocki" <rafael@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>, Peng Fan <peng.fan@....com>,
Mike Tipton <quic_mdtipton@...cinc.com>, arm-scmi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH] cpufreq: scmi: Add quirk to disable checks in
scmi_dev_used_by_cpus()
On Fri, Aug 15, 2025 at 09:46:22AM -0700, Florian Fainelli wrote:
[...]
> which would be more in line with checking the Device Tree only, and it would
> also allow for unmodified backports to reach the stable trees. Contrary to
> what I suggested privately however, this check is done later, so we leave a
> chance for properly formed DT to return "true" earlier on.
>
Completely agree on keeping the backports for stable simple without the
need to backport the quirk infrastructure.
> What do you think? I am now leaning more towards that solution that
> leveraging the quirks as I agree it is somewhat unrelated.
>
I am confused here. Do you prefer not to have SCMI quirk based solution
upstream forever ? Or are you OK to revert the fix and move to quirks
say in v6.18 and above ?
--
Regards,
Sudeep
Powered by blists - more mailing lists