linux-kernel - Re: [PATCH] arm64: dts: ti: k3-am62x-sk-common: Add bootph-all for I2C1 instance pinmux

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: <171898028156.2272421.18249578267583148135.b4-ty@ti.com>
Date: Fri, 21 Jun 2024 20:54:14 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <conor+dt@...nel.org>, <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        Devarsh Thakkar
	<devarsht@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <praneeth@...com>,
        <a-bhatia1@...com>, <j-luthra@...com>, <d-gole@...com>, <bb@...com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62x-sk-common: Add bootph-all for I2C1 instance pinmux

Hi Devarsh Thakkar,

On Fri, 14 Jun 2024 18:05:32 +0530, Devarsh Thakkar wrote:
> I2C1 controller controls io-expander which provides power to voltage
> regulator vdd_mmc1 for MMC SD using a gpio line.
> 
> Add bootph-all to the pinmux node for this instance, as this is used during
> SPL stage too by the bootloader while using SD boot mode as without this
> the SD boot mode fails with below error when using this device-tree in
> u-boot:
> 
> [...]

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

[1/1] arm64: dts: ti: k3-am62x-sk-common: Add bootph-all for I2C1 instance pinmux
      commit: 175133a32b48a092363828ce3041a0adaab01ffc

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