Hi, 2008/1/19, Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>: > On Fri, Jan 18, 2008 at 06:11:45PM +0000, Dmitry Baryshkov wrote: > > Dmitry Torokhov wrote: > > > > I will need some more time to review and understand the need for the new > > > bus in the driver. > > > Most likely this can be converted to platform_bus. Maybe this can also get > > Could you expand on how you see that being implemented, please? It > doesn't feel entirely comfortable to me - providing a bus for the chip > seems more direct and the platform bus not what I'd think of using for > something hanging off another bus - but I think I'm just not visualising > what you're thinking of properly. Well... It's a common suggestion not to duplicate code. The wm97xx bus looks mostly like platform. The only difference is the name. To help visualisation, devices can have parents. Just set (in pseudocode) wm97xx-touchscreen->parent to wm97xx, do the same for wm97xx-battery and so on. Thus all devices would be on the platform device but with proper parent <-> child notation. > > help from soon-to-be posted MFD (multi function devices) helpers. > > The multi-function device support does feel like it could be a good fit. > I'd seen it discussed sometime last year but don't recall seeing > anything for quite a while. Like Ben said, any pointers to current work > would be appreciated. You can find the current work at git://git.mnementh.co.uk/linux-2.6-im.git#tmio_dev_try3. Look for "Core MFD support" changeset. > > It's probably worth mentioning that in addition to what is in the > current patch series these chips all also provide an audio codec which > requires a reasonably substantial driver for full support. > This would only touch child devices organisation. -- With best wishes Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
