From: Drew Fustini <fustini@kernel.org>
To: Thomas Gerner <thomas.gerner@muenchen-mail.de>
Cc: Guo Ren <guoren@kernel.org>, Fu Wei <wefu@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] riscv: dts: thead: Enable wifi on the BeagleV-Ahead
Date: Wed, 27 May 2026 15:32:30 +0200 [thread overview]
Message-ID: <ahbybiNqYq0lFZ5w@gen8> (raw)
In-Reply-To: <20260514183510.234063-1-thomas.gerner@muenchen-mail.de>
On Thu, May 14, 2026 at 08:32:01PM +0200, Thomas Gerner wrote:
> The BeagleV-Ahead board uses an AP6203BM WiFi chip from AMPAK Technology
> Inc. connected to SDIO1. The chip is compatible to the broadcom wireless
> driver.
>
> The AP6203BM is a dual-band 2.4GHz/5GHz Wi-Fi 4 (802.11a/b/g/n) and
> Bluetooth 5.4 module. Bluetooth is not enabled by this patch.
>
> Signed-off-by: Thomas Gerner <thomas.gerner@muenchen-mail.de>
> ---
> Change in v4:
> - follow DTS coding style
> - use generic name for pwrseq node
>
> Change in v3:
> - consider further issues found by sashiko AI review
>
> Change in v2:
> - consider issues found by sashiko AI review
>
> .../boot/dts/thead/th1520-beaglev-ahead.dts | 48 +++++++++++++++++++
> 1 file changed, 48 insertions(+)
Reviewed-by: Drew Fustini <fustini@kernel.org>
I have applied this to thead-dt-for-next [1].
Thanks,
Drew
[1] https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git/commit/?h=thead-dt-for-next&id=3a5791956edbfa84d7256224167941931cbc46e7
prev parent reply other threads:[~2026-05-27 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 18:32 [PATCH v4] riscv: dts: thead: Enable wifi on the BeagleV-Ahead Thomas Gerner
2026-05-27 13:32 ` Drew Fustini [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=ahbybiNqYq0lFZ5w@gen8 \
--to=fustini@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=thomas.gerner@muenchen-mail.de \
--cc=wefu@redhat.com \
/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