All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Peter Chen <peter.chen@nxp.com>,
	"felipe.balbi@linux.intel.com" <felipe.balbi@linux.intel.com>,
	Marco Felsch <m.felsch@pengutronix.de>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH] ARM: imx25: provide a fixed regulator for usb phys
Date: Fri, 15 Nov 2019 10:07:57 +0100	[thread overview]
Message-ID: <20191115090757.usc753lq7uujtqyy@pengutronix.de> (raw)
In-Reply-To: <20190923102825.zemkconnvdibke5h@pengutronix.de>

Hello,

On Mon, Sep 23, 2019 at 12:28:25PM +0200, Uwe Kleine-König wrote:
> On Wed, Jul 24, 2019 at 03:09:39PM +0200, Uwe Kleine-König wrote:
> > On Thu, Jun 27, 2019 at 03:15:10AM +0000, Peter Chen wrote:
> > >  
> > > > On 19-06-26 02:40, Peter Chen wrote:
> > > > >
> > > > > > Subject: [PATCH] ARM: imx25: provide a fixed regulator for usb phys
> > > > > >
> > > > > > The usb phys are internal to the SoC and so it their 5V supply. With
> > > > > > this regulator added explicitly the following (harmless) boot messages go away:
> > > > > >
> > > > > > 	usb_phy_generic usbphy:usb-phy@0: usbphy:usb-phy@0 supply vcc not found, using dummy regulator
> > > > > > 	usb_phy_generic usbphy:usb-phy@1: usbphy:usb-phy@1 supply vcc not found, using dummy regulator
> > > > > >
> > > > >
> > > > > To eliminate the warning message, I suggest doing below changes, as
> > > > > vcc supply is not mandatory.
> > > > >
> > > > > diff --git a/drivers/usb/phy/phy-generic.c
> > > > > b/drivers/usb/phy/phy-generic.c index a53b89be5324..01a5ff1a0515
> > > > > 100644
> > > > > --- a/drivers/usb/phy/phy-generic.c
> > > > > +++ b/drivers/usb/phy/phy-generic.c
> > > > > @@ -275,7 +275,7 @@ int usb_phy_gen_create_phy(struct device *dev, struct usb_phy_generic *nop,
> > > > >                 }
> > > > >         }
> > > > >
> > > > > -       nop->vcc = devm_regulator_get(dev, "vcc");
> > > > > +       nop->vcc = devm_regulator_get_optional(dev, "vcc");
> > > > 
> > > > Is the regulator optional? IMHO this shouldn't be the fix. I think the right fix is Uwe's
> > > > approach.
> > > > 
> > > 
> > > Add Felipe.
> > > 
> > > Some USB PHY's power are from the core system's power (eg, DDR), and some are
> > > fixed at the board and no switch for it. So, it is transparent for software at some cases.
> > 
> > It's not clear to me how to proceed. There are two opposing opinions and
> > I don't know enough about USB on mx25 to judge myself.
> > 
> > Felipe?
> 
> This thread is still open in my inbox. Felipe, how can I lure you into
> giving your opinion?
> 
> My original suggestion can be seen at
> https://lore.kernel.org/linux-usb/20190625100412.11815-1-u.kleine-koenig@pengutronix.de/,
> Peter's alternative is still in the quotes above. Which is the
> right/better one?

The stuff said above is still true. I'd like to put this issue on file
with "fixed in mainline", but currently this seems to be a stalemate.
because nobody cares enough :-|

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

  reply	other threads:[~2019-11-15  9:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 10:04 [PATCH] ARM: imx25: provide a fixed regulator for usb phys Uwe Kleine-König
2019-06-25 10:44 ` Sergei Shtylyov
2019-06-26  2:40 ` Peter Chen
2019-06-26  5:54   ` Marco Felsch
2019-06-26  5:54     ` Marco Felsch
2019-06-27  3:15     ` Peter Chen
2019-07-24 13:09       ` Uwe Kleine-König
2019-07-24 13:09         ` Uwe Kleine-König
2019-09-23 10:28         ` Uwe Kleine-König
2019-11-15  9:07           ` Uwe Kleine-König [this message]
2021-10-21 11:02             ` Uwe Kleine-König

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=20191115090757.usc753lq7uujtqyy@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=devicetree@vger.kernel.org \
    --cc=felipe.balbi@linux.intel.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-imx@nxp.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=peter.chen@nxp.com \
    --cc=shawnguo@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 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.