From: Conor Dooley <conor.dooley@microchip.com>

Hey Mark,

v3 with the review comment about the core handing CS_HIGH dealt with.
I noticed that in the same function there was a "raw" BIT(1), which I
replaced with a macro that the patch was already adding for use in the
setup function...

Cheers,
Conor.

CC: Conor Dooley <conor.dooley@microchip.com>
CC: Daire McNamara <daire.mcnamara@microchip.com>
CC: Mark Brown <broonie@kernel.org>
CC: Cyril Jean <cyril.jean@microchip.com>
CC: Valentina.FernandezAlanis@microchip.com
CC: linux-riscv@lists.infradead.org
CC: linux-spi@vger.kernel.org
CC: linux-kernel@vger.kernel.org

Conor Dooley (3):
  spi: microchip-core-qspi: control built-in cs manually
  spi: microchip-core-qspi: don't attempt to transmit during emulated
    read-only dual/quad operations
  spi: microchip-core-qspi: remove some inline markings

 drivers/spi/spi-microchip-core-qspi.c | 99 +++++++++++++++++++++------
 1 file changed, 79 insertions(+), 20 deletions(-)

-- 
2.53.0

On Thu, 30 Apr 2026 11:10:17 +0100, Conor Dooley wrote:
> microchip core-qspi gpio-cs fixes + cleanup
> 
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> Hey Mark,
> 
> v3 with the review comment about the core handing CS_HIGH dealt with.
> I noticed that in the same function there was a "raw" BIT(1), which I
> replaced with a macro that the patch was already adding for use in the
> setup function...
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: microchip-core-qspi: control built-in cs manually
      https://git.kernel.org/broonie/spi/c/7672749e1496
[2/3] spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations
      https://git.kernel.org/broonie/spi/c/eb56deaabf12
[3/3] spi: microchip-core-qspi: remove some inline markings
      https://git.kernel.org/broonie/spi/c/0b2eb1f8473e

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