From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v5 0/1] drivers: mfd: Versatile Express SPC support
Date: Wed, 17 Jul 2013 15:20:11 +0100 [thread overview]
Message-ID: <1374070811.3146.124.camel@hornet> (raw)
In-Reply-To: <alpine.LFD.2.03.1307171014510.14924@syhkavp.arg>
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?
WARNING: multiple messages have this Message-ID (diff)
From: Pawel Moll <pawel.moll@arm.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Olof Johansson <olof@lixom.net>,
Amit Kucheria <amit.kucheria@linaro.org>,
Jon Medhurst <tixy@linaro.org>, Achin Gupta <Achin.Gupta@arm.com>,
Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
Subject: Re: [RFC PATCH v5 0/1] drivers: mfd: Versatile Express SPC support
Date: Wed, 17 Jul 2013 15:20:11 +0100 [thread overview]
Message-ID: <1374070811.3146.124.camel@hornet> (raw)
In-Reply-To: <alpine.LFD.2.03.1307171014510.14924@syhkavp.arg>
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ł
next prev parent reply other threads:[~2013-07-17 14:20 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 16:05 [RFC PATCH v5 0/1] drivers: mfd: Versatile Express SPC support Lorenzo Pieralisi
2013-07-16 16:05 ` Lorenzo Pieralisi
2013-07-16 16:05 ` [RFC PATCH v5 1/1] drivers: mfd: vexpress: add Serial Power Controller (SPC) support Lorenzo Pieralisi
2013-07-16 16:05 ` Lorenzo Pieralisi
2013-07-16 16:05 ` Lorenzo Pieralisi
2013-07-16 20:05 ` Rob Herring
2013-07-16 20:05 ` Rob Herring
2013-07-16 23:32 ` Nicolas Pitre
2013-07-16 23:32 ` Nicolas Pitre
2013-07-17 3:26 ` [RFC PATCH v5 0/1] drivers: mfd: Versatile Express SPC support Nicolas Pitre
2013-07-17 3:26 ` Nicolas Pitre
2013-07-17 3:26 ` Nicolas Pitre
2013-07-17 9:18 ` Pawel Moll
2013-07-17 9:18 ` Pawel Moll
2013-07-17 10:44 ` Lorenzo Pieralisi
2013-07-17 10:44 ` Lorenzo Pieralisi
2013-07-17 12:33 ` Nicolas Pitre
2013-07-17 12:33 ` Nicolas Pitre
2013-07-17 13:29 ` Pawel Moll
2013-07-17 13:29 ` Pawel Moll
2013-07-17 14:16 ` Nicolas Pitre
2013-07-17 14:16 ` Nicolas Pitre
2013-07-17 14:20 ` Pawel Moll [this message]
2013-07-17 14:20 ` Pawel Moll
2013-07-17 15:57 ` Nicolas Pitre
2013-07-17 15:57 ` Nicolas Pitre
2013-07-17 17:00 ` Russell King - ARM Linux
2013-07-17 17:00 ` Russell King - ARM Linux
2013-07-17 17:00 ` Russell King - ARM Linux
2013-07-17 18:29 ` Nicolas Pitre
2013-07-17 18:29 ` Nicolas Pitre
2013-07-17 21:23 ` Samuel Ortiz
2013-07-17 21:23 ` Samuel Ortiz
2013-07-17 22:22 ` Nicolas Pitre
2013-07-17 22:22 ` Nicolas Pitre
2013-07-17 22:22 ` Nicolas Pitre
2013-07-17 22:47 ` Samuel Ortiz
2013-07-17 22:47 ` Samuel Ortiz
2013-07-17 21:10 ` Samuel Ortiz
2013-07-17 21:10 ` Samuel Ortiz
2013-07-17 21:10 ` Samuel Ortiz
2013-07-17 21:07 ` Samuel Ortiz
2013-07-17 21:07 ` Samuel Ortiz
2013-07-17 21:07 ` Samuel Ortiz
2013-07-18 9:28 ` Lorenzo Pieralisi
2013-07-18 9:28 ` Lorenzo Pieralisi
2013-07-18 9:28 ` Lorenzo Pieralisi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1374070811.3146.124.camel@hornet \
--to=pawel.moll@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.