From: sashiko-bot@kernel.org
To: "Aaron Kling" <webgeek1234@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] soc/tegra: pmc: Add Tegra210B01 support
Date: Tue, 28 Jul 2026 02:14:26 +0000 [thread overview]
Message-ID: <20260728021426.CD0071F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260727-t210b01-pmc-v4-2-af68a21cd746@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Undocumented behavioral change disabling the MBIST workaround (`needs_mbist_war = false`) for Tegra210B01.
--
--- Patch [2]: [PATCH v4 2/2] soc/tegra: pmc: Add Tegra210B01 support ---
commit 86284ce805fe44e2007af5f83c9d15e2c0fd40d2
Author: Alexandre Hamamdjian <azkali.limited@gmail.com>
soc/tegra: pmc: Add Tegra210B01 support
This commit adds power management controller support for the Tegra210B01
stepping. The commit message notes it is similar to the original Tegra210
but removes the sata and ve2 powergates.
> diff --git a/drivers/soc/tegra/pmc.c b/drivers/soc/tegra/pmc.c
> index f419a5395545f..685b2b0f975c3 100644
> --- a/drivers/soc/tegra/pmc.c
> +++ b/drivers/soc/tegra/pmc.c
[ ... ]
> @@ -3897,6 +3897,67 @@ static const struct tegra_pmc_soc tegra210_pmc_soc = {
> .has_single_mmio_aperture = true,
> };
>
> +static const char * const tegra210b01_powergates[] = {
[ ... ]
> +};
> +
> +static const struct tegra_pmc_soc tegra210b01_pmc_soc = {
> + .supports_core_domain = false,
> + .num_powergates = ARRAY_SIZE(tegra210b01_powergates),
> + .powergates = tegra210b01_powergates,
> + .num_cpu_powergates = ARRAY_SIZE(tegra210_cpu_powergates),
> + .cpu_powergates = tegra210_cpu_powergates,
> + .has_tsense_reset = true,
> + .has_gpu_clamps = true,
> + .needs_mbist_war = false,
[Severity: Medium]
The commit message mentions that sata and ve2 are removed, but does not
mention disabling the MBIST workaround. Is this an intentional hardware
fix for the B01 stepping, or was this field accidentally set to false
compared to the original tegra210_pmc_soc?
If it's an intentional change, could the commit message be updated to
reflect this difference from the original Tegra210?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260727-t210b01-pmc-v4-0-af68a21cd746@gmail.com?part=2
next prev parent reply other threads:[~2026-07-28 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 2:00 [PATCH v4 0/2] soc/tegra: pmc: Add Tegra210B01 support Aaron Kling via B4 Relay
2026-07-28 2:00 ` [PATCH v4 1/2] dt-bindings: soc: tegra: pmc: Document Tegra210B01 Aaron Kling via B4 Relay
2026-07-28 2:00 ` [PATCH v4 2/2] soc/tegra: pmc: Add Tegra210B01 support Aaron Kling via B4 Relay
2026-07-28 2:14 ` sashiko-bot [this message]
2026-09-11 18:08 ` [PATCH v4 0/2] " Aaron Kling
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=20260728021426.CD0071F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=webgeek1234@gmail.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