Received-SPF: pass (google.com: domain of linux-kernel+bounces-72305-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>, Judith Mendez <jm@ti.com>
CC: Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
        Tero
 Kristo <kristo@kernel.org>,
        <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>, Wadim Egorov
	<w.egorov@phytec.de>,
        Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v3 0/9] Fix MMC properties on Sitara K3 devices
Date: Tue, 20 Feb 2024 09:33:17 +0530
Message-ID: <170834878955.3471454.11267750873554490606.b4-ty@ti.com>
In-Reply-To: <20240213235701.2438513-1-jm@ti.com>
References: <20240213235701.2438513-1-jm@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi Judith Mendez,

On Tue, 13 Feb 2024 17:56:52 -0600, Judith Mendez wrote:
> This patch series aims to fix and update MMC nodes for TI
> Sitara K3 devices with the following changes.
> 
> The series introduces sdhci0 and sdhci2 nodes and enables
> eMMC for AM62ax platform.
> 
> Also introduce fixes for MMC ITAP/OTAP values for AM64x
> platform according to device datasheet [0], and add ITAP/
> OTAP values for AM62p to enable the highest timing possible
> for MMC0 and MMC1, according to device datasheet [1].
> 
> [...]

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

[1/9] arm64: dts: ti: k3-am62a-main: Add sdhci0 instance
      commit: d3ae4e8d8b6ac0db82264c5576daa260cac3d536
[2/9] arm64: dts: ti: k3-am62a-main: Add sdhci2 instance
      commit: feb5d68cec77b6783f4febb8c91c1b1caa8b4924
[3/9] arm64: dts: ti: k3-am62a7-sk: Enable eMMC support
      commit: e041ec6e86e7dbc49f5245ace6f3b965bb7c26f7
[4/9] arm64: dts: ti: k3-am64-main: Fix ITAP/OTAP values for MMC
      commit: 379c7752bbd0e81654544a896dd19c19ebb6faba
[5/9] arm64: dts: ti: k3-am62p: Add ITAP/OTAP values for MMC
      commit: 37f28165518f7df2ed085e4481dade9c262b593b
[6/9] arm64: dts: ti: k3-am6*: Remove DLL properties for soft PHYs
      commit: eea929f0e0e3f83d2c027b1e60630deb50df4494
[7/9] arm64: dts: ti: k3-am6*: Fix ti,clkbuf-sel property in MMC nodes
      commit: 2812d23ade3d614b451bff5d63d29a31b92d8859
[8/9] arm64: dts: ti: k3-am6*: Fix bus-width property in MMC nodes
      commit: 0ae3113a46a64266f19fdc9753d5e3a6748fc594
[9/9] arm64: dts: ti: k3-am6*: Add bootph-all property in MMC node
      commit: 5f0e6ce354f61092182b79d177585bd7310f12a2

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