From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Correct bad gpio naming
Date: Tue, 24 Jan 2012 17:32:21 +0100 [thread overview]
Message-ID: <4F1EDD15.7010704@antcom.de> (raw)
In-Reply-To: <20120124155921.GH2609@pengutronix.de>
Hi,
On 01/24/2012 04:59 PM, Wolfram Sang wrote:
> On Sun, Jan 22, 2012 at 06:57:57PM +0100, Roland Stigge wrote:
>> One of the GPIO names in drivers/gpio/gpio-lpc32xx.c was bad.
>> Renaming gpi000 -> gpio00
>>
>> Signed-off-by: Roland Stigge <stigge@antcom.de>
>
> Since you are modifying LPC32xx :) Which kernel version do you run?
> I was trying to get a board up with 3.0 (not booting) and 3.3-rc1
> (build breakage). I even thought about removing that mach, since
> vital parts seem to be missing (Net, NAND) or broken. So, I am
> interested if there are still users.
I'm actively maintaining an LPC32xx machine line (WORK Microwave GmbH
devices) at http://git.antcom.de/ - feel free to merge from there.
For me, it works fine with Linux 3.2.0.
The repo includes some additional features like NAND (esp. MLC
controller, while NXP implemented an SLC driver), High Speed UARTs and
ADC. Some of those are not yet integrated mainline, but I'm willing to
help here. Looks like I will maintain it anyway for the next few years.
Expect the first one of the drivers to be submitted soon, I will do
them one by one.
Thanks for keeping LPC32xx :-)
Roland
next prev parent reply other threads:[~2012-01-24 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 17:57 [PATCH] Correct bad gpio naming Roland Stigge
2012-01-22 19:31 ` Grant Likely
2012-01-24 15:59 ` Wolfram Sang
2012-01-24 16:32 ` Roland Stigge [this message]
2012-01-24 19:25 ` LPC32xx status (Re: [PATCH] Correct bad gpio naming) Wolfram Sang
2012-01-24 20:38 ` Roland Stigge
2012-01-24 21:09 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2012-01-10 13:36 [PATCH] Correct bad gpio naming stigge at antcom.de
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=4F1EDD15.7010704@antcom.de \
--to=stigge@antcom.de \
--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).