Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-08-10 Thread Sodagudi Prasad
probe retry cycle after every initcall level To: Rishabh Bhatnagar Cc: "Rafael J. Wysocki" , Greg Kroah-Hartman , Linux Kernel Mailing List , ckad...@codeaurora.org, ts...@codeaurora.org, Vikram Mulukutla On Wed, Aug 1, 2018 at 11:18 PM, wrote: On 2018-07-24 01:24, Rafael J. Wys

Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-08-10 Thread Rafael J. Wysocki
On Fri, Aug 10, 2018 at 12:30 AM, wrote: > On 2018-08-06 01:53, Rafael J. Wysocki wrote: >> >> On Fri, Aug 3, 2018 at 12:20 AM, Sodagudi Prasad >> wrote: >>>> >>>> From: RAFAEL J. WYSOCKI >>>> Date: Wed, Aug 1, 2018 at 2:21 PM >>

Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-08-09 Thread rishabhb
On 2018-08-06 01:53, Rafael J. Wysocki wrote: On Fri, Aug 3, 2018 at 12:20 AM, Sodagudi Prasad wrote: From: RAFAEL J. WYSOCKI Date: Wed, Aug 1, 2018 at 2:21 PM Subject: Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level To: Rishabh Bhatnagar Cc: "Rafael J. Wy

Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-08-06 Thread Rafael J. Wysocki
On Fri, Aug 3, 2018 at 12:20 AM, Sodagudi Prasad wrote: >> From: RAFAEL J. WYSOCKI >> Date: Wed, Aug 1, 2018 at 2:21 PM >> Subject: Re: [PATCH] dd: Invoke one probe retry cycle after every >> initcall level >> To: Rishabh Bhatnagar >> Cc: "Rafael J.

Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-08-02 Thread Sodagudi Prasad
From: RAFAEL J. WYSOCKI Date: Wed, Aug 1, 2018 at 2:21 PM Subject: Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level To: Rishabh Bhatnagar Cc: "Rafael J. Wysocki" , Greg Kroah-Hartman , Linux Kernel Mailing List , ckad...@codeaurora.org, ts...@codeaurora.o

Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-08-01 Thread Rafael J. Wysocki
On Wed, Aug 1, 2018 at 11:18 PM, wrote: > On 2018-07-24 01:24, Rafael J. Wysocki wrote: >> >> On Mon, Jul 23, 2018 at 10:22 PM, wrote: >>> >>> On 2018-07-23 04:17, Rafael J. Wysocki wrote: On Thu, Jul 19, 2018 at 11:24 PM, Rishabh Bhatnagar wrote: > > > Drivers

Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-08-01 Thread rishabhb
On 2018-07-24 01:24, Rafael J. Wysocki wrote: On Mon, Jul 23, 2018 at 10:22 PM, wrote: On 2018-07-23 04:17, Rafael J. Wysocki wrote: On Thu, Jul 19, 2018 at 11:24 PM, Rishabh Bhatnagar wrote: Drivers that are registered at an initcall level may have to wait until late_init before the prob

Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-07-24 Thread Rafael J. Wysocki
On Mon, Jul 23, 2018 at 10:22 PM, wrote: > On 2018-07-23 04:17, Rafael J. Wysocki wrote: >> >> On Thu, Jul 19, 2018 at 11:24 PM, Rishabh Bhatnagar >> wrote: >>> >>> Drivers that are registered at an initcall level may have to >>> wait until late_init before the probe deferral mechanism can >>> r

Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-07-23 Thread rishabhb
On 2018-07-23 04:17, Rafael J. Wysocki wrote: On Thu, Jul 19, 2018 at 11:24 PM, Rishabh Bhatnagar wrote: Drivers that are registered at an initcall level may have to wait until late_init before the probe deferral mechanism can retry their probe functions. It is possible that their dependencies

Re: [PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-07-23 Thread Rafael J. Wysocki
On Thu, Jul 19, 2018 at 11:24 PM, Rishabh Bhatnagar wrote: > Drivers that are registered at an initcall level may have to > wait until late_init before the probe deferral mechanism can > retry their probe functions. It is possible that their > dependencies were resolved much earlier, in some cases

[PATCH] dd: Invoke one probe retry cycle after every initcall level

2018-07-19 Thread Rishabh Bhatnagar
Drivers that are registered at an initcall level may have to wait until late_init before the probe deferral mechanism can retry their probe functions. It is possible that their dependencies were resolved much earlier, in some cases even before the next initcall level. Invoke one probe retry cycle a