All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jon Hunter" <jonathanh@nvidia.com>
Cc: robh@kernel.org, neil.armstrong@linaro.org, vkoul@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	olteanv@gmail.com, linux-phy@lists.infradead.org
Subject: Re: [PATCH v3 3/3] phy: tegra: Add support for Tegra238 XUSB pad controller
Date: Wed, 07 Oct 2026 14:52:57 +0000	[thread overview]
Message-ID: <sashiko-outbox-163126@kernel.org> (raw)
In-Reply-To: <20261007-tegra-phy-v3-3-d501de414710@nvidia.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] phy: tegra: missing declarations for exported SoC structs in xusb.h
--

commit 8acf4872f17465f59f32558aefacb7be8e2c679f
Author: Jon Hunter <jonathanh@nvidia.com>

phy: tegra: Add support for Tegra238 XUSB pad controller

This commit adds support for the Tegra238 XUSB pad controller. It populates
the Tegra238 specific SoC data, reusing structures from Tegra186 and
Tegra194, and drops the compile time guards around these shared structures in
the source file.

> diff --git a/drivers/phy/tegra/xusb-tegra186.c b/drivers/phy/tegra/xusb-tegra186.c
> index 322efdea0d807..aa8ab94fad4cf 100644
> --- a/drivers/phy/tegra/xusb-tegra186.c
> +++ b/drivers/phy/tegra/xusb-tegra186.c
[ ... ]
> @@ -1665,11 +1664,7 @@ const struct tegra_xusb_padctl_soc tegra186_xusb_padctl_soc = {
>  	.num_supplies = ARRAY_SIZE(tegra186_xusb_padctl_supply_names),
>  };
>  EXPORT_SYMBOL_GPL(tegra186_xusb_padctl_soc);
> -#endif

[Severity: Low]
Since the guards are removed here, tegra186_xusb_padctl_soc is now defined
and exported unconditionally. However, its extern declaration in
drivers/phy/tegra/xusb.h remains conditionally guarded:

#if defined(CONFIG_ARCH_TEGRA_186_SOC)
extern const struct tegra_xusb_padctl_soc tegra186_xusb_padctl_soc;
#endif

Does this cause missing declaration warnings (-Wmissing-declarations or
-Wmissing-prototypes) during the build if the kernel is configured with
CONFIG_ARCH_TEGRA_238_SOC=y but CONFIG_ARCH_TEGRA_186_SOC=n? Should the
corresponding guards in xusb.h be removed as well?

>  
> -#if IS_ENABLED(CONFIG_ARCH_TEGRA_194_SOC) || \
> -	IS_ENABLED(CONFIG_ARCH_TEGRA_234_SOC) || \
> -	IS_ENABLED(CONFIG_ARCH_TEGRA_264_SOC)
>  static const char * const tegra194_xusb_padctl_supply_names[] = {
>  	"avdd-usb",
>  	"vclamp-usb",

[Severity: Low]
A similar mismatch occurs here for tegra194_xusb_padctl_soc. The definition
is now unconditional, but the extern declaration in xusb.h is still guarded
by #if defined(CONFIG_ARCH_TEGRA_194_SOC). Could this also trigger missing
prototype warnings when building with certain configs disabled?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261007-tegra-phy-v3-0-d501de414710@nvidia.com?part=3

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Jon Hunter" <jonathanh@nvidia.com>
Cc: robh@kernel.org, neil.armstrong@linaro.org, vkoul@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	olteanv@gmail.com, linux-phy@lists.infradead.org
Subject: Re: [PATCH v3 3/3] phy: tegra: Add support for Tegra238 XUSB pad controller
Date: Wed, 07 Oct 2026 14:52:57 +0000	[thread overview]
Message-ID: <sashiko-outbox-163126@kernel.org> (raw)
In-Reply-To: <20261007-tegra-phy-v3-3-d501de414710@nvidia.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] phy: tegra: missing declarations for exported SoC structs in xusb.h
--

commit 8acf4872f17465f59f32558aefacb7be8e2c679f
Author: Jon Hunter <jonathanh@nvidia.com>

phy: tegra: Add support for Tegra238 XUSB pad controller

This commit adds support for the Tegra238 XUSB pad controller. It populates
the Tegra238 specific SoC data, reusing structures from Tegra186 and
Tegra194, and drops the compile time guards around these shared structures in
the source file.

> diff --git a/drivers/phy/tegra/xusb-tegra186.c b/drivers/phy/tegra/xusb-tegra186.c
> index 322efdea0d807..aa8ab94fad4cf 100644
> --- a/drivers/phy/tegra/xusb-tegra186.c
> +++ b/drivers/phy/tegra/xusb-tegra186.c
[ ... ]
> @@ -1665,11 +1664,7 @@ const struct tegra_xusb_padctl_soc tegra186_xusb_padctl_soc = {
>  	.num_supplies = ARRAY_SIZE(tegra186_xusb_padctl_supply_names),
>  };
>  EXPORT_SYMBOL_GPL(tegra186_xusb_padctl_soc);
> -#endif

[Severity: Low]
Since the guards are removed here, tegra186_xusb_padctl_soc is now defined
and exported unconditionally. However, its extern declaration in
drivers/phy/tegra/xusb.h remains conditionally guarded:

#if defined(CONFIG_ARCH_TEGRA_186_SOC)
extern const struct tegra_xusb_padctl_soc tegra186_xusb_padctl_soc;
#endif

Does this cause missing declaration warnings (-Wmissing-declarations or
-Wmissing-prototypes) during the build if the kernel is configured with
CONFIG_ARCH_TEGRA_238_SOC=y but CONFIG_ARCH_TEGRA_186_SOC=n? Should the
corresponding guards in xusb.h be removed as well?

>  
> -#if IS_ENABLED(CONFIG_ARCH_TEGRA_194_SOC) || \
> -	IS_ENABLED(CONFIG_ARCH_TEGRA_234_SOC) || \
> -	IS_ENABLED(CONFIG_ARCH_TEGRA_264_SOC)
>  static const char * const tegra194_xusb_padctl_supply_names[] = {
>  	"avdd-usb",
>  	"vclamp-usb",

[Severity: Low]
A similar mismatch occurs here for tegra194_xusb_padctl_soc. The definition
is now unconditional, but the extern declaration in xusb.h is still guarded
by #if defined(CONFIG_ARCH_TEGRA_194_SOC). Could this also trigger missing
prototype warnings when building with certain configs disabled?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261007-tegra-phy-v3-0-d501de414710@nvidia.com?part=3

  reply	other threads:[~2026-10-07 14:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 14:44 [PATCH v3 0/3] phy: tegra: xusb: Add Tegra238 support Jon Hunter
2026-10-07 14:44 ` Jon Hunter
2026-10-07 14:44 ` [PATCH v3 1/3] dt-bindings: phy: tegra194: Add compatible for Tegra238 Jon Hunter
2026-10-07 14:44   ` Jon Hunter
2026-10-07 14:44 ` [PATCH v3 2/3] phy: tegra: xusb: Use dev_err_probe() Jon Hunter
2026-10-07 14:44   ` Jon Hunter
2026-10-07 14:44 ` [PATCH v3 3/3] phy: tegra: Add support for Tegra238 XUSB pad controller Jon Hunter
2026-10-07 14:44   ` Jon Hunter
2026-10-07 14:52   ` sashiko-bot [this message]
2026-10-07 14:52     ` sashiko-bot
2026-10-07 15:20   ` Manivannan Sadhasivam
2026-10-07 15:20     ` Manivannan Sadhasivam
2026-10-07 16:27     ` Jon Hunter
2026-10-07 16:27       ` Jon Hunter
2026-10-08 12:09       ` Jon Hunter
2026-10-08 12:09         ` Jon Hunter
2026-10-09  8:07         ` Vinod Koul
2026-10-09  8:07           ` Vinod Koul
2026-10-07 15:15 ` [PATCH v3 0/3] phy: tegra: xusb: Add Tegra238 support Manivannan Sadhasivam
2026-10-07 15:15   ` Manivannan Sadhasivam
2026-10-09  8:18 ` Vinod Koul
2026-10-09  8:18   ` Vinod Koul

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=sashiko-outbox-163126@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=olteanv@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@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 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.