[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fa686aa40905271354y50b9583cp9f53c35354edc285@mail.gmail.com>
Date: Wed, 27 May 2009 14:54:10 -0600
From: Grant Likely <grant.likely@...retlab.ca>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
devicetree-discuss <devicetree-discuss@...abs.org>,
linux-kernel@...r.kernel.org, Timur Tabi <timur@...escale.com>,
Jon Smirl <jonsmirl@...il.com>,
Scott Wood <scottwood@...escale.com>,
Janboe Ye <yuan-bo.ye@...orola.com>,
linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [RFC] [PATCH] Device Tree on ARM platform
On Wed, May 27, 2009 at 2:19 PM, Jean-Christophe PLAGNIOL-VILLARD
<plagnioj@...osoft.com> wrote:
>> One option that has been suggested (more than once) is to make the
>> adapter code an of_platform_driver which translates the device tree
>> data and then registers the appropriate platform_devices. This neatly
>> solves the problem, but I don't like the overhead involved in
>> registering 2 struct devices with the kernel for every device node in
>> the device tree.
> but simplify the dev and maintaining is also an important goal.
>
> Have to duplicated ressource handling via ifdef in every drivers is also an
> overhead which need to be avoided
agreed. I don't have a best of both worlds answer here.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists