Hi Pawel, On Wed, Jul 17, 2013 at 03:20:11PM +0100, Pawel Moll wrote: > On Wed, 2013-07-17 at 15:16 +0100, Nicolas Pitre wrote: > > On Wed, 17 Jul 2013, Pawel Moll wrote: > > > > > On Wed, 2013-07-17 at 13:33 +0100, Nicolas Pitre wrote: > > > > If this is really miscelaneous code that really doesn't fit > > > > anywhere else, it should rather go into drivers/misc/ as a last resort. > > > > > > Interestingly enough drivers/misc was my first choice for all the > > > vexpress stuff, but it wasn't received well... > > > > > > Anyway, the SPC driver as it is now seem to be a "power management > > > system driver". Maybe a relevant directory would be in place? Wouldn't > > > PSCI belong there as well? (there are two psci.c files in arch/arm and > > > arch/arm64, surprisingly similar ones ;-) > > > > > > The bottom line is: today it is not an MFD driver. > > > > But we know it will, right? So better save some churn by storing the > > initial code where it would end up anyway once complete. > > Not in that form, no. The code living in mfd will just register > mfd_cells while "functional" parts are going to live elsewhere. This is > how I understand what Samuel asked me to do and that's what is happening > to vexpress-sysreg now. Very good, I'll happily apply such changes. If I understand the IP correctly, the SPC driver will stay as a set of runtime APIs for controlling the SPC features. If that's the case, then misc sounds like a more appropriate place for this driver. drivers/power/ really is for power supplies and charging drivers.
Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/