Messages in this thread | | | From | Arnd Bergmann <> | Subject | Re: [PATCH v4 01/11] mfd: add pruss mfd driver. | Date | Mon, 23 May 2011 17:13:48 +0200 |
| |
Hi Samuel,
On Sunday 22 May 2011, Samuel Ortiz wrote: > On Wed, May 11, 2011 at 10:03:54PM +0200, Arnd Bergmann wrote: > > On Wednesday 11 May 2011, Subhasish Ghosh wrote: > > We had a little discussion at the Linaro Developer Summit about your > > driver and mfd drivers in general. There was a general feeling among > > some people (including me) that by the point you dynamically create > > the subdevices, MFD is probably not the right abstraction any more, > > as it does not provide any service that you need. > I agree it's not what it's been designed for. > > > > Instead, maybe you can simply call platform_device_register > > at that stage to create the children and not use MFD at all. > The MFD APIs are slightly easier to use though, imho. > > > > Samuel, can you comment on this as well? Do you still see pruss > > as an MFD driver when the uses are completely dynamic and determined > > by the firmware loaded into it? > Even though that is definitely not a typical MFD use case, I wouldn't object > strongly against it. Right now mfd is probably the least worst choice for this > kind of drivers, which still doesn't make it an ideal situation.
Thanks for your input! When you say that MFD APIs are easier to use than platform_device APIs, is that something we should fix with platform devices to make them easier to use?
Arnd
| |