From: Sean Anderson <sean.anderson@linux.dev>
To: Mark Brown <broonie@kernel.org>,
Michal Simek <michal.simek@amd.com>,
linux-spi@vger.kernel.org
Cc: Jinjie Ruan <ruanjinjie@huawei.com>,
linux-arm-kernel@lists.infradead.org,
Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>,
linux-kernel@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Sean Anderson <sean.anderson@linux.dev>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org
Subject: [PATCH 0/7] spi: zynqmp-gqspi: Split the bus and add GPIO support
Date: Thu, 16 Jan 2025 18:21:10 -0500 [thread overview]
Message-ID: <20250116232118.2694169-1-sean.anderson@linux.dev> (raw)
As discussed in patches 1 and FIXME, this device really has two SPI
busses. Split the existing "merged" bus in twain, and add support for
GPIO chipselects.
This series depends on [1, 2].
[1] https://lore.kernel.org/linux-spi/20250116224130.2684544-1-sean.anderson@linux.dev/T/#t
[2] https://lore.kernel.org/linux-spi/20250116225521.2688224-1-sean.anderson@linux.dev/T/#t
Sean Anderson (7):
dt-bindings: spi: zynqmp-qspi: Split the bus
spi: zynqmp-gqspi: Pass speed/mode directly to config_op
spi: zynqmp-gqspi: Configure SPI mode dynamically
spi: zynqmp-gqspi: Refactor out controller initialization
spi: zynqmp-gqspi: Split the bus
spi: zynqmp-gqspi: Support GPIO chip selects
ARM64: xilinx: zynqmp: Convert to split QSPI bus
.../bindings/spi/spi-zynqmp-qspi.yaml | 43 ++-
.../boot/dts/xilinx/zynqmp-sm-k26-revA.dts | 5 +-
.../boot/dts/xilinx/zynqmp-zc1232-revA.dts | 5 +-
.../boot/dts/xilinx/zynqmp-zc1254-revA.dts | 5 +-
.../dts/xilinx/zynqmp-zc1751-xm015-dc1.dts | 5 +-
.../dts/xilinx/zynqmp-zc1751-xm018-dc4.dts | 5 +-
.../boot/dts/xilinx/zynqmp-zcu102-revA.dts | 5 +-
.../boot/dts/xilinx/zynqmp-zcu104-revA.dts | 5 +-
.../boot/dts/xilinx/zynqmp-zcu104-revC.dts | 5 +-
.../boot/dts/xilinx/zynqmp-zcu106-revA.dts | 5 +-
.../boot/dts/xilinx/zynqmp-zcu111-revA.dts | 5 +-
.../boot/dts/xilinx/zynqmp-zcu1275-revA.dts | 5 +-
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 15 +-
drivers/spi/spi-zynqmp-gqspi.c | 328 ++++++++++++++----
14 files changed, 359 insertions(+), 82 deletions(-)
--
2.35.1.1320.gc452695387.dirty
next reply other threads:[~2025-01-16 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 23:21 Sean Anderson [this message]
2025-01-16 23:21 ` [PATCH 1/7] dt-bindings: spi: zynqmp-qspi: Split the bus Sean Anderson
2025-01-22 0:16 ` David Lechner
2025-01-23 16:24 ` Sean Anderson
2025-01-23 21:59 ` David Lechner
2025-01-23 22:37 ` Sean Anderson
2025-01-24 13:35 ` Mark Brown
2025-06-12 23:44 ` Sean Anderson
2025-06-13 14:20 ` David Lechner
2025-06-13 15:57 ` Sean Anderson
2025-06-13 16:44 ` Sean Anderson
2025-06-13 16:53 ` David Lechner
2025-01-16 23:21 ` [PATCH 7/7] ARM64: xilinx: zynqmp: Convert to split QSPI bus Sean Anderson
2025-01-16 23:24 ` [PATCH 0/7] spi: zynqmp-gqspi: Split the bus and add GPIO support Sean Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250116232118.2694169-1-sean.anderson@linux.dev \
--to=sean.anderson@linux.dev \
--cc=amit.kumar-mahapatra@amd.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=miquel.raynal@bootlin.com \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).