From: sashiko-bot@kernel.org
To: "Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Cc: vkoul@kernel.org, conor+dt@kernel.org, neil.armstrong@linaro.org,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org,
media-ci@linuxtv.org, robh@kernel.org, linux-clk@vger.kernel.org,
olteanv@gmail.com
Subject: Re: [PATCH v17 2/5] phy: core: Add phy_get_by_of_node()
Date: Sun, 06 Sep 2026 14:31:26 +0000 [thread overview]
Message-ID: <20260906143127.2B5691F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260906-b4-linux-next-25-03-13-dtsi-x1e80100-camss-v17-2-e2197a3e2551@linaro.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] phy_get_by_of_node() misses the legacy usb-nop-xceiv workaround, causing infinite -EPROBE_DEFER loops.
--
commit a021b561c8a9bfb36addca720d49ea935b34a131
Author: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
phy: core: Add phy_get_by_of_node()
This commit introduces phy_get_by_of_node() to allow looking up a phy
directly by its device node. It refactors the existing lookup logic in
_of_phy_get() into a new shared helper function called
_of_phy_get_with_args().
> diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
> index 89addd732bff3..490a7cde6d40a 100644
> --- a/drivers/phy/phy-core.c
> +++ b/drivers/phy/phy-core.c
[ ... ]
> @@ -1001,6 +1015,41 @@ struct phy *devm_of_phy_get_by_index(struct device *dev, struct device_node *np,
> }
> EXPORT_SYMBOL_GPL(devm_of_phy_get_by_index);
>
> +/**
> + * phy_get_by_of_node() - lookup and obtain a reference to a phy by device_node
> + * @np: node containing the phy
> + *
> + * Returns the phy associated with the device node or ERR_PTR.
> + */
> +struct phy *phy_get_by_of_node(struct device_node *np)
> +{
> + struct of_phandle_args args = { .np = np, .args_count = 0 };
> + struct phy *phy;
> +
> + if (!np)
> + return ERR_PTR(-EINVAL);
> +
> + mutex_lock(&phy_provider_mutex);
> +
> + phy = _of_phy_get_with_args(&args);
[Severity: Medium]
Does this new API miss the legacy compatibility check for usb-nop-xceiv?
In _of_phy_get(), there is a workaround that returns -ENODEV if the
device is compatible with "usb-nop-xceiv". Because this workaround was
left in _of_phy_get() rather than being relocated into the shared
_of_phy_get_with_args() helper, phy_get_by_of_node() bypasses it
completely.
Could this cause drivers looking up a "usb-nop-xceiv" node via this new
API to receive -EPROBE_DEFER instead of -ENODEV, leading to infinite
probe deferrals and breaking fallback to the usb-phy subsystem?
> +
> + if (IS_ERR(phy))
> + goto out_unlock;
> +
> + if (!try_module_get(phy->ops->owner)) {
> + phy = ERR_PTR(-EPROBE_DEFER);
> + goto out_unlock;
> + }
> +
> + get_device(&phy->dev);
> +
> +out_unlock:
> + mutex_unlock(&phy_provider_mutex);
> +
> + return phy;
> +}
> +EXPORT_SYMBOL_GPL(phy_get_by_of_node);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260906-b4-linux-next-25-03-13-dtsi-x1e80100-camss-v17-0-e2197a3e2551@linaro.org?part=2
next prev parent reply other threads:[~2026-09-06 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 14:17 [PATCH v17 0/5] Add phy_get_by_of_node and devm helper Bryan O'Donoghue
2026-09-06 14:17 ` [PATCH v17 1/5] phy: core: Fix use-after-free in phy_get paths Bryan O'Donoghue
2026-09-06 14:17 ` [PATCH v17 2/5] phy: core: Add phy_get_by_of_node() Bryan O'Donoghue
2026-09-06 14:31 ` sashiko-bot [this message]
2026-09-06 14:17 ` [PATCH v17 3/5] phy: core: Add devm_phy_get_by_of_node() Bryan O'Donoghue
2026-09-06 14:17 ` [PATCH v17 4/5] media: qcom: camss: Add support for PHY API devices Bryan O'Donoghue
2026-09-06 14:32 ` sashiko-bot
2026-09-06 14:17 ` [PATCH v17 5/5] media: qcom: camss: Use data-lanes starting at 1 for new CSIPHY mode Bryan O'Donoghue
2026-09-06 14:28 ` sashiko-bot
2026-09-06 15:47 ` Nihal Kumar Gupta
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=20260906143127.2B5691F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=media-ci@linuxtv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox