From: sashiko-bot@kernel.org
To: "Svyatoslav Ryhel" <clamor95@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 07/10] ARM: tegra: tf701t: Fix BCM4334 configuration
Date: Thu, 04 Jun 2026 07:08:15 +0000 [thread overview]
Message-ID: <20260604070816.257491F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260604065556.137614-8-clamor95@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch silently changes the WiFi node's compatible string to include 'brcm,bcm43340-fmac', which contradicts the commit message stating it fixes 'BCM4334' configuration.
--
commit e6b9085d18e1ff9ab5d22d698abaaba30676ee22
Author: Svyatoslav Ryhel <clamor95@gmail.com>
ARM: tegra: tf701t: Fix BCM4334 configuration
This commit removes the reset GPIO from the Bluetooth node and adds the
lpo clock to both the WiFi and Bluetooth nodes to fix configuration.
> diff --git a/arch/arm/boot/dts/nvidia/tegra114-asus-tf701t.dts b/arch/arm/boot/dts/nvidia/tegra114-asus-tf701t.dts
> index 73276f2aa7fe4..e3e0b4ba7eb86 100644
> --- 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";
[Severity: Medium]
The commit message notes this fixes BCM4334 configuration, and explicitly
mentions dropping a GPIO and adding an lpo clock, but it does not mention
modifying the compatible string.
Could the commit message be updated to document this change? Also, is
brcm,bcm43340-fmac the correct value here, or is it a typo for
brcm,bcm4334-fmac, given the commit title and the Bluetooth node both
specify BCM4334?
> reg = <1>;
>
> + clocks = <&palmas_clk32k>;
> + clock-names = "lpo";
> +
> interrupt-parent = <&gpio>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260604065556.137614-1-clamor95@gmail.com?part=7
next prev parent reply other threads:[~2026-06-04 7:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 6:55 [PATCH v1 00/10] ARM: tegra: tf701t: Add new features Svyatoslav Ryhel
2026-06-04 6:55 ` [PATCH v1 01/10] ARM: tegra: tf701t: Configure CPU DFLL clock node Svyatoslav Ryhel
2026-06-04 7:15 ` sashiko-bot
2026-06-04 6:55 ` [PATCH v1 02/10] ARM: tegra: tf701t: Add core-supply to PMC node Svyatoslav Ryhel
2026-06-04 6:55 ` [PATCH v1 03/10] ARM: tegra: tf701t: Add MC and EMC timing nodes Svyatoslav Ryhel
2026-06-04 6:55 ` [PATCH v1 04/10] ARM: tegra: tf701t: Remove pin_ prefix from PMIC pinmux Svyatoslav Ryhel
2026-06-04 6:55 ` [PATCH v1 05/10] ARM: tegra: tf701t: Add thermal zones for nct1008 sensor Svyatoslav Ryhel
2026-06-04 7:05 ` sashiko-bot
2026-06-04 6:55 ` [PATCH v1 06/10] ARM: tegra: tf701t: Tune MMC devices Svyatoslav Ryhel
2026-06-04 7:10 ` sashiko-bot
2026-06-04 6:55 ` [PATCH v1 07/10] ARM: tegra: tf701t: Fix BCM4334 configuration Svyatoslav Ryhel
2026-06-04 7:08 ` sashiko-bot [this message]
2026-06-04 6:55 ` [PATCH v1 08/10] ARM: tegra: tf701t: Complete power sensor node Svyatoslav Ryhel
2026-06-04 6:55 ` [PATCH v1 09/10] ARM: tegra: tf701t: Configure UART-B line used for GPS Svyatoslav Ryhel
2026-06-04 6:55 ` [PATCH v1 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=20260604070816.257491F00893@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox