linux-kernel - Re: [PATCH v7 0/6] ti: k3-am62{a,p}x-sk: add opp frequencies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240930050512.mq3hmukyzzcobbaq@lcpd911>
Date: Mon, 30 Sep 2024 10:35:12 +0530
From: Dhruva Gole <d-gole@...com>
To: Nishanth Menon <nm@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, Tero Kristo <kristo@...nel.org>,
        Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Viresh Kumar <viresh.kumar@...aro.org>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-pm@...r.kernel.org>,
        Andrew Davis
	<afd@...com>, Bryan Brattlof <bb@...com>,
        Vishal Mahaveer <vishalm@...com>, Kevin Hilman <khilman@...libre.com>,
        Markus Schneider-Pargmann
	<msp@...libre.com>
Subject: Re: [PATCH v7 0/6] ti: k3-am62{a,p}x-sk: add opp frequencies

On Sep 27, 2024 at 08:40:03 -0500, Nishanth Menon wrote:
> On 14:04-20240926, Dhruva Gole wrote:
> [...]
> 
> > Bryan Brattlof (4):
> >   arm64: dts: ti: k3-am62a: add opp frequencies
> >   arm64: dts: ti: k3-am62a7-sk: add 1.4ghz opp entry
> >   arm64: dts: ti: k3-am62p: add opp frequencies
> >   arm64: dts: ti: k3-am62p5-sk: add 1.4ghz opp entry
> > 
> > Dhruva Gole (2):
> >   arm64: dts: ti: k3-am62: use opp_efuse_table for opp-table syscon
> >   cpufreq: ti-cpufreq: Update efuse/rev offsets in AM62 family
> 
> Please drop the dt patches from the series - they are completely
> un-related. just fix the driver for compatibility and we can attack the
> am625 cpufreq support fixup separately. AM62a/62p etc are independent of
> this completely - those need to go to the DT maintainer separately

OK, will drop them out and post them later on to the TI maintainers.

> 
> am625: Just post the driver fixups for backward compatibility and get it
> merged prior to dt fixup.
> 

Got it, I'll incorporate your suggestion on the driver patch and post it
independently. Then post the DT fixups later.

Thanks for all the inputs!

-- 
Best regards,
Dhruva Gole
Texas Instruments Incorporated