On Mon, Jul 23, 2012 at 12:49:11PM +0200, Andrew Lunn wrote:

There is no logic in the board code to first try DT, and if that
fails, use old fashioned platform_device instantiating of the drivers.

Well, I'd really expect this to be done the other way around.

I've also had bad experiences when we have the old platform_device
instantiating plus DT also instantiating the same device.

Hopefully we can arrange for them to collide with each other...

The only way i've found to convert an existing board from
platform_device to DT is to first add DT support to the driver, and
then atomically swap platform_device structures for DT descriptions.

I guess if it's not working then we need to do that, but it's really sad
that the DT deployment is this painful.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120723/0dd23d02/attachment.sig>