public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kishon <kishon@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Roger Quadros <rogerq@ti.com>, <linux@arm.linux.org.uk>,
	<tony@atomide.com>, <gregkh@linuxfoundation.org>,
	<devicetree-discuss@lists.ozlabs.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<balbi@ti.com>, <eballetbo@gmail.com>, <javier@dowhile0.org>,
	<linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1 6/6] USB: MUSB: OMAP: get PHY by phandle for dt boot
Date: Tue, 22 Jan 2013 21:10:57 +0530	[thread overview]
Message-ID: <50FEB309.9040709@ti.com> (raw)
In-Reply-To: <50FEB275.80504@ti.com>

Hi,

On Tuesday 22 January 2013 09:08 PM, Peter Ujfalusi wrote:
> On 01/22/2013 04:21 PM, kishon wrote:
>> But it's better to check if deferred probing
>> takes place whenever a new driver is bound to a device as you just mentioned.
>
> Whenever you load (might be also when you unload) a driver the deferred
> modules will try to probe again. This is to check back if the dependency of
> the deferred modules has been fulfilled by the new driver or not.

Thanks Peter.

-Kishon

  reply	other threads:[~2013-01-22 15:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22  9:58 [PATCH v1 0/6] USB: Add support for multiple PHYs of same type Kishon Vijay Abraham I
2013-01-22  9:58 ` [PATCH v1 1/6] usb: otg: Add an API to bind the USB controller and PHY Kishon Vijay Abraham I
2013-01-22  9:58 ` [PATCH v1 2/6] usb: otg: utils: add facilities in phy lib to support multiple PHYs of same type Kishon Vijay Abraham I
2013-01-22 14:07   ` Roger Quadros
2013-01-22 14:13     ` kishon
2013-01-22  9:58 ` [PATCH v1 3/6] ARM: OMAP: USB: Add phy binding information Kishon Vijay Abraham I
2013-01-22  9:58 ` [PATCH v1 4/6] drivers: usb: musb: omap: make use of the new PHY lib APIs Kishon Vijay Abraham I
2013-01-22 14:09   ` Roger Quadros
2013-01-24 18:58     ` kishon
2013-01-22  9:58 ` [PATCH v1 5/6] usb: otg: add device tree support to otg library Kishon Vijay Abraham I
2013-01-22 10:36   ` Mark Rutland
2013-01-22 15:37     ` kishon
2013-01-22  9:58 ` [PATCH v1 6/6] USB: MUSB: OMAP: get PHY by phandle for dt boot Kishon Vijay Abraham I
2013-01-22 14:17   ` Roger Quadros
2013-01-22 14:37     ` kishon
2013-01-22 14:47       ` Roger Quadros
2013-01-22 15:21         ` kishon
2013-01-22 15:38           ` Peter Ujfalusi
2013-01-22 15:40             ` kishon [this message]
2013-01-22 15:41 ` [PATCH v1 0/6] USB: Add support for multiple PHYs of same type Koen Kooi
2013-01-22 15:45   ` kishon
2013-01-22 16:16     ` kishon
2013-01-22 17:02       ` Koen Kooi
2013-01-23  5:19         ` kishon
2013-01-23 13:58         ` Mohammed, Afzal
2013-01-23 14:26           ` kishon
2013-01-24 11:51             ` Mohammed, Afzal
2013-01-25 14:46               ` Mohammed, Afzal

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=50FEB309.9040709@ti.com \
    --to=kishon@ti.com \
    --cc=balbi@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=eballetbo@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=javier@dowhile0.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=peter.ujfalusi@ti.com \
    --cc=rogerq@ti.com \
    --cc=tony@atomide.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