v5:
- Changed SoC compatible to list exact models
v4:
- Added SoC series-specific compatible matches.
v3:
- Added cpu_relax() to busy loop.
- Dropped .remove callback from driver struct.
- Use (variations of) realtek-rtl as prefix.
- Dropped Kconfig entry, and use MACH_REALTEK_RTL setting to build the
driver, since there's no point booting without the SPI-connected flash.
v2:
- Rewrote from spi-nor driver to regular spi driver, implementing only
set_cs() and transfer_one(). (Thanks Chuanhong Guo!)
Bert Vermeulen (2):
dt-bindings: spi: Realtek RTL838x/RTL839x SPI controller
spi: realtek-rtl: Add support for Realtek RTL838x/RTL839x SPI
controllers
.../bindings/spi/realtek,rtl-spi.yaml | 41 ++++
drivers/spi/Makefile | 1 +
drivers/spi/spi-realtek-rtl.c | 209 ++++++++++++++++++
3 files changed, 251 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/realtek,rtl-spi.yaml
create mode 100644 drivers/spi/spi-realtek-rtl.c
--
2.25.1
On Wed, 20 Jan 2021 14:59:26 +0100, Bert Vermeulen wrote:
> v5:
> - Changed SoC compatible to list exact models
>
> v4:
> - Added SoC series-specific compatible matches.
>
> v3:
> - Added cpu_relax() to busy loop.
> - Dropped .remove callback from driver struct.
> - Use (variations of) realtek-rtl as prefix.
> - Dropped Kconfig entry, and use MACH_REALTEK_RTL setting to build the
> driver, since there's no point booting without the SPI-connected flash.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] dt-bindings: spi: Realtek RTL838x/RTL839x SPI controller
commit: 6acbd614c2c8d3b8de5fb7605d6e24b9b3a8a17b
[2/2] spi: realtek-rtl: Add support for Realtek RTL838x/RTL839x SPI controllers
commit: a8af5cc2ff1e804694629a8ef320935629dd15ba
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