Received-SPF: pass (google.com: domain of linux-kernel+bounces-66551-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
        Rob Herring
	<robh+dt@kernel.org>,
        Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        Francesco Dolcini <francesco@dolcini.it>
CC: Vignesh Raghavendra <vigneshr@ti.com>,
        Francesco Dolcini
	<francesco.dolcini@toradex.com>,
        <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] arm64: dts: ti: verdin-am62: Set VDD CORE minimum voltage to 0.75V
Date: Thu, 15 Feb 2024 15:02:10 +0530
Message-ID: <170798813445.1487216.11059927145774998794.b4-ty@ti.com>
In-Reply-To: <20240213155622.18309-1-francesco@dolcini.it>
References: <20240213155622.18309-1-francesco@dolcini.it>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi Francesco Dolcini,

On Tue, 13 Feb 2024 16:56:22 +0100, Francesco Dolcini wrote:
> Set VDD_CORE minimum voltage to 0.75V, TI AM62 can run at either 0.75V
> or 0.85V depending on the actual speed grade and on the maximum
> configured speed (1.4GHz frequency requires 0.85V).
> 
> The actual value is programmed into the PMIC EEPROM during manufacturing
> (according to the SOC speed grade) and this ensure that both the voltage
> values are valid and therefore the OS will not overwrite the value
> programmed into the PMIC.
> 
> [...]

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

[1/1] arm64: dts: ti: verdin-am62: Set VDD CORE minimum voltage to 0.75V
      commit: 2af8358ad64fb4bf012a6dc2917fbfc78a2093b2

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