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, junhui.liu@pigmoral.tech,
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 v4 3/3] riscv: dts: spacemit: define a SPI controller node
Date: Fri, 26 Sep 2025 12:07:13 +0800 [thread overview]
Message-ID: <20250926040713-GYA1324993@gentoo.org> (raw)
In-Reply-To: <20250925121714.2514932-4-elder@riscstar.com>
Hi Alex,
On 07:17 Thu 25 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>
>
Reviewed-by: Yixun Lan <dlan@gentoo.org>
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-09-26 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 12:17 [PATCH v4 0/3] spi: support the SpacemiT K1 SPI controller Alex Elder
2025-09-25 12:17 ` [PATCH v4 1/3] dt-bindings: spi: add SpacemiT K1 SPI support Alex Elder
2025-09-25 12:17 ` [PATCH v4 2/3] spi: spacemit: introduce SpacemiT K1 SPI controller driver Alex Elder
2025-09-25 12:17 ` [PATCH v4 3/3] riscv: dts: spacemit: define a SPI controller node Alex Elder
2025-09-26 4:07 ` Yixun Lan [this message]
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=20250926040713-GYA1324993@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=junhui.liu@pigmoral.tech \
--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