Am 18.05.2014 16:59, schrieb Grant Likely:
Hi Tomasz,
Thanks for weighing in on this. Thoughts and comments below.
On Sat, 17 May 2014 16:24:19 +0200, Tomasz Figa wrote:
registration order. Alexander had to hook into the driver registration
patch to get the optimal probe order. For device o
Hi Tomasz,
Thanks for weighing in on this. Thoughts and comments below.
On Sat, 17 May 2014 16:24:19 +0200, Tomasz Figa wrote:
> Hi,
>
> On 14.05.2014 16:05, Grant Likely wrote:
> > On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
> > wrote:
> >> Use the properties named 'dependencies' in
Am 16.05.2014 13:00, schrieb Grant Likely:
On Wed, 14 May 2014 23:10:39 +0200, Alexander Holler
wrote:
Am 14.05.2014 22:06, schrieb Grant Likely:
On Wed, 14 May 2014 16:49:05 +0200, Alexander Holler
wrote:
Am 14.05.2014 16:05, schrieb Grant Likely:
On Mon, 12 May 2014 18:47:53 +0200, Alex
Hi,
On 14.05.2014 16:05, Grant Likely wrote:
> On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
> wrote:
>> Use the properties named 'dependencies' in binary device tree blobs to build
>> a dependency based initialization order for platform devices and drivers.
>>
>> This is done by building
Wed, 14 May 2014 23:10:39 +0200 от Alexander Holler :
> Am 14.05.2014 22:06, schrieb Grant Likely:
> > On Wed, 14 May 2014 16:49:05 +0200, Alexander Holler
> > wrote:
> >> Am 14.05.2014 16:05, schrieb Grant Likely:
> >>> On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
> >>> wrote:
>
> >>
On Wed, 14 May 2014 23:10:39 +0200, Alexander Holler
wrote:
> Am 14.05.2014 22:06, schrieb Grant Likely:
> > On Wed, 14 May 2014 16:49:05 +0200, Alexander Holler
> > wrote:
> >> Am 14.05.2014 16:05, schrieb Grant Likely:
> >>> On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
> >>> wrote:
Am 14.05.2014 22:06, schrieb Grant Likely:
> On Wed, 14 May 2014 16:49:05 +0200, Alexander Holler
> wrote:
>> Am 14.05.2014 16:05, schrieb Grant Likely:
>>> On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
>>> wrote:
>> Hmm, I don't really care if that will be merged. I have no motivation
On Wed, 14 May 2014 16:49:05 +0200, Alexander Holler
wrote:
> Am 14.05.2014 16:05, schrieb Grant Likely:
> > On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
> > wrote:
> >> Use the properties named 'dependencies' in binary device tree blobs to
> >> build
> >> a dependency based initializa
Am 14.05.2014 16:49, schrieb Alexander Holler:
Am 14.05.2014 16:05, schrieb Grant Likely:
On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
wrote:
Personally, I think the parts of this patch that manipulate the device
registration
order is entirely the wrong way to handle it. If anything,
Am 14.05.2014 16:05, schrieb Grant Likely:
+
+ if (graph.finished)
+ return -EINVAL; /* cycle found */
+
+ /* of_init_print_order(); */
If you wrap of_init_print_order with a #ifdef DEBUG/#else/#endif, then
you don't need to comment out the call to of_init_print_order
Am 14.05.2014 16:05, schrieb Grant Likely:
On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
wrote:
Use the properties named 'dependencies' in binary device tree blobs to build
a dependency based initialization order for platform devices and drivers.
This is done by building a directed acy
On Mon, 12 May 2014 18:47:53 +0200, Alexander Holler
wrote:
> Use the properties named 'dependencies' in binary device tree blobs to build
> a dependency based initialization order for platform devices and drivers.
>
> This is done by building a directed acyclic graph using an adjacency list
> a
Use the properties named 'dependencies' in binary device tree blobs to build
a dependency based initialization order for platform devices and drivers.
This is done by building a directed acyclic graph using an adjacency list
and doing a topological sort to retrieve the order in which devices/drive
13 matches
Mail list logo
