On Fri, Sep 26, 2008 at 10:12:27AM -0700, David Brownell wrote: > Let's apply the following patch 10/9 on top of this though. > And probably update the board files similarly (alpha order). > > As an FYI, if you look at the "MFD core" you'll observe that > if some crap gets stripped away, the *useful* bit is a utility > making some of this create-a-child-node easier. It's not worth > using now. But a little bird told me that some of that crap > may be getting stripped away soon, so add_children() could > become simpler. Wouldn't affect the function drivers (the > OTG transceiver, keypad, GPIO, RTC, etc) because we have, with > foresight, been using platform_device already. ;) I was trying to organize by order of importance to a running system. If we run out of memory when registering the madc child, that should be ok, but if we run out of memory when registering rtc, that might cause some problems, right ? If you prefer in alphabetic order, it's no problem, I'll fix that ;-) -- balbi -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
