mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Peter Chen <peter.chen@nxp.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v3] usb: chipidea: Grab the (legacy) USB PHY by phandle first
Date: Thu, 21 Feb 2019 11:48:37 +0100	[thread overview]
Message-ID: <9e2e22ea7c7a8974764d45f2f84c4f599f5aee61.camel@bootlin.com> (raw)
In-Reply-To: <VI1PR04MB5327CA438A1EAA5BB99E91188B7E0@VI1PR04MB5327.eurprd04.prod.outlook.com>

Hi,

On Thu, 2019-02-21 at 09:30 +0000, Peter Chen wrote:
>  
> > > Current code w/o your patch, it is possible both ci->phy and
> > > ci->usb_phy are valid if the USB PHY is not at the device tree, but generic PHY is
> > at the device tree.
> > > If you don't want to fix this issue with this patch, it is ok too. We could fix it later.
> > 
> > I'm not sure I understand the issue. With my patch, if there is a generic PHY
> > described in device-tree, then devm_usb_get_phy_by_phandle for legacy PHY will
> > fail and the code will fallback to devm_usb_get_phy, which is the same behavior as
> > before.
> > 
> 
> You are right, but this behavior is incorrect since each controller has only one physical
> USB PHY.
> 
> > Is it a problem that we can end up with both a generic and legacy PHY?
> > I thought this was expected behavior at probe, and the rest of the code will just use
> > the generic one in priority.
> > 
> > Do you want to make it so that only one (generic or legacy) PHY remains after
> > probe?
> > 
>  
> Yes, I just want only one valid, either ci->phy or ci->usb_phy, it makes sense.

Sounds good to me. I'll send out v4 with this patch and an extra one to
refactor the PHY selection path and only attempt to get a single PHY.

Cheers,

Paul

-- 
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com


      reply	other threads:[~2019-02-21 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 16:22 Paul Kocialkowski
2019-02-18  3:04 ` Peter Chen
2019-02-18  8:32   ` Paul Kocialkowski
2019-02-21  3:29     ` Peter Chen
2019-02-21  8:22       ` Paul Kocialkowski
2019-02-21  8:37         ` Peter Chen
2019-02-21  8:44           ` Paul Kocialkowski
2019-02-21  9:30             ` Peter Chen
2019-02-21 10:48               ` Paul Kocialkowski [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=9e2e22ea7c7a8974764d45f2f84c4f599f5aee61.camel@bootlin.com \
    --to=paul.kocialkowski@bootlin.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.chen@nxp.com \
    --cc=thomas.petazzoni@bootlin.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

all inboxes | Powered by JetHome®