Received-SPF: pass (google.com: domain of linux-kernel+bounces-35250-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Mark Brown <broonie@kernel.org>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, git@amd.com
In-Reply-To: <20231218090652.18403-1-amit.kumar-mahapatra@amd.com>
References: <20231218090652.18403-1-amit.kumar-mahapatra@amd.com>
Subject: Re: [PATCH] spi: spi-cadence: Reverse the order of interleaved
 write and read operations
Message-Id: <170601312400.19682.11415116408445396292.b4-ty@kernel.org>
Date: Tue, 23 Jan 2024 12:32:04 +0000
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Mon, 18 Dec 2023 14:36:52 +0530, Amit Kumar Mahapatra wrote:
> In the existing implementation, when executing interleaved write and read
> operations in the ISR for a transfer length greater than the FIFO size,
> the TXFIFO write precedes the RXFIFO read. Consequently, the initially
> received data in the RXFIFO is pushed out and lost, leading to a failure
> in data integrity. To address this issue, reverse the order of interleaved
> operations and conduct the RXFIFO read followed by the TXFIFO write.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: spi-cadence: Reverse the order of interleaved write and read operations
      commit: 8715c23b6540d142b955efe64f91b8bc2d3cf623

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a 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.

Thanks,
Mark