Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-27 Thread Saravana Kannan
On Wed, Jun 26, 2019 at 2:31 PM Rob Herring wrote: > > On Mon, Jun 24, 2019 at 9:54 PM Greg Kroah-Hartman > wrote: > > > > On Mon, Jun 24, 2019 at 03:37:07PM -0700, Sandeep Patil wrote: > > > We are trying to make sure that all (most) drivers in an Aarch64 system > > > can > > > be kernel

Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-26 Thread Rob Herring
On Mon, Jun 24, 2019 at 9:54 PM Greg Kroah-Hartman wrote: > > On Mon, Jun 24, 2019 at 03:37:07PM -0700, Sandeep Patil wrote: > > We are trying to make sure that all (most) drivers in an Aarch64 system can > > be kernel modules for Android, like any other desktop system for > > example. There are

Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-25 Thread Frank Rowand
On 6/25/19 9:30 PM, Sandeep Patil wrote: > On Tue, Jun 25, 2019 at 11:53:13AM +0800, Greg Kroah-Hartman wrote: >> On Mon, Jun 24, 2019 at 03:37:07PM -0700, Sandeep Patil wrote: >>> We are trying to make sure that all (most) drivers in an Aarch64 system can >>> be kernel modules for Android, like

Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-25 Thread Sandeep Patil
On Tue, Jun 25, 2019 at 11:53:13AM +0800, Greg Kroah-Hartman wrote: > On Mon, Jun 24, 2019 at 03:37:07PM -0700, Sandeep Patil wrote: > > We are trying to make sure that all (most) drivers in an Aarch64 system can > > be kernel modules for Android, like any other desktop system for > > example.

Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-24 Thread Greg Kroah-Hartman
On Mon, Jun 24, 2019 at 03:37:07PM -0700, Sandeep Patil wrote: > We are trying to make sure that all (most) drivers in an Aarch64 system can > be kernel modules for Android, like any other desktop system for > example. There are a number of problems we need to fix before that happens > ofcourse.

Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-24 Thread Sandeep Patil
(Responding to the first email in the series to summarize the current situation and choices we have.) On Mon, Jun 03, 2019 at 05:32:13PM -0700, 'Saravana Kannan' via kernel-team wrote: > Add a generic "depends-on" property that allows specifying mandatory > functional dependencies between

Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-13 Thread Frank Rowand
Adding cc: David Collins Plus my comments below. On 6/3/19 5:32 PM, Saravana Kannan wrote: > Add a generic "depends-on" property that allows specifying mandatory > functional dependencies between devices. Add device-links after the > devices are created (but before they are probed) by looking at

Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-13 Thread Rob Herring
On Wed, Jun 12, 2019 at 3:21 PM Frank Rowand wrote: > > Adding cc: David Collins > > Plus my comments below. > > On 6/3/19 5:32 PM, Saravana Kannan wrote: > > Add a generic "depends-on" property that allows specifying mandatory > > functional dependencies between devices. Add device-links after

[RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-03 Thread Saravana Kannan
Add a generic "depends-on" property that allows specifying mandatory functional dependencies between devices. Add device-links after the devices are created (but before they are probed) by looking at this "depends-on" property. This property is used instead of existing DT properties that specify