Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Cc: conor+dt@kernel.org, media-ci@linuxtv.org,
	devicetree@vger.kernel.org, olteanv@gmail.com, robh@kernel.org,
	neil.armstrong@linaro.org, linux-phy@lists.infradead.org,
	linux-clk@vger.kernel.org, vkoul@kernel.org
Subject: Re: [PATCH v18 2/5] phy: core: Add phy_get_by_of_node()
Date: Thu, 17 Sep 2026 11:18:44 +0000	[thread overview]
Message-ID: <20260917111844.B28E31F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917-b4-linux-next-25-03-13-dtsi-x1e80100-camss-v18-2-f85c9103177e@linaro.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] phy: phy_get_by_of_node() bypasses usb-nop-xceiv legacy check
--

commit d8c1cc00496d43b5d8e3b5f03853e461912120c9
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 PHY lookups by device
node. It splits the lookup logic from _of_phy_get() into a new internal
_of_phy_get_with_args() helper.

> diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
> --- 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 bypass the legacy compatibility check for usb-nop-xceiv PHYs?

Looking at the newly introduced helper _of_phy_get_with_args(), it does
not contain the check for usb-nop-xceiv that remains in _of_phy_get():

drivers/phy/phy-core.c:_of_phy_get() {
        ...
        /* This phy type handled by the usb-phy subsystem for now */
        if (of_device_is_compatible(args.np, "usb-nop-xceiv")) {
                phy = ERR_PTR(-ENODEV);
                ...
        }
        ...
}

Because phy_get_by_of_node() calls _of_phy_get_with_args() directly,
if it is called on a device node with the usb-nop-xceiv compatible string,
it will fail to find the legacy PHY provider and return -EPROBE_DEFER
instead of -ENODEV.

Could this cause caller drivers to enter infinite probe deferral loops
since the legacy PHY will never register with this generic framework?

> +
> +	if (IS_ERR(phy))
> +		goto out_unlock;

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917-b4-linux-next-25-03-13-dtsi-x1e80100-camss-v18-0-f85c9103177e@linaro.org?part=2

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

  reply	other threads:[~2026-09-17 11:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 11:07 [PATCH v18 0/5] Add phy_get_by_of_node and devm helper Bryan O'Donoghue
2026-09-17 11:07 ` [PATCH v18 1/5] phy: core: Fix race-condition between _of_phy_get() and try_module_get() Bryan O'Donoghue
2026-09-17 11:07 ` [PATCH v18 2/5] phy: core: Add phy_get_by_of_node() Bryan O'Donoghue
2026-09-17 11:18   ` sashiko-bot [this message]
2026-09-17 12:29   ` Neil Armstrong
2026-09-17 12:32     ` Bryan O'Donoghue
2026-09-17 11:07 ` [PATCH v18 3/5] phy: core: Add devm_phy_get_by_of_node() Bryan O'Donoghue
2026-09-17 11:18   ` sashiko-bot
2026-09-17 12:32   ` Neil Armstrong
2026-09-17 12:43     ` Bryan O'Donoghue
2026-09-17 13:27     ` Bryan O'Donoghue
2026-09-17 15:03       ` Bryan O'Donoghue
2026-09-17 11:07 ` [PATCH v18 4/5] media: qcom: camss: Add support for PHY API devices Bryan O'Donoghue
2026-09-17 11:19   ` sashiko-bot
2026-09-17 11:07 ` [PATCH v18 5/5] media: qcom: camss: Use data-lanes starting at 1 for new CSIPHY mode Bryan O'Donoghue
2026-09-17 13:05   ` Loic Poulain

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=20260917111844.B28E31F000FF@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