linux-kernel - Re: [PATCH v2 0/2] Reconfigure 1.4GHz in AM62 PHYCORE SoM

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: <173012710988.558239.17362858553590828268.b4-ty@ti.com>
Date: Mon, 28 Oct 2024 20:35:23 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <w.egorov@...tec.de>, Garrett Giordano <ggiordano@...tec.com>
CC: Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <upstream@...ts.phytec.de>
Subject: Re: [PATCH v2 0/2] Reconfigure 1.4GHz in AM62 PHYCORE SoM

Hi Garrett Giordano,

On Tue, 01 Oct 2024 00:19:14 -0700, Garrett Giordano wrote:
> This patch set moves our 1.4GHz opp table definition out of our overlay
> and into our som dtsi. This change goes along with our updated PMIC, which
> is now configured to output 0.85v by default.
> 
> We drop the overlay as it is no longer needed.
> 
> Changes in v2:
>   - Use git revert to revert the overlay patch
>   - Update commit message to reflect revert adding the device tree overlay
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/2] arm64: dts: ti: am62-phycore-som: Increase cpu frequency to 1.4 GHz
      commit: bc3552d675537be111148d9614f4f02f31e30de3
[2/2] Revert "arm64: dts: ti: am62-phyboard-lyra: Add overlay to increase cpu frequency to 1.4 GHz"
      commit: 151ed40a4f204e8786a2573e3f8083ffd29f3b1e

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh