mbox series

[v1,0/2] spi: gpio: Enable a single always-selected device

Message ID 20250205132127.742750-1-andriy.shevchenko@linux.intel.com
Headers show
Series spi: gpio: Enable a single always-selected device | expand

Message

Andy Shevchenko Feb. 5, 2025, 1:19 p.m. UTC 
Enable a single always-selected device hardware setup for SPI GPIO driver,
so some custom SPI bitbang code may be replaced with the generic implementation
in the future (e.g. Up Board FPGA driver).

Andy Shevchenko (2):
  spi: gpio: Remove stale documentation part
  spi: gpio: Support a single always-selected device

 drivers/spi/spi-gpio.c | 45 +++++++-----------------------------------
 1 file changed, 7 insertions(+), 38 deletions(-)

Comments

Mark Brown Feb. 6, 2025, 2:07 p.m. UTC | #1 
On Wed, 05 Feb 2025 15:19:18 +0200, Andy Shevchenko wrote:
> Enable a single always-selected device hardware setup for SPI GPIO driver,
> so some custom SPI bitbang code may be replaced with the generic implementation
> in the future (e.g. Up Board FPGA driver).
> 
> Andy Shevchenko (2):
>   spi: gpio: Remove stale documentation part
>   spi: gpio: Support a single always-selected device
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: gpio: Remove stale documentation part
      commit: c108905a7423d44237d17374f845fc5bb9cb9728
[2/2] spi: gpio: Support a single always-selected device
      commit: 25fac20edd09b60651eabcc57c187b1277f43d08

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