Hi, On Mon, Oct 1, 2012 at 5:39 PM, Mark Brown <broo...@opensource.wolfsonmicro.com> wrote: > On Mon, Oct 01, 2012 at 05:23:15PM +0530, ABRAHAM, KISHON VIJAY wrote: >> On Mon, Oct 1, 2012 at 5:14 PM, Mark Brown > >> > No, this is not at all sensible - if there's an mfd_remove_devices() >> > function we really ought to be able to use it to remove the children. >> > If we can't do that we should fix the API usability, not open code the >> > same stuff in every user. > >> What makes more sense to me is extend mfd_add_devices to create child >> devices from dt data. Then for removing devices, one can use >> mfd_remove_devices(). > > Why would that be helpful? Most platforms don't support DT at all, and I'm not sure how to put it correctly. All I'm trying to tell is mfd is a framework that exposes a set of API's to create and remove a device among others. If a mfd child device is not created using mfd API, it'll be unfair to expect that child be removed properly using mfd API. Like in this patch, the device is created using of_platform_populate (not a mfd API) but is removed using mfd_remove_devices (mfd API) [which should result in an abort]. 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.
Thanks Kishon _______________________________________________ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss