Hi, coming late to the discussion, so bear with me On Tue, Oct 02, 2012 at 01:38:56PM +0100, Mark Brown wrote: > > This means mfd framework does not have an API to create a device from > > dt data or so do I think since of_platform_populate() is used. Thats > > why I suggested the idea of extending mfd_add_devices() (or adding a > > new API in mfd framework) to create child devices from dt data so that > > we'll have API's in mfd framework to both create and delete a device. > > The trouble that always exists with representing MFD children in DT is > that unless you've got a usefully reusable IP block which is clearly > separate from the chip integration you end up essentially just dumping > the Linux data structures into DT which often doesn't leave you with > something which describes the hardware. do you mean to say that children creation should be left into the driver (outside dt) ? That should be doable, indeed. BTW, OTOH writing all children into the DT actually describes the HW, no ? And depending on the device I feel it'd be better to write that data to DT. Think of twlxxxx (TI's PMICs), we might have completely unrelated drivers using one of TWL's GPIO lines as an interrupt source. If that particular children isn't listed in DT, it can't be used as an interrupt-parent, right ? -- balbi
Attachment:
signature.asc
Description: Digital signature
