From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/4] mfd: lubbock_cplds: add lubbock IO board
Date: Wed, 25 Mar 2015 15:07:25 +0100 [thread overview]
Message-ID: <20150325140725.GA11499@kroah.com> (raw)
In-Reply-To: <87a9088tam.fsf@free.fr>
On Fri, Feb 20, 2015 at 05:02:57PM +0100, Robert Jarzmik wrote:
> Lee Jones <lee.jones@linaro.org> writes:
> >> > Arnd, Greg,
> >> >
> >> > Perhaps you have some ideas WRT programmables (PLDs/CPLDs/FPGAs)?
>
> Hi Arnd and Greg,
>
> I have this driver I'm upstreaming, which comes out of
> arch/arm/mach-pxa/lubbock.c. As for the reason it is extracted, see submitted
> commit [1] for reference.
>
> The main question is : where does it belong in the kernel ?
>
> The driver is :
> - for the CPLDs on the Lubbock development platform, which is more or less an
> old motherboard for Intel Xscale pxa255 SoC (see [2] for more details)
> - these CPLDs control :
> - interrupt muxing towards the SoC
> - several leds
> - switches read back
> For the whole patch, see [4]
>
> Lee's position is that it doesn't belong to drivers/mfd, see [3].
>
> So where should I submit it ? And more generally, where should CPLDs drivers be
> pushed in the kernel tree ?
>
> If there is no solution, I'll fallback through arch/arm/plat-pxa, not very nice,
> but it has to land somewhere, I don't want lubbock to remain broken.
drivers/platform/arm ?
next prev parent reply other threads:[~2015-03-25 14:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 15:05 [PATCH v4 1/4] dt-bindings: mfd: add lubbock-cplds binding Robert Jarzmik
2015-01-24 15:05 ` [PATCH v4 2/4] mfd: lubbock_cplds: add lubbock IO board Robert Jarzmik
2015-02-16 13:05 ` Lee Jones
2015-02-16 13:27 ` robert.jarzmik at free.fr
2015-02-16 16:27 ` Lee Jones
2015-02-16 22:14 ` Robert Jarzmik
2015-02-17 7:43 ` Lee Jones
2015-02-17 17:38 ` Nicolas Pitre
2015-02-18 8:07 ` Lee Jones
2015-02-20 16:02 ` Robert Jarzmik
2015-02-28 9:57 ` Robert Jarzmik
2015-02-28 15:11 ` Greg Kroah-Hartman
2015-02-28 15:29 ` Robert Jarzmik
2015-03-25 14:07 ` Greg Kroah-Hartman [this message]
2015-03-26 21:38 ` Robert Jarzmik
2015-03-26 23:47 ` Greg Kroah-Hartman
2015-03-28 2:35 ` Arnd Bergmann
2015-03-28 8:29 ` Robert Jarzmik
2015-03-28 13:24 ` Arnd Bergmann
2015-01-24 15:05 ` [PATCH v4 3/4] ARM: pxa: lubbock: use new lubbock_cplds driver Robert Jarzmik
2015-01-24 15:05 ` [PATCH v4 4/4] MAINTAINERS: add entry for lubbock-cplds Robert Jarzmik
2015-02-10 18:41 ` [PATCH v4 1/4] dt-bindings: mfd: add lubbock-cplds binding Robert Jarzmik
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=20150325140725.GA11499@kroah.com \
--to=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).