Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Brown <broonie@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Rob Herring <robh@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	devicetree@vger.kernel.org, linux-phy@lists.infradead.org,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 9/9] arm64: dts: renesas: ebisu: Describe PCIe/USB3.0 clock generator
Date: Thu, 22 Jan 2026 11:56:48 +0100	[thread overview]
Message-ID: <f577f6a3-0239-4f73-9d4a-60d4dea64955@mailbox.org> (raw)
In-Reply-To: <CAMuHMdX0iuyUhGRPFf4x==e_ZEMjaB_dP6mrM81F+yxqwam0FA@mail.gmail.com>

On 1/22/26 11:24 AM, Geert Uytterhoeven wrote:

Hello Geert,

>> This piece of code in drivers/usb/phy/phy-generic.c [1] shouldn't fail
>> the probe if "vbus-supply" property is not present in DT. If
>> "vbus-supply" property is not present in DT, then
>> PTR_ERR(nop->vbus_draw) == -ENODEV is true, nop->vbus_draw will be set
>> to NULL, but won't encode error, so the dev_err_probe() won't trigger.
>>
>> "
>> 259         nop->vbus_draw = devm_regulator_get_exclusive(dev, "vbus");
>> 260         if (PTR_ERR(nop->vbus_draw) == -ENODEV)
>> 261                 nop->vbus_draw = NULL;
>> 262         if (IS_ERR(nop->vbus_draw))
>> 263                 return dev_err_probe(dev, PTR_ERR(nop->vbus_draw),
>> 264                                      "could not get vbus regulator\n");
>> "
>>
>> [1]
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/phy/phy-generic.c#n259
> 
> Sorry, you are right. I missed the PHY driver ignores the error and
> probes successfully, and thus didn't bother doing "echo ee000000.usb >
> /sys/bus/platform/drivers/xhci-renesas-hcd/bind" after /lib/firmware
> became available.

Is any change needed to this series then ?

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

  reply	other threads:[~2026-01-22 13:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18 13:49 [PATCH v2 0/9] Describe PCIe/USB3.0 clock generator on R-Car Gen3 Marek Vasut
2026-01-18 13:49 ` [PATCH v2 1/9] arm64: dts: renesas: r8a77951: Describe PCIe root ports Marek Vasut
2026-01-23 13:29   ` Geert Uytterhoeven
2026-01-18 13:49 ` [PATCH v2 2/9] arm64: dts: renesas: r8a77960: " Marek Vasut
2026-01-23 13:29   ` Geert Uytterhoeven
2026-01-18 13:49 ` [PATCH v2 3/9] arm64: dts: renesas: r8a77961: " Marek Vasut
2026-01-23 13:30   ` Geert Uytterhoeven
2026-01-18 13:49 ` [PATCH v2 4/9] arm64: dts: renesas: r8a77965: " Marek Vasut
2026-01-23 13:31   ` Geert Uytterhoeven
2026-01-18 13:49 ` [PATCH v2 5/9] arm64: dts: renesas: r8a77990: Describe PCIe root port Marek Vasut
2026-01-23 13:31   ` Geert Uytterhoeven
2026-01-18 13:49 ` [PATCH v2 6/9] arm64: dts: renesas: r8a77990: Add USB 3.0 PHY and USB3S0 clock nodes Marek Vasut
2026-01-23 13:32   ` Geert Uytterhoeven
2026-01-18 13:49 ` [PATCH v2 7/9] arm64: dts: renesas: salvator-common: Describe PCIe/USB3.0 clock generator Marek Vasut
2026-01-23 13:34   ` Geert Uytterhoeven
2026-01-18 13:49 ` [PATCH v2 8/9] arm64: dts: renesas: ulcb: ulcb-kf: " Marek Vasut
2026-01-23 13:37   ` Geert Uytterhoeven
2026-01-23 15:02     ` Marek Vasut
2026-01-18 13:49 ` [PATCH v2 9/9] arm64: dts: renesas: ebisu: " Marek Vasut
2026-01-21 13:48   ` Geert Uytterhoeven
2026-01-21 17:38     ` Marek Vasut
2026-01-22 10:24       ` Geert Uytterhoeven
2026-01-22 10:56         ` Marek Vasut [this message]
2026-01-23 13:39   ` Geert Uytterhoeven

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=f577f6a3-0239-4f73-9d4a-60d4dea64955@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=yoshihiro.shimoda.uh@renesas.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