From: Detlev Casanova <detlev.casanova@collabora.com>
To: linux-kernel@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Detlev Casanova <detlev.casanova@collabora.com>,
Alexey Charkov <alchark@gmail.com>,
Dragan Simic <dsimic@manjaro.org>,
Stephen Chen <stephen@radxa.com>,
Kever Yang <kever.yang@rock-chips.com>,
Liang Chen <cl@rock-chips.com>,
Elaine Zhang <zhangqing@rock-chips.com>,
Frank Wang <frank.wang@rock-chips.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: [PATCH 0/2] Add SPI support for Radxa ROCK 4D
Date: Fri, 28 Feb 2025 09:50:46 -0500 [thread overview]
Message-ID: <20250228145304.581349-1-detlev.casanova@collabora.com> (raw)
The board comes with a SPI NOR chip connected on the FSPI0 interface.
Add the SFC nodes for the rk3576 SoC and enable sfc0 for the Radxa ROCK
4D.
Detlev Casanova (2):
arm64: dts: rockchip: Add SFC nodes for rk3576
arm64: dts: rockchip: Add SPI NOR device on the ROCK 4D
.../boot/dts/rockchip/rk3576-rock-4d.dts | 16 ++++++++++++++
arch/arm64/boot/dts/rockchip/rk3576.dtsi | 22 +++++++++++++++++++
2 files changed, 38 insertions(+)
--
2.48.1
next reply other threads:[~2025-02-28 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 14:50 Detlev Casanova [this message]
2025-02-28 14:50 ` [PATCH 1/2] arm64: dts: rockchip: Add SFC nodes for rk3576 Detlev Casanova
2025-02-28 14:50 ` [PATCH 2/2] arm64: dts: rockchip: Add SPI NOR device on the ROCK 4D Detlev Casanova
2025-03-08 17:32 ` [PATCH 0/2] Add SPI support for Radxa " Heiko Stuebner
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=20250228145304.581349-1-detlev.casanova@collabora.com \
--to=detlev.casanova@collabora.com \
--cc=alchark@gmail.com \
--cc=cl@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=frank.wang@rock-chips.com \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=stephen@radxa.com \
--cc=zhangqing@rock-chips.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
all inboxes | Powered by JetHome®