[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200127210415.5708-1-chris.packham@alliedtelesis.co.nz>
Date: Tue, 28 Jan 2020 10:04:13 +1300
From: Chris Packham <chris.packham@...iedtelesis.co.nz>
To: broonie@...nel.org, robh+dt@...nel.org, mark.rutland@....com
Cc: linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Chris Packham <chris.packham@...iedtelesis.co.nz>
Subject: [PATCH v3 0/2] SPI bus multiplexing
This is a revisit of two earlier efforts to add more complex mutliplexing to
SPI busses.
https://patchwork.kernel.org/patch/2706151/
https://patchwork.kernel.org/patch/10897255/
This version makes use of the general purpose mux controller which simplifies
things greatly.
One outstanding problem is the need for the spi-max-frequency on the mux
device. This is not used for anything and is just needed to satisfy the spi
driver infrastructure which expects all spi devices to have this property.
Chris Packham (2):
dt-bindings: spi: Document binding for generic SPI multiplexer
spi: Add generic SPI multiplexer
.../devicetree/bindings/spi/spi-mux.yaml | 89 +++++++++
drivers/spi/Kconfig | 12 ++
drivers/spi/Makefile | 1 +
drivers/spi/spi-mux.c | 189 ++++++++++++++++++
4 files changed, 291 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-mux.yaml
create mode 100644 drivers/spi/spi-mux.c
--
2.25.0
Powered by blists - more mailing lists