devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Geis <pgwipeout@gmail.com>
To: linux-rockchip@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: Peter Geis <pgwipeout@gmail.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 4/7] arm64: dts: rockchip: add rk356x sfc support
Date: Fri, 29 Apr 2022 07:52:49 -0400	[thread overview]
Message-ID: <20220429115252.2360496-5-pgwipeout@gmail.com> (raw)
In-Reply-To: <20220429115252.2360496-1-pgwipeout@gmail.com>

Add the sfc node to the rk356x device tree. This enables spi flash
support for this soc.

Signed-off-by: Peter Geis <pgwipeout@gmail.com>
---
 arch/arm64/boot/dts/rockchip/rk356x.dtsi | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/arch/arm64/boot/dts/rockchip/rk356x.dtsi b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
index ca20d7b91fe5..61a6d9d4c8a0 100644
--- a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
@@ -750,6 +750,17 @@ sdmmc1: mmc@fe2c0000 {
 		status = "disabled";
 	};
 
+	sfc: spi@fe300000 {
+		compatible = "rockchip,sfc";
+		reg = <0x0 0xfe300000 0x0 0x4000>;
+		interrupts = <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
+		clocks = <&cru SCLK_SFC>, <&cru HCLK_SFC>;
+		clock-names = "clk_sfc", "hclk_sfc";
+		pinctrl-0 = <&fspi_pins>;
+		pinctrl-names = "default";
+		status = "disabled";
+	};
+
 	sdhci: mmc@fe310000 {
 		compatible = "rockchip,rk3568-dwcmshc";
 		reg = <0x0 0xfe310000 0x0 0x10000>;
-- 
2.25.1


  parent reply	other threads:[~2022-04-29 11:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 11:52 [PATCH v2 0/7] Add support for several new rk3566 SBCs Peter Geis
2022-04-29 11:52 ` [PATCH v2 1/7] dt-bindings: arm: rockchip: Add Pine64 Quartz64 Model B Peter Geis
2022-05-01  8:13   ` Krzysztof Kozlowski
2022-04-29 11:52 ` [PATCH v2 2/7] dt-bindings: arm: rockchip: Add Pine64 SoQuartz SoM Peter Geis
2022-04-29 11:52 ` [PATCH v2 3/7] dt-bindings: arm: rockchip: Add Firefly Station M2 Peter Geis
2022-04-29 11:52 ` Peter Geis [this message]
2022-04-29 11:52 ` [PATCH v2 5/7] arm64: dts: rockchip: add Pine64 Quartz64-B device tree Peter Geis
2022-04-30  0:16   ` kernel test robot
2022-04-30 14:46     ` Peter Geis
2022-04-30 16:57       ` Heiko Stübner
2022-05-01  7:06   ` Johan Jonker
2022-05-01 11:31     ` Heiko Stübner
2022-05-01 11:48       ` Peter Geis
2022-05-01 12:04         ` Heiko Stübner
2022-04-29 11:52 ` [PATCH v2 6/7] arm64: dts: rockchip: add SoQuartz CM4IO dts Peter Geis
2022-04-30  5:42   ` kernel test robot
2022-04-29 11:52 ` [PATCH v2 7/7] arm64: dts: rockchip: add dts for Firefly Station M2 rk3566 Peter Geis
2022-04-30 11:06   ` kernel test robot
2022-04-30 14:05 ` (subset) [PATCH v2 0/7] Add support for several new rk3566 SBCs Heiko Stuebner
2022-05-01 13:05 ` 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=20220429115252.2360496-5-pgwipeout@gmail.com \
    --to=pgwipeout@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --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+dt@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).