From: Jun Guo <jun.guo@cixtech.com>
To: peter.chen@cixtech.com, fugang.duan@cixtech.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, broonie@kernel.org
Cc: linux-spi@vger.kernel.org, michal.simek@amd.com,
cix-kernel-upstream@cixtech.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, "jun.guo" <jun.guo@cixtech.com>
Subject: [PATCH v3 0/3] spi-cadence: support transmission with bits_per_word of 16 and 32
Date: Fri, 31 Oct 2025 15:30:00 +0800 [thread overview]
Message-ID: <20251031073003.3289573-1-jun.guo@cixtech.com> (raw)
From: "jun.guo" <jun.guo@cixtech.com>
The Cadence SPI IP supports configurable FIFO data widths during
integration. On some SoCs, the FIFO data width is designed to be 16 or
32 bits at the chip design stage. However, the current driver only
supports communication with an 8-bit FIFO data width. Therefore, these
patches are added to enable the driver to support communication with
16-bit and 32-bit FIFO data widths.
This series introduces the following enhancements for Cadence SPI
controller support on arm64 platforms:
Patch 1: Add a compatible string "cix,sky1-spi-r1p6" for the cix
sky1 SoC.
Patch 2: Update DT binding docs to support cix sky1 SoC.
Patch 3: Enhance the SPI Cadence driver to support data transmission
with bits_per_word values of 16 and 32.
The CIX Sky1 SPI supported patch is added:
https://lore.kernel.org/all/20250919013118.853078-1-jun.guo@cixtech.com/
The patches have been tested on CIX SKY1 platform.
Changes for v3:
- Rebase the dt-bindings modification on top of the latest patches in
spi/for-next to make the patch more minimal.
Changes for v2:
- Remove the fifo-width property and add a compatible string for the
cix sky1 SoC to control the FIFO data width configuration.
Jun Guo (3):
dt-bindings: spi: spi-cadence: update DT binding docs to support cix
sky1 SoC
spi: spi-cadence: supports transmission with bits_per_word of 16 and
32
arm64: dts: cix: add a compatible string for the cix sky1 SoC
.../devicetree/bindings/spi/spi-cadence.yaml | 1 +
arch/arm64/boot/dts/cix/sky1.dtsi | 4 +-
drivers/spi/spi-cadence.c | 106 +++++++++++++++---
3 files changed, 96 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2025-10-31 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 7:30 Jun Guo [this message]
2025-10-31 7:30 ` [PATCH v3 1/3] dt-bindings: spi: spi-cadence: update DT binding docs to support cix sky1 SoC Jun Guo
2025-10-31 15:10 ` Conor Dooley
2025-10-31 7:30 ` [PATCH v3 2/3] spi: spi-cadence: supports transmission with bits_per_word of 16 and 32 Jun Guo
2025-10-31 7:30 ` [PATCH v3 3/3] arm64: dts: cix: add a compatible string for the cix sky1 SoC Jun Guo
2025-11-17 9:32 ` Peter Chen
2025-11-14 17:07 ` (subset) [PATCH v3 0/3] spi-cadence: support transmission with bits_per_word of 16 and 32 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=20251031073003.3289573-1-jun.guo@cixtech.com \
--to=jun.guo@cixtech.com \
--cc=broonie@kernel.org \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fugang.duan@cixtech.com \
--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=peter.chen@cixtech.com \
--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 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).