From: yankei.fong@altera.com
To: Dinh Nguyen <dinguyen@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list),
Matthew Gerlach <matthew.gerlach@altera.com>
Subject: [PATCH 0/4] Add 4-bit SPI bus width on target devices
Date: Tue, 24 Jun 2025 14:52:24 +0800 [thread overview]
Message-ID: <cover.1750747163.git.yan.kei.fong@altera.com> (raw)
From: "Fong, Yan Kei" <yan.kei.fong@altera.com>
Add SPI bus width properties to correctly describe the hardware on the following devices:
- Stratix10
- Agilex
- Agilex5
- N5X
Fong, Yan Kei (4):
arm64: dts: socfpga: n5x: Add 4-bit SPI bus width
arm64: dts: socfpga: stratix10: Add 4-bit SPI bus width
arm64: dts: socfpga: agilex: Add 4-bit SPI bus width
arm64: dts: socfpga: agilex5: Add 4-bit SPI bus width
arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts | 2 ++
arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts | 2 ++
arch/arm64/boot/dts/intel/socfpga_agilex_socdk.dts | 2 ++
arch/arm64/boot/dts/intel/socfpga_n5x_socdk.dts | 2 ++
4 files changed, 8 insertions(+)
--
2.25.1
next reply other threads:[~2025-06-24 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 6:52 yankei.fong [this message]
2025-06-24 6:52 ` [PATCH 1/4] arm64: dts: socfpga: n5x: Add 4-bit SPI bus width yankei.fong
2025-08-31 1:40 ` Dinh Nguyen
2025-06-24 6:52 ` [PATCH 2/4] arm64: dts: socfpga: stratix10: " yankei.fong
2025-06-24 6:52 ` [PATCH 3/4] arm64: dts: socfpga: agilex: " yankei.fong
2025-06-24 6:52 ` [PATCH 4/4] arm64: dts: socfpga: agilex5: " yankei.fong
2025-06-24 17:32 ` [PATCH 0/4] Add 4-bit SPI bus width on target devices Dinh Nguyen
2025-06-30 2:44 ` yankei.fong
2025-07-09 7:00 ` Fong, Yan Kei
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=cover.1750747163.git.yan.kei.fong@altera.com \
--to=yankei.fong@altera.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@altera.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).