linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@nxp.com>
To: Fabien Lahoudere <fabien.lahoudere@collabora.co.uk>,
	Peter Chen <hzpeterchen@gmail.com>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
	Peter Senna Tschudin <peter.senna@collabora.com>,
	Felipe Balbi <balbi@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"open list:USB PHY LAYER" <linux-usb@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: RE: [RFC] usb-phy-generic: Add support to SMSC USB3315
Date: Fri, 9 Jun 2017 08:26:28 +0000	[thread overview]
Message-ID: <HE1PR04MB1450BD44697BCE7777459AEF8BCE0@HE1PR04MB1450.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1496924821.22734.15.camel@collabora.co.uk>

 
>
>I have a look at your patches (http://www.spinics.net/lists/linux-usb/msg157134.html)
>and I wonder if power sequence is applicable only on hub node?

No, power sequence can be used for any devices which needs to carry out power on
before probe.

> hub are probed too
>late (after ci_ulpi_init). Do you think it is possible to read a power sequence in dts
>from ci_ulpi_init?
>

I think the suitable place for power sequence is at ulpi_of_register, some ULPI PHYs
need to carry out power on before reading ID.

Peter

  reply	other threads:[~2017-06-09  8:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19  6:14 [RFC] usb-phy-generic: Add support to SMSC USB3315 Peter Senna Tschudin
2017-04-19 10:03 ` Sergei Shtylyov
2017-04-19 10:24   ` Peter Senna Tschudin
2017-04-19 17:23     ` Sergei Shtylyov
2017-04-20  8:50 ` Peter Chen
2017-05-23 18:16   ` Fabien Lahoudere
2017-05-23 21:00     ` Stephen Boyd
2017-05-25 10:36       ` Fabien Lahoudere
2017-05-26  9:00         ` Fabien Lahoudere
2017-06-02 22:00           ` Stephen Boyd
2017-06-05  8:57             ` Fabien Lahoudere
2017-06-05  9:43               ` Peter Chen
2017-06-05  9:52                 ` Fabien Lahoudere
2017-06-06  1:55                   ` Peter Chen
2017-06-06 17:36                     ` Fabien Lahoudere
2017-06-07  1:43                       ` Peter Chen
2017-06-07 15:00                         ` Fabien Lahoudere
2017-06-08 12:27                         ` Fabien Lahoudere
2017-06-09  8:26                           ` Peter Chen [this message]
2017-06-09 11:17                             ` Fabien Lahoudere
2017-06-12  1:20                               ` Peter Chen

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=HE1PR04MB1450BD44697BCE7777459AEF8BCE0@HE1PR04MB1450.eurprd04.prod.outlook.com \
    --to=peter.chen@nxp.com \
    --cc=balbi@kernel.org \
    --cc=fabien.lahoudere@collabora.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hzpeterchen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.senna@collabora.com \
    --cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).