All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo2@yeah.net>
To: Primoz Fiser <primoz.fiser@norik.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, upstream@lists.phytec.de
Subject: Re: [PATCH 1/2] arm64: dts: freescale: imx93-phyboard-nash: Add USB vbus regulators
Date: Mon, 20 Oct 2025 20:32:28 +0800	[thread overview]
Message-ID: <aPYr3DRVerHvWN0i@dragon> (raw)
In-Reply-To: <20250916080635.1520551-1-primoz.fiser@norik.com>

On Tue, Sep 16, 2025 at 10:06:34AM +0200, Primoz Fiser wrote:
> Add USB vbus regulators to silence the following kernel warnings:
> 
>   usb_phy_generic usbphynop1: dummy supplies not allowed for exclusive requests (id=vbus)
>   usb_phy_generic usbphynop2: dummy supplies not allowed for exclusive requests (id=vbus)
> 
> Because generic USB PHY driver requires exclusive vbus regulators since
> commit 75fd6485ccce ("usb: phy: generic: Get the vbus supply").
> 
> Signed-off-by: Primoz Fiser <primoz.fiser@norik.com>

Applied both, thanks!


      parent reply	other threads:[~2025-10-20 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  8:06 [PATCH 1/2] arm64: dts: freescale: imx93-phyboard-nash: Add USB vbus regulators Primoz Fiser
2025-09-16  8:06 ` [PATCH 2/2] arm64: dts: freescale: imx93-phyboard-segin: " Primoz Fiser
2025-09-18  9:41   ` Peng Fan
2025-09-18  9:41 ` [PATCH 1/2] arm64: dts: freescale: imx93-phyboard-nash: " Peng Fan
2025-10-20 12:32 ` Shawn Guo [this message]

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=aPYr3DRVerHvWN0i@dragon \
    --to=shawnguo2@yeah.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=primoz.fiser@norik.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=upstream@lists.phytec.de \
    /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.