[PATCH v5 0/3] support for amlogic the new SPI IP

Xianwei Zhao via B4 Relay posted 3 patches 2 months, 2 weeks ago
.../devicetree/bindings/spi/amlogic,a4-spisg.yaml  |  59 ++
MAINTAINERS                                        |   9 +
drivers/spi/Kconfig                                |   9 +
drivers/spi/Makefile                               |   1 +
drivers/spi/spi-amlogic-spisg.c                    | 888 +++++++++++++++++++++
5 files changed, 966 insertions(+)
[PATCH v5 0/3] support for amlogic the new SPI IP
Posted by Xianwei Zhao via B4 Relay 2 months, 2 weeks ago
Introduced support for the new SPI IP (SPISG). The SPISG is
a communication-oriented SPI controller from Amlogic,supporting
three operation modes: PIO, block DMA, and scatter-gather DMA.

Add the drivers and device tree bindings corresponding to the SPISG.

Signed-off-by: Xianwei Zhao <xianwei.zhao@amlogic.com>
---
Changes in v5:
- The location for interrupting registration has been adjusted.
- Unexpected interrupt return IRQ_NONE.
- Modify div clk register and process reset_dev return value.
- Link to v4: https://lore.kernel.org/r/20250704-spisg-v4-0-6b731dfbe610@amlogic.com

Changes in v4:
- Add resets prop and modify some formats for bindings.
- Remove irrelevant headers files and fix some issues.
- Link to v3: https://lore.kernel.org/r/20250623-spisg-v3-0-c731f57e289c@amlogic.com

Changes in v3:
- Rename of bit definition and fix some issues.
- Enable runtime_suspend function.
- Link to v2: https://lore.kernel.org/r/20250617-spisg-v2-0-51a605a84bd5@amlogic.com

Changes in v2:
- Use regmap to operation register and drop bitfied define.
- Use "SPISG" prefix intead of "SPICC", and declare clock div table in the spisg_device. 
- Delete other power operation functions except for runtime_supspend and runtime_resume.
- Fix some format corrections.
- Link to v1: https://lore.kernel.org/r/20250604-spisg-v1-0-5893dbe9d953@amlogic.com

---
Sunny Luo (2):
      spi: dt-bindings: Add binding document of Amlogic SPISG controller
      spi: Add Amlogic SPISG driver

Xianwei Zhao (1):
      MAINTAINERS: Add an entry for Amlogic spi driver

 .../devicetree/bindings/spi/amlogic,a4-spisg.yaml  |  59 ++
 MAINTAINERS                                        |   9 +
 drivers/spi/Kconfig                                |   9 +
 drivers/spi/Makefile                               |   1 +
 drivers/spi/spi-amlogic-spisg.c                    | 888 +++++++++++++++++++++
 5 files changed, 966 insertions(+)
---
base-commit: bd30b995df8fd053e13d10f78dbc7b2fa5ed1aae
change-id: 20250603-spisg-78f21682ebac

Best regards,
-- 
Xianwei Zhao <xianwei.zhao@amlogic.com>
Re: [PATCH v5 0/3] support for amlogic the new SPI IP
Posted by Mark Brown 2 months, 1 week ago
On Fri, 18 Jul 2025 09:52:15 +0800, Xianwei Zhao wrote:
> Introduced support for the new SPI IP (SPISG). The SPISG is
> a communication-oriented SPI controller from Amlogic,supporting
> three operation modes: PIO, block DMA, and scatter-gather DMA.
> 
> Add the drivers and device tree bindings corresponding to the SPISG.
> 
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: dt-bindings: Add binding document of Amlogic SPISG controller
      commit: 78d35a20783941c8ba5cf912349728c6e1bee84b
[2/3] spi: Add Amlogic SPISG driver
      commit: cef9991e04aed3305c61c392e880f6e01a0c2ea4
[3/3] MAINTAINERS: Add an entry for Amlogic spi driver
      commit: 0ef2a9779e9decee52a85bc393309b3e068a74a6

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