On Mon, Oct 10, 2011 at 12:44:08PM +0100, Mark Brown wrote: > On Mon, Oct 10, 2011 at 01:42:30PM +0200, Zoltan Devai wrote: > > > Where should the adc driver go in this case ? > > At the minute it seems to me that arch/arm is as good a place as any > really - currently this code is getting dumped wherever the main device > is. No it isn't - we want drivers out of arch/arm (it's already been a topic of flame for Linus, so it's something that we should try _really_ hard to avoid.) As this is clearly a device driver (it has a device driver struct, it relies upon a struct device, etc) then it needs to live outside of arch/arm/ - and I think Arnd's suggestion of drivers/adc is probably the right place for it to move to (even though its probably the first to create the directory.) More stuff can come along in the future, and then its all together to start creating a common API in there. The other thing I'd say is that things like the callback definitions and driver data should not be in some arch/arm/ include file - if it's private to the ADC, it should go in drivers/adc too. If not, then somewhere in include/linux (maybe include/linux/adc) is a better place. What we *do* need to avoid is having the spmp8000 ADC callback function data structure, the foo ADC callback function data structure, the bar ADC callback function data structure and so forth. We need to think *NOW* about defining a common ADC callback structure so that we don't spawn a new problem which'll take effort to solve. -- 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
