public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: kernel@wildgooses.com
Cc: rpurdie@rpsys.net, const@mimas.ru, daniel@caiaq.de,
	a.zummo@towertech.it, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: New PCEngines Alix LED driver using gpio interface
Date: Thu, 7 Apr 2011 14:58:36 -0700	[thread overview]
Message-ID: <20110407145836.3cde7699.akpm@linux-foundation.org> (raw)
In-Reply-To: <1299430285-13189-1-git-send-email-kernel@wildgooses.com>

On Sun,  6 Mar 2011 16:51:25 +0000
kernel@wildgooses.com wrote:

> From: Ed Wildgoose <kernel@wildgooses.com>
> 
> This new driver replaces the old PCEngines Alix 2/3 LED driver with
> a new driver that controls the LEDs through the leds-gpio driver.
> The old driver accessed GPIOs directly, which created a conflict 
> and prevented also loading the cs5535-gio driver to read other
> GPIOs on the Alix board. With this new driver, both are loaded
> and therefore it's possible to access both the LEDs and onboard GPIOs 
> 
> This driver is based on leds-net5501.c 
> by: Alessandro Zummo <a.zummo@towertech.it>
> Additionally it relies on parts of the patch: 7f131cf3ed
> by: Daniel Mack <daniel@caiaq.de> to perform detection of the Alix board

As far as I can tell from looking at it, this driver maintains all the
same interfaces and behaviour as the old version.  Am I right?


  reply	other threads:[~2011-04-07 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06 16:51 [PATCH] leds: New PCEngines Alix LED driver using gpio interface kernel
2011-04-07 21:58 ` Andrew Morton [this message]
2011-04-07 22:41   ` Ed W
  -- strict thread matches above, loose matches on Subject: below --
2011-03-17 18:17 Feedback please: " Grant Likely
2011-03-18 18:12 ` kernel
2011-03-18 18:32   ` Ed W
2011-03-18 22:48     ` Grant Likely

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=20110407145836.3cde7699.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=a.zummo@towertech.it \
    --cc=const@mimas.ru \
    --cc=daniel@caiaq.de \
    --cc=kernel@wildgooses.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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