On Tue, Jul 23, 2019 at 3:18 PM Rob Herring wrote:
>
> On Tue, Jul 23, 2019 at 2:49 PM Saravana Kannan wrote:
> >
> > On Tue, Jul 23, 2019 at 11:06 AM Rob Herring wrote:
> > >
> > > On Sat, Jul 20, 2019 at 12:17 AM Saravana Kannan
> > > wrote:
> > > >
> > > > Add device-links after the devices
On Tue, Jul 23, 2019 at 2:49 PM Saravana Kannan wrote:
>
> On Tue, Jul 23, 2019 at 11:06 AM Rob Herring wrote:
> >
> > On Sat, Jul 20, 2019 at 12:17 AM Saravana Kannan
> > wrote:
> > >
> > > Add device-links after the devices are created (but before they are
> > > probed) by looking at common D
On Tue, Jul 23, 2019 at 11:06 AM Rob Herring wrote:
>
> On Sat, Jul 20, 2019 at 12:17 AM Saravana Kannan wrote:
> >
> > Add device-links after the devices are created (but before they are
> > probed) by looking at common DT bindings like clocks and
> > interconnects.
>
> The structure now looks a
On Sat, Jul 20, 2019 at 12:17 AM Saravana Kannan wrote:
>
> Add device-links after the devices are created (but before they are
> probed) by looking at common DT bindings like clocks and
> interconnects.
The structure now looks a lot better to me. A few minor things below.
>
> Automatically addi
Add device-links after the devices are created (but before they are
probed) by looking at common DT bindings like clocks and
interconnects.
Automatically adding device-links for functional dependencies at the
framework level provides the following benefits:
- Optimizes device probe order and avoi
