From: Yixun Lan <dlan@gentoo.org>
To: Alex Elder <elder@riscstar.com>
Cc: broonie@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, ziyao@disroot.org,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, p.zabel@pengutronix.de,
spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] riscv: dts: spacemit: define a SPI controller node
Date: Tue, 23 Sep 2025 08:19:30 +0800 [thread overview]
Message-ID: <20250923001930-GYB1303776@gentoo.org> (raw)
In-Reply-To: <20250922161717.1590690-4-elder@riscstar.com>
Hi Alex,
On 11:17 Mon 22 Sep , Alex Elder wrote:
> Define a node for the fourth SoC SPI controller (number 3) on
> the SpacemiT K1 SoC.
>
> Enable it on the Banana Pi BPI-F3 board, which exposes this feature
> via its GPIO block:
> GPIO PIN 19: MOSI
> GPIO PIN 21: MISO
> GPIO PIN 23: SCLK
> GPIO PIN 24: SS (inverted)
>
> Define pincontrol configurations for the pins as used on that board.
>
> (This was tested using a GigaDevice GD25Q64E SPI NOR chip.)
>
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
> v3: - Moved the SPI controller into the dma-bus memory region
>
> .../boot/dts/spacemit/k1-bananapi-f3.dts | 7 +++++++
> arch/riscv/boot/dts/spacemit/k1-pinctrl.dtsi | 20 +++++++++++++++++++
> arch/riscv/boot/dts/spacemit/k1.dtsi | 16 +++++++++++++++
> 3 files changed, 43 insertions(+)
>
> diff --git a/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts b/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
> index 2aaaff77831e1..d9d865fbe320e 100644
> --- a/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
> +++ b/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
> @@ -14,6 +14,7 @@ aliases {
> ethernet0 = ð0;
> ethernet1 = ð1;
> serial0 = &uart0;
> + spi3 = &spi3;
> };
>
> chosen {
> @@ -92,6 +93,12 @@ &pdma {
> status = "okay";
> };
>
> +&spi3 {
> + pinctrl-0 = <&ssp3_0_cfg>;
> + pinctrl-names = "default";
> + status = "okay";
> +};
> +
> &uart0 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart0_2_cfg>;
> diff --git a/arch/riscv/boot/dts/spacemit/k1-pinctrl.dtsi b/arch/riscv/boot/dts/spacemit/k1-pinctrl.dtsi
> index aff19c86d5ff3..205c201a3005c 100644
> --- a/arch/riscv/boot/dts/spacemit/k1-pinctrl.dtsi
> +++ b/arch/riscv/boot/dts/spacemit/k1-pinctrl.dtsi
> @@ -76,4 +76,24 @@ pwm14-1-pins {
> drive-strength = <32>;
> };
> };
> +
> + ssp3_0_cfg: ssp3-0-cfg {
..
> + ssp3-0-no-pull-pins {
I'd prefer not to enforce "pull" info inside the name, you can't embed
all property info, besides, what's if you want to change/override later?
how about just name it as ssp3-0-defaul-pins or simply ssp3-0-pins?
> + pinmux = <K1_PADCONF(75, 2)>, /* SCLK */
> + <K1_PADCONF(77, 2)>, /* MOSI */
> + <K1_PADCONF(78, 2)>; /* MISO */
> +
> + bias-disable;
> + drive-strength = <19>;
> + power-source = <3300>;
> + };
> +
> + ssp3-0-frm-pins {
> + pinmux = <K1_PADCONF(76, 2)>; /* FRM (frame) */
> +
> + bias-pull-up = <0>;
> + drive-strength = <19>;
> + power-source = <3300>;
> + };
> + };
> };
> diff --git a/arch/riscv/boot/dts/spacemit/k1.dtsi b/arch/riscv/boot/dts/spacemit/k1.dtsi
> index 6cdcd80a7c83b..eb8a14dd72ea4 100644
> --- a/arch/riscv/boot/dts/spacemit/k1.dtsi
> +++ b/arch/riscv/boot/dts/spacemit/k1.dtsi
> @@ -797,6 +797,22 @@ uart9: serial@d4017800 {
> status = "disabled";
> };
>
> + spi3: spi@d401c000 {
> + compatible = "spacemit,k1-spi";
> + reg = <0x0 0xd401c000 0x0 0x30>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + clocks = <&syscon_apbc CLK_SSP3>,
> + <&syscon_apbc CLK_SSP3_BUS>;
> + clock-names = "core", "bus";
> + resets = <&syscon_apbc RESET_SSP3>;
> + interrupts = <55>;
..
> + dmas = <&pdma 20>,
> + <&pdma 19>;
can we also squash the dmas into one line? but, do split if there are too many..
yes, it's simply a style change that I'd like to keep them consistent at DT level,
besides you might also want to adjust dt-binding examples to align with them here..
thanks
> + dma-names = "rx", "tx";
> + status = "disabled";
> + };
> +
> /* sec_uart1: 0xf0612000, not available from Linux */
> };
>
> --
> 2.48.1
>
>
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-09-23 0:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 16:17 [PATCH v3 0/3] spi: support the SpacemiT K1 SPI controller Alex Elder
2025-09-22 16:17 ` [PATCH v3 1/3] dt-bindings: spi: add SpacemiT K1 SPI support Alex Elder
2025-09-22 16:17 ` [PATCH v3 2/3] spi: spacemit: introduce SpacemiT K1 SPI controller driver Alex Elder
2025-09-22 23:06 ` Yixun Lan
2025-09-23 8:27 ` Mark Brown
2025-09-23 12:49 ` Alex Elder
2025-09-28 12:36 ` Yixun Lan
2025-09-28 18:30 ` Alex Elder
2025-09-22 16:17 ` [PATCH v3 3/3] riscv: dts: spacemit: define a SPI controller node Alex Elder
2025-09-23 0:19 ` Yixun Lan [this message]
2025-09-23 2:59 ` Troy Mitchell
2025-09-23 6:31 ` Junhui Liu
2025-09-24 3:11 ` Troy Mitchell
2025-09-23 12:49 ` Alex Elder
2025-09-24 3:10 ` Troy Mitchell
2025-09-23 12:49 ` Alex Elder
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=20250923001930-GYB1303776@gentoo.org \
--to=dlan@gentoo.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@riscstar.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=ziyao@disroot.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