mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alexey Charkov <alchark@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Pavel Zhovner <pavel@flipperdevices.com>
Subject: Re: [PATCH 0/3] arm64: dts: rockchip: Enable RTC, WiFi and Bluetooth on RK3576 EVB1
Date: Sun, 24 Aug 2025 12:54:39 +0200	[thread overview]
Message-ID: <175603280232.3445205.16083508502929513202.b4-ty@sntech.de> (raw)
In-Reply-To: <20250813-evb1-rtcwifibt-v1-0-d13c83422971@gmail.com>


On Wed, 13 Aug 2025 00:30:22 +0400, Alexey Charkov wrote:
> Rockchip RK3576 EVB1 boards follow the usual Rockchip design pattern
> with the I2C connected RTC chip feeding a 32 kHz LPO clock to the
> onboard Ampak AP6275P combo WiFi/BT module. In this case the WiFi
> part is connected by a PCIe link and BT over UART.
> 
> Add required DT nodes to enable them.
> 
> [...]

Applied, thanks!

[1/3] arm64: dts: rockchip: Add RTC on rk3576-evb1-v10
      commit: 0adaae77862932a19cc14c086d7fd15ec0ef7703
[2/3] arm64: dts: rockchip: Add WiFi on rk3576-evb1-v10
      commit: ebf8183ad08afc4fcabe1379a5098354829d950d
[3/3] arm64: dts: rockchip: Add Bluetooth on rk3576-evb1-v10
      commit: 34f7620912bb0f881a23dfea529e69fd2e8fdcf2

Best regards,
-- 
Heiko Stuebner <heiko@sntech.de>

      parent reply	other threads:[~2025-08-24 10:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12 20:30 Alexey Charkov
2025-08-12 20:30 ` [PATCH 1/3] arm64: dts: rockchip: Add RTC on rk3576-evb1-v10 Alexey Charkov
2025-08-12 20:30 ` [PATCH 2/3] arm64: dts: rockchip: Add WiFi " Alexey Charkov
2025-08-12 20:30 ` [PATCH 3/3] arm64: dts: rockchip: Add Bluetooth " Alexey Charkov
2025-08-24 10:54 ` 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=175603280232.3445205.16083508502929513202.b4-ty@sntech.de \
    --to=heiko@sntech.de \
    --cc=alchark@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=pavel@flipperdevices.com \
    --cc=robh@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

all inboxes | Powered by JetHome®