From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: Heiko Stuebner <heiko@sntech.de>, Yao Zi <ziyao@disroot.org>,
Rob Herring <robh@kernel.org>, Mark Brown <broonie@kernel.org>,
Jonas Karlman <jonas@kwiboo.se>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: (subset) [PATCH 0/2] arm64: dts: rockchip: Add spi nodes for RK3528
Date: Mon, 9 Jun 2025 12:22:56 +0200 [thread overview]
Message-ID: <174946455541.762051.5287964403437718499.b4-ty@sntech.de> (raw)
In-Reply-To: <20250520100102.1226725-1-amadeus@jmu.edu.cn>
On Tue, 20 May 2025 18:01:00 +0800, Chukun Pan wrote:
> There are 2 SPI controllers on the RK3528 SoC, describe it.
> Tested using st7789v chip with spi-cpha and spi-cpol properties.
>
> [ 10.831306] fb_st7789v spi0.0: fbtft_property_value: buswidth = 8
> [ 11.042915] graphics fb0: fb_st7789v frame buffer, 240x320, 150 KiB
> video memory, 4 KiB buffer memory, fps=20, spi0.0 at 15 MHz
>
> [...]
Applied, thanks!
[2/2] arm64: dts: rockchip: Add spi nodes for RK3528
commit: 2783335329e5762deb0dc5b6d634225d8613af16
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2025-06-09 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 10:01 [PATCH 0/2] arm64: dts: rockchip: Add spi nodes for RK3528 Chukun Pan
2025-05-20 10:01 ` [PATCH 1/2] spi: dt-bindings: Add rk3528-spi compatible Chukun Pan
2025-05-20 15:45 ` Conor Dooley
2025-05-20 10:01 ` [PATCH 2/2] arm64: dts: rockchip: Add spi nodes for RK3528 Chukun Pan
2025-05-20 10:51 ` Jonas Karlman
2025-05-20 12:01 ` Chukun Pan
2025-05-21 17:56 ` (subset) [PATCH 0/2] " Mark Brown
2025-06-09 10:22 ` Heiko Stuebner [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=174946455541.762051.5287964403437718499.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=amadeus@jmu.edu.cn \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonas@kwiboo.se \
--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=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--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