From: "Lu, Baolu" <baolu.lu@linux.intel.com>
To: David Cohen <david.a.cohen@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
balbi@ti.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, qiuxu.zhuo@intel.com
Subject: Re: [PATCH v4 1/1] usb: ulpi: ulpi_init should be executed in subsys_initcall
Date: Thu, 28 May 2015 08:50:12 +0800 [thread overview]
Message-ID: <55666644.1060305@linux.intel.com> (raw)
In-Reply-To: <20150527165327.GB1028@psi-dev26.jf.intel.com>
On 05/28/2015 12:53 AM, David Cohen wrote:
> Hi,
>
> On Tue, May 26, 2015 at 07:37:02PM -0700, Greg Kroah-Hartman wrote:
>> On Wed, May 27, 2015 at 09:45:37AM +0800, Lu Baolu wrote:
>>> Phy drivers and the ulpi interface providers depend on the
>>> registration of the ulpi bus. Ulpi registers the bus in
>>> module_init(). This could cause unnecessary probe delays.
>> What do you mean by "probe delays"?
> I believe he meant the bus users' probe delays. i.e. unnecessary
> -EPROBE_DEFER happening on ulpi_drivers in case they're registered
> before ulpi bus itself.
>
> Is that correct, Baolu?
Yes.
>
> Br, David
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2015-05-28 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 1:45 [PATCH v4 1/1] usb: ulpi: ulpi_init should be executed in subsys_initcall Lu Baolu
2015-05-27 2:37 ` Greg Kroah-Hartman
2015-05-27 16:53 ` David Cohen
2015-05-28 0:50 ` Lu, Baolu [this message]
2015-06-04 12:17 ` Heikki Krogerus
2015-06-04 12:31 ` Lu, Baolu
2015-05-27 2:37 ` Greg Kroah-Hartman
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=55666644.1060305@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=balbi@ti.com \
--cc=david.a.cohen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=qiuxu.zhuo@intel.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 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.