From: sashiko-bot@kernel.org
To: "Bruno Banelli" <bbanelli@gmail.com>
Cc: vkoul@kernel.org, neil.armstrong@linaro.org,
linux-phy@lists.infradead.org, olteanv@gmail.com
Subject: Re: [PATCH] phy: spacemit: enable K1 USB 2.0 PHY by default on ARCH_SPACEMIT
Date: Tue, 25 Aug 2026 05:33:01 +0000 [thread overview]
Message-ID: <20260825053302.2C0421F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260825052158.66367-1-bbanelli@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
Pre-existing issues:
- [High] Missing `select REGMAP_MMIO` in `PHY_SPACEMIT_K1_USB2` Kconfig entry.
- [Medium] Missing `depends on HAS_IOMEM` in `PHY_SPACEMIT_K1_USB2` Kconfig entry.
--
--- Patch [1]: [PATCH] phy: spacemit: enable K1 USB 2.0 PHY by default on ARCH_SPACEMIT ---
commit f756c3cf5b8ff136e8d286e16f1e25289aa9e095
Author: Bruno Banelli <bbanelli@gmail.com>
phy: spacemit: enable K1 USB 2.0 PHY by default on ARCH_SPACEMIT
This patch adds a default ARCH_SPACEMIT configuration for the K1 USB 2.0 PHY
driver. This matches the PCIe PHY configuration and ensures the USB driver is
enabled by default on SpacemiT K1 boards.
> diff --git a/drivers/phy/spacemit/Kconfig b/drivers/phy/spacemit/Kconfig
> index 5fdf18fce4995..dd74a3faf01fd 100644
> --- a/drivers/phy/spacemit/Kconfig
> +++ b/drivers/phy/spacemit/Kconfig
> @@ -20,6 +20,7 @@ config PHY_SPACEMIT_K1_USB2
> depends on COMMON_CLK
> depends on USB_COMMON
> select GENERIC_PHY
[Severity: High]
This is a pre-existing issue, but does this config entry need to select
REGMAP_MMIO?
If a randconfig build has PHY_SPACEMIT_K1_USB2 enabled and CONFIG_REGMAP
enabled, but CONFIG_REGMAP_MMIO is disabled, would this result in a linkage
error? The driver uses devm_regmap_init_mmio() during probe:
drivers/phy/spacemit/phy-k1-usb2.c:spacemit_usb2phy_probe() {
...
sphy->regmap_base = devm_regmap_init_mmio(dev, base, &phy_regmap_config);
...
}
[Severity: Medium]
This is also a pre-existing issue, but should this config depend on HAS_IOMEM?
The driver maps I/O memory during probe:
drivers/phy/spacemit/phy-k1-usb2.c:spacemit_usb2phy_probe() {
...
base = devm_platform_ioremap_resource(pdev, 0);
...
}
Could this cause build or runtime failures on architectures lacking I/O memory
support (such as UML) when COMPILE_TEST is enabled?
> + default ARCH_SPACEMIT
> help
> Enable this to support K1 USB 2.0 PHY driver. This driver takes care of
> enabling and clock setup and will be used by K1 udc/ehci/otg/xhci driver.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260825052158.66367-1-bbanelli@gmail.com?part=1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-08-25 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 5:21 [PATCH] phy: spacemit: enable K1 USB 2.0 PHY by default on ARCH_SPACEMIT Bruno Banelli
2026-08-25 5:33 ` sashiko-bot [this message]
2026-08-25 22:27 ` Yixun Lan
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=20260825053302.2C0421F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bbanelli@gmail.com \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox