public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: David Brownell <david-b@pacbell.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.24-rc6-mm 4/9] gpiolib: avr32 at32ap platform support
Date: Sat, 5 Jan 2008 21:49:16 +0100	[thread overview]
Message-ID: <20080105214916.7c67a522@siona> (raw)
In-Reply-To: <200801051210.56567.david-b@pacbell.net>

On Sat, 5 Jan 2008 12:10:56 -0800
David Brownell <david-b@pacbell.net> wrote:

> From: David Brownell <dbrownell@users.sourceforge.net>
> 
> Teach AVR32 to use the "GPIO Library" when exposing its GPIOs, so that
> signals on external chips (like GPIO expanders) can easily be used.
> 
> This mostly reorganizes some existing logic, with two minor changes
> in behavior:
> 
>  - The PSR registers are used instead of the previous "gpio_mask"
> values, matching AT91 behavior and removing some duplication between
> that role and that of "pinmux_mask".
> 
>  - NR_IRQs grew to acommodate a bank of external GPIOs.  Eventually
> this number should probably become a board-specific config option.
> 
> There's a debugfs dump of status for the built-in GPIOs, showing which
> pins have deglitching, pullups, or open drain drive enabled, as well
> as the ID string used when requesting each IRQ.
> 
> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>

Acked-by: Haavard Skinnemoen <hskinnemoen@atmel.com>

I'm not going to merge it since the rest of gpiolib isn't in mainline
yet.

Haavard

  reply	other threads:[~2008-01-05 21:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200712281927.32575.david-b@pacbell.net>
2007-12-29  3:53 ` [patch 2.6.24-rc6-mm 1/9] gpiolib: add drivers/gpio directory David Brownell
2007-12-29  6:58   ` Sam Ravnborg
2007-12-29 18:19     ` David Brownell
2007-12-29 19:03       ` Sam Ravnborg
2008-01-05 20:07   ` David Brownell
2007-12-29  3:54 ` [patch 2.6.24-rc6-mm 2/9] gpiolib: add gpio provider infrastructure David Brownell
2007-12-29  7:10   ` Sam Ravnborg
2007-12-29 18:35     ` David Brownell
2008-01-05 20:08   ` David Brownell
2007-12-29  3:55 ` [patch 2.6.24-rc6-mm 3/9] gpiolib: update Documentation/gpio.txt David Brownell
2008-01-05 20:09   ` David Brownell
2007-12-29  3:56 ` [patch 2.6.24-rc6-mm 4/9] gpiolib: avr32 at32ap platform support David Brownell
2008-01-05 20:10   ` David Brownell
2008-01-05 20:49     ` Haavard Skinnemoen [this message]
2008-01-05 22:09       ` David Brownell
2007-12-29  3:57 ` [patch 2.6.24-rc6-mm 5/9] gpiolib: pxa " David Brownell
2008-01-05 20:11   ` David Brownell
2007-12-29  3:58 ` [patch 2.6.24-rc6-mm 6/9] gpiolib: pcf857x i2c gpio expander support David Brownell
2008-01-05 20:13   ` David Brownell
2007-12-29  3:58 ` [patch 2.6.24-rc6-mm 7/9] gpiolib: mcp23s08 spi " David Brownell
2007-12-29  3:58 ` [patch 2.6.24-rc6-mm 8/9] gpiolib: pca9539 i2c " David Brownell
2008-01-02 13:46   ` Jean Delvare
2008-01-04  1:41     ` David Brownell
2008-01-05 19:40   ` David Brownell
2008-01-06 12:59     ` Jean Delvare
2007-12-29  3:59 ` [patch 2.6.24-rc6-mm 9/9] gpiolib: deprecate obsolete pca9539 driver David Brownell

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=20080105214916.7c67a522@siona \
    --to=hskinnemoen@atmel.com \
    --cc=akpm@linux-foundation.org \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.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