From: sashiko-bot@kernel.org
To: "Svyatoslav Ryhel" <clamor95@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 07/10] ARM: tegra: tf701t: Fix BCM43341 WiFi/BT chip configuration
Date: Fri, 31 Jul 2026 11:54:27 +0000 [thread overview]
Message-ID: <20260731115428.633821F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260731114106.169398-8-clamor95@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message incorrectly conflates the BCM4334 chip with BCM43340/BCM43341, leading to a conflicting mismatch with the assigned `brcm,bcm43340-fmac` compatible string.
--
--- Patch [7]: [PATCH v3 07/10] ARM: tegra: tf701t: Fix BCM43341 WiFi/BT chip configuration ---
commit 3696d445e834823ddf2bb90d90ee281b49e3e4e6
Author: Svyatoslav Ryhel <clamor95@gmail.com>
ARM: tegra: tf701t: Fix BCM43341 WiFi/BT chip configuration
This commit fixes the WiFi and Bluetooth configuration for the Asus TF701T by
dropping the unsupported reset-gpio from the Bluetooth node and adding the
required LPO clock to both nodes. It also updates the WiFi primary compatible
string to brcm,bcm43340-fmac.
> The BCM4334 chip's Bluetooth part does not support reset-gpio. This was
> confirmed by testing on the TF701T, so drop reset-gpio from the Bluetooth
> node to comply with the existing schema. Additionally, the BCM4334
> supports an LPO clock, which is required for proper and stable operation
> of WiFi and Bluetooth, so add it to both nodes. Lastly, the BCM4334 chip's
> WiFi part has a dedicated compatible in the schema, so set
> 'brcm,bcm43340-fmac' as the primary compatible while 'brcm,bcm4329-fmac'
> remains as a fallback.
[Severity: Medium]
Is the description of the chip in the commit message accurate?
The commit title correctly references the "BCM43341", but the body of the
commit message repeatedly refers to the "BCM4334" chip. This creates some
confusion because the BCM4334 has its own distinct compatible string
("brcm,bcm4334-fmac").
Claiming "the BCM4334 chip's WiFi part has a dedicated compatible [...] so set
'brcm,bcm43340-fmac'" contradicts the actual compatible string being used,
which targets the 43340/43341 variants.
> diff --git a/arch/arm/boot/dts/nvidia/tegra114-asus-tf701t.dts b/arch/arm/boot/dts/nvidia/tegra114-asus-tf701t.dts
> --- a/arch/arm/boot/dts/nvidia/tegra114-asus-tf701t.dts
> +++ b/arch/arm/boot/dts/nvidia/tegra114-asus-tf701t.dts
[ ... ]
> @@ -2382,9 +2382,12 @@ mmc@78000000 {
> vqmmc-supply = <&vdd_1v8_vio>;
>
> wifi@1 {
> - compatible = "brcm,bcm4329-fmac";
> + compatible = "brcm,bcm43340-fmac", "brcm,bcm4329-fmac";
Could the commit message body be updated to consistently reference the
BCM43341 (or BCM43340) instead of BCM4334, to match the hardware and this new
compatible string in the wifi node?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260731114106.169398-1-clamor95@gmail.com?part=7
next prev parent reply other threads:[~2026-07-31 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 11:40 [PATCH v3 00/10] ARM: tegra: tf701t: Add new features Svyatoslav Ryhel
2026-07-31 11:40 ` [PATCH v3 01/10] ARM: tegra: tf701t: Configure CPU DFLL clock node Svyatoslav Ryhel
2026-07-31 11:56 ` sashiko-bot
2026-07-31 11:40 ` [PATCH v3 02/10] ARM: tegra: tf701t: Add core-supply to PMC node Svyatoslav Ryhel
2026-07-31 11:40 ` [PATCH v3 03/10] ARM: tegra: tf701t: Add MC and EMC timing nodes Svyatoslav Ryhel
2026-07-31 12:02 ` sashiko-bot
2026-07-31 11:41 ` [PATCH v3 04/10] ARM: tegra: tf701t: Remove pin_ prefix from PMIC pinmux Svyatoslav Ryhel
2026-07-31 11:41 ` [PATCH v3 05/10] ARM: tegra: tf701t: Add thermal zones for nct1008 sensor Svyatoslav Ryhel
2026-07-31 11:41 ` [PATCH v3 06/10] ARM: tegra: tf701t: Tune MMC devices Svyatoslav Ryhel
2026-07-31 11:41 ` [PATCH v3 07/10] ARM: tegra: tf701t: Fix BCM43341 WiFi/BT chip configuration Svyatoslav Ryhel
2026-07-31 11:54 ` sashiko-bot [this message]
2026-07-31 11:41 ` [PATCH v3 08/10] ARM: tegra: tf701t: Complete power sensor node Svyatoslav Ryhel
2026-07-31 11:41 ` [PATCH v3 09/10] ARM: tegra: tf701t: Configure UART-B line used for GPS Svyatoslav Ryhel
2026-07-31 11:41 ` [PATCH v3 10/10] ARM: tegra: tf701t: Add chosen node Svyatoslav Ryhel
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=20260731115428.633821F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.