From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mfd: vexpress: Add pseudo-GPIO based LEDs
Date: Wed, 30 Jan 2013 15:54:42 +0000 [thread overview]
Message-ID: <1359561282.3094.15.camel@hornet> (raw)
In-Reply-To: <20130130154923.GE1174@sortiz-mobl>
On Wed, 2013-01-30 at 15:49 +0000, Samuel Ortiz wrote:
> On Wed, Jan 30, 2013 at 10:33:16AM +0000, Pawel Moll wrote:
> > The LEDs on the Versatile Express motherboard are controlled
> > through simple memory-mapped register. This patch extends
> > the pseudo-GPIO controller definition for these lines and
> > creates generic "leds-gpio" device using them
> >
> > Signed-off-by: Pawel Moll <pawel.moll@arm.com>
> > ---
> >
> > Hello Samuel,
> >
> > Would you be so kind to take this patch in for 3.9? Or would
> > you prefer to get it in through arm-soc tree?
> I'll take it through my MFD tree.
Great, thanks!
>
> > drivers/mfd/vexpress-sysreg.c | 73 +++++++++++++++++++++++++++++++----------
> > include/linux/vexpress.h | 8 +++++
> Hmmm, there is a include/linux/mfd/ directory for kernel MFD drivers, FYI.
Sure, it's just that this header "serves" whole platform, not only the
mfd drivers (eg. there are power-related declarations there as well). If
one day it gets divided, I'll make sure that the MFD portions will find
its way into ../mfd/.
Cheers!
Pawel
WARNING: multiple messages have this Message-ID (diff)
From: Pawel Moll <pawel.moll@arm.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] mfd: vexpress: Add pseudo-GPIO based LEDs
Date: Wed, 30 Jan 2013 15:54:42 +0000 [thread overview]
Message-ID: <1359561282.3094.15.camel@hornet> (raw)
In-Reply-To: <20130130154923.GE1174@sortiz-mobl>
On Wed, 2013-01-30 at 15:49 +0000, Samuel Ortiz wrote:
> On Wed, Jan 30, 2013 at 10:33:16AM +0000, Pawel Moll wrote:
> > The LEDs on the Versatile Express motherboard are controlled
> > through simple memory-mapped register. This patch extends
> > the pseudo-GPIO controller definition for these lines and
> > creates generic "leds-gpio" device using them
> >
> > Signed-off-by: Pawel Moll <pawel.moll@arm.com>
> > ---
> >
> > Hello Samuel,
> >
> > Would you be so kind to take this patch in for 3.9? Or would
> > you prefer to get it in through arm-soc tree?
> I'll take it through my MFD tree.
Great, thanks!
>
> > drivers/mfd/vexpress-sysreg.c | 73 +++++++++++++++++++++++++++++++----------
> > include/linux/vexpress.h | 8 +++++
> Hmmm, there is a include/linux/mfd/ directory for kernel MFD drivers, FYI.
Sure, it's just that this header "serves" whole platform, not only the
mfd drivers (eg. there are power-related declarations there as well). If
one day it gets divided, I'll make sure that the MFD portions will find
its way into ../mfd/.
Cheers!
Pawel
next prev parent reply other threads:[~2013-01-30 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 10:33 [PATCH] mfd: vexpress: Add pseudo-GPIO based LEDs Pawel Moll
2013-01-30 10:33 ` Pawel Moll
2013-01-30 15:49 ` Samuel Ortiz
2013-01-30 15:49 ` Samuel Ortiz
2013-01-30 15:54 ` Pawel Moll [this message]
2013-01-30 15:54 ` Pawel Moll
2013-02-03 22:32 ` Samuel Ortiz
2013-02-03 22:32 ` Samuel Ortiz
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=1359561282.3094.15.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.