On Tue, Jul 2, 2019 at 5:59 PM Saravana Kannan wrote:
>
> On Tue, Jul 2, 2019 at 5:03 PM David Collins wrote:
> >
> > Hello Saravana,
> >
> > On 7/1/19 5:48 PM, Saravana Kannan wrote:
> > ...
> > > TODO:
> > > - For the case of consumer child sub-nodes being added by a parent
> > > device after
On Tue, Jul 2, 2019 at 5:03 PM David Collins wrote:
>
> Hello Saravana,
>
> On 7/1/19 5:48 PM, Saravana Kannan wrote:
> ...
> > TODO:
> > - For the case of consumer child sub-nodes being added by a parent
> > device after late_initcall_sync we might be able to address that by
> > recursively p
Hello Saravana,
On 7/1/19 5:48 PM, Saravana Kannan wrote:
...
> TODO:
> - For the case of consumer child sub-nodes being added by a parent
> device after late_initcall_sync we might be able to address that by
> recursively parsing all child nodes and adding all their suppliers as
> suppliers
Add device-links to track functional dependencies between devices
after they are created (but before they are probed) by looking at
their common DT bindings like clocks, interconnects, etc.
Having functional dependencies automatically added before the devices
are probed, provides the following ben
4 matches
Mail list logo