diff options
| author | Mark Brown <broonie@kernel.org> | 2026-10-04 19:17:58 +0200 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-10-04 19:17:58 +0200 |
| commit | beed2380517a7f4f2c40df2a42afc88d08f8a4fb (patch) | |
| tree | 8bbbce44490e641b1419f504580f1411ab6b8715 /tools/perf/scripts/python/task-analyzer.py | |
| parent | 65766f75dce38103e5cbfa40eefffdc285645084 (diff) | |
| parent | 8767f4599551e9a6bc13ab2816d724b6324caff2 (diff) | |
spi: Add Nuvoton MA35D1 SPI controller support
Chi-Wen Weng <cwweng@nuvoton.com> says:
This series adds support for the SPI controller found on the Nuvoton
MA35D1 SoC.
The MA35D1 provides separate SPI and QSPI controller IPs. They expose
the same Devicetree-visible resources and provide up to two native chip
selects, so the existing MA35D1 QSPI binding is extended to also cover
the SPI controller.
The SPI driver supports host mode using polling-based PIO transfers,
SPI modes 0 through 3, 8 to 32 bits per word, LSB-first transfers, native
chip selects and GPIO chip selects. The PIO path also honors per-word
delays requested through struct spi_transfer.
The existing MA35D1 QSPI driver is updated separately to support GPIO
chip selects through the SPI core. SPI-mem operations for devices using
GPIO chip selects fall back to the regular SPI transfer path, while
native chip selects continue to use the controller's SSCTL register.
This series is based on the current broonie/spi.git for-7.4 branch and
therefore includes the already applied MA35D1 QSPI reset handling and DTR
follow-up fixes.
Link: https://patch.msgid.link/20261001131818.110028-1-cwweng.linux@gmail.com
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions
