[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <177024312540.380254.1461688590164454858.b4-ty@kernel.org>
Date: Wed, 04 Feb 2026 22:12:05 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-arm-msm@...r.kernel.org, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org, bjorn.andersson@....qualcomm.com,
dmitry.baryshkov@....qualcomm.com, konrad.dybcio@....qualcomm.com,
Praveen Talari <praveen.talari@....qualcomm.com>
Cc: prasad.sodagudi@....qualcomm.com, mukesh.savaliya@....qualcomm.com,
quic_vtanuku@...cinc.com, aniket.randive@....qualcomm.com,
chandana.chiluveru@....qualcomm.com, jyothi.seerapu@....qualcomm.com
Subject: Re: [PATCH v2 0/4] Improve SPI target mode support and error
handling
On Wed, 04 Feb 2026 21:58:50 +0530, Praveen Talari wrote:
> Enhance the Qualcomm GENI SPI driver's target mode support and improve
> error handling for serial engine operations.
>
> The current implementation has issues with incorrect controller allocation
> for target mode, missing abort sequence execution during error recovery,
> and lack of graceful abort mechanism for target operations. These problems
> can lead to serial engine undefined behavior and improper resource
> cleanup.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/4] spi: geni-qcom: Improve target mode allocation by using proper allocation functions
commit: 50464497b5874b7c2f3ab991cec81e916d40743c
[2/4] spi: geni-qcom: Fix abort sequence execution for serial engine errors
commit: 96e041647bb0f9d92f95df1d69cb7442d7408b79
[3/4] spi: qcom-geni: Drop unused msg parameter from timeout handlers
commit: 9934383f98c91d8dfdf16d0e980431041c2d17ee
[4/4] spi: geni-qcom: Add target abort support
commit: 6516169fa7f6110ce42a5958c921255f2d0968bc
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
Powered by blists - more mailing lists