2023-05-10 08:30:18

by Maksim Kiselev

Subject: [PATCH v5 0/5] Allwinner R329/D1/R528/T113s SPI support

v5:
- fixed DT bindings (Allowed three-string compatibility)

v4:
- fixed SPI sample mode configuration
- sorted DT bindings list

v3:
- fixed effective_speed_hz setup and added SPI sample mode configuration
- merged DT bindings for R329 and D1 SPI controllers
- added SPI_DBI node to sunxi-d1s-t113.dtsi

v2:
- added DT bindings and node for D1/T113s

Icenowy Zheng (1):
spi: sun6i: change OF match data to a struct

Icenowy Zheng (1):
spi: sun6i: change OF match data to a struct

Maksim Kiselev (4):
dt-bindings: spi: sun6i: add DT bindings for Allwinner
R329/D1/R528/T113s SPI
spi: sun6i: add quirk for in-controller clock divider
spi: sun6i: add support for R329/D1/R528/T113s SPI controllers
riscv: dts: allwinner: d1: Add SPI controllers node

.../bindings/spi/allwinner,sun6i-a31-spi.yaml | 10 ++
.../boot/dts/allwinner/sunxi-d1s-t113.dtsi | 37 +++++
drivers/spi/spi-sun6i.c | 131 ++++++++++++------
3 files changed, 138 insertions(+), 40 deletions(-)

--
2.39.2

2023-05-12 05:41:12

by Mark Brown

Subject: Re: (subset) [PATCH v5 0/5] Allwinner R329/D1/R528/T113s SPI support

On Wed, 10 May 2023 11:11:07 +0300, Maksim Kiselev wrote:
> v5:
> - fixed DT bindings (Allowed three-string compatibility)
>
> v4:
> - fixed SPI sample mode configuration
> - sorted DT bindings list
>
> [...]

Applied to

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

Thanks!

[1/5] dt-bindings: spi: sun6i: add DT bindings for Allwinner R329/D1/R528/T113s SPI
commit: f603a3f083aeb9438865975c28b27be0afaae0c1
[2/5] spi: sun6i: change OF match data to a struct
commit: b00c0d8932f1e7e36570edf0f000c64399e985e0
[3/5] spi: sun6i: add quirk for in-controller clock divider
commit: 8e886ac838ef12f6994ed9b13ab87784c4f0bc35
[4/5] spi: sun6i: add support for R329/D1/R528/T113s SPI controllers
commit: 046484cb214b43dc4463343e8c49133d9edb5454

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