On Sat, Dec 17, 2011 at 03:54:17PM +0000, Jonathan Cameron wrote: > On 12/16/2011 10:23 PM, Greg KH wrote: > > Rewriting all probe functions really shouldn't be hard as you have to > > just change from manipulating this list by-hand, to making a function > > call. That sounds like an easy thing to do, and something that should > > be done, right? > That plus add a level of indirection to every driver that currently > has any platform data (which covers the vast majority). Either > the array of consumers has to be added to their existing pd which is > clunky and driver specific or we have another structure with optional > consumer data and another level of platform data to pass in what the > driver actually cares about. Note throughout that we are passing data > that is completely irrelevant to the driver. We are doing all this > to support a usecase that isn't even relevant to many IIO drivers. FWIW the generic platform data embed thing is what the regulator API is currently doing, though of course we've got a bunch more data going in there in the constraints. This is actually a bit limiting as it means we need to know how things are glued together at registeration time, it'd be nice if we were able to add links in separately. -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
