From: Chi-Wen Weng <cwweng.linux@gmail.com>
To: broonie@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
cwweng@nuvoton.com, cwweng.linux@gmail.com
Subject: [PATCH v3 0/2] spi: ma35d1-qspi: Enable GPIO chip-select support
Date: Mon, 3 Aug 2026 15:49:11 +0800 [thread overview]
Message-ID: <20260803074913.1656675-1-cwweng.linux@gmail.com> (raw)
In-Reply-To: <5769eae0-1b40-419f-8311-0d919bf619fa@sirena.org.uk>
From: Chi-Wen Weng <cwweng@nuvoton.com>
The generic SPI controller binding allows GPIO-based chip selects, but
the MA35D1 QSPI driver currently supports only the controller's two
native chip selects.
This series enables GPIO descriptor-based chip-select handling in the
driver and updates the binding so that num-cs can describe the total
number of native and GPIO chip selects.
Patch 1 removes the native hardware limit from the binding's num-cs
property.
Patch 2 enables GPIO chip selects in the driver while retaining the
hardware limit of two native chip selects.
Changes in v3:
* Split the binding and driver changes into a two-patch series.
* Allow num-cs to exceed the two native chip selects when GPIO chip
selects are present.
* Remove the driver's upper limit of two from num-cs.
* Rename the native chip-select limit for clarity.
* Reject out-of-range native chip-select indices in the setup callback.
* Retain active-high support for GPIO chip selects only.
Changes in v2:
* Enable GPIO descriptor-based chip-select handling in the driver
instead of disallowing cs-gpios in the binding.
* Set the maximum number of native chip selects to two.
* Reject active-high polarity only for native chip selects.
Chi-Wen Weng (2):
dt-bindings: spi: nuvoton,ma35d1-qspi: Allow additional GPIO chip
selects
spi: ma35d1-qspi: Enable GPIO chip selects
.../bindings/spi/nuvoton,ma35d1-qspi.yaml | 1 -
drivers/spi/spi-ma35d1-qspi.c | 32 ++++++++++++++++---
2 files changed, 28 insertions(+), 5 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2026-08-03 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 2:38 [PATCH v5 0/2] spi: ma35d1-qspi: Add Nuvoton MA35D1 QSPI controller Chi-Wen Weng
2026-07-31 2:38 ` [PATCH v5 1/2] dt-bindings: spi: nuvoton,ma35d1-qspi: Add Nuvoton MA35D1 QSPI Chi-Wen Weng
2026-07-31 20:28 ` Mark Brown
2026-08-03 2:06 ` Chi-Wen Weng
2026-08-03 6:24 ` [PATCH v2] spi: ma35d1-qspi: Enable GPIO chip selects Chi-Wen Weng
2026-08-03 6:38 ` sashiko-bot
2026-08-03 7:49 ` Chi-Wen Weng [this message]
2026-08-03 7:49 ` [PATCH v3 1/2] dt-bindings: spi: nuvoton,ma35d1-qspi: Allow additional " Chi-Wen Weng
2026-08-04 7:05 ` Krzysztof Kozlowski
2026-08-04 7:33 ` Chi-Wen Weng
2026-08-03 7:49 ` [PATCH v3 2/2] spi: ma35d1-qspi: Enable " Chi-Wen Weng
2026-08-03 12:30 ` [PATCH v3 0/2] spi: ma35d1-qspi: Enable GPIO chip-select support Mark Brown
2026-08-04 1:57 ` Chi-Wen Weng
2026-07-31 2:38 ` [PATCH v5 2/2] spi: ma35d1-qspi: Add Nuvoton MA35D1 QSPI controller support Chi-Wen Weng
2026-07-31 20:29 ` [PATCH v5 0/2] spi: ma35d1-qspi: Add Nuvoton MA35D1 QSPI controller Mark Brown
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=20260803074913.1656675-1-cwweng.linux@gmail.com \
--to=cwweng.linux@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cwweng@nuvoton.com \
--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=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.