From mboxrd@z Thu Jan 1 00:00:00 1970 From: pawel.moll@arm.com (Pawel Moll) Date: Wed, 17 Jul 2013 15:20:11 +0100 Subject: [RFC PATCH v5 0/1] drivers: mfd: Versatile Express SPC support In-Reply-To: References: <1373990743-23106-1-git-send-email-lorenzo.pieralisi@arm.com> <1374052705.3146.86.camel@hornet> <1374067786.3146.123.camel@hornet> Message-ID: <1374070811.3146.124.camel@hornet> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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. Pawe?