On Thu, Apr 26, 2007 at 02:02:16AM +0000, Arnd Bergmann wrote:
On Thursday 26 April 2007, Mark A. Greer wrote:
quoted
quoted
location is the smaller part of the problem. Even if it was the right
thing to scan the tree and then create platform_data instead of using
the of_device, that code would still belong into the device driver.
I don't think of_device is going to work very well on MIPS.
Ok, I see your point there. But after looking at the i2c and net drivers,
I believe that they can easily be split into an architecture dependent
part that is either an of_platform_driver or a platform_driver, and
a common part that does not know about either of these.
Oh, it's certainly possible, but it doesn't seem desirable to me. Why
should the drivers carry the burden of supporting both platform_driver
and of_platform_driver interfaces?
-Dale