From: Ben Nizette <bn@niasdigital.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: Latest gpio gumph
Date: Wed, 28 May 2008 15:13:53 +1000 [thread overview]
Message-ID: <1211951633.27810.72.camel@moss.renham> (raw)
In-Reply-To: <200805272144.33334.david-b@pacbell.net>
On Tue, 2008-05-27 at 21:44 -0700, David Brownell wrote:
> On Tuesday 27 May 2008, Ben Nizette wrote:
> > Hey David,
> >
> > Have you got a git/quilt repo somewhere with all the latest gpiolib (and
> > gpio framework) stuff glued in? I've seen most of it hit -mm but
> > developing against -mm on (especially on obscure archs like AVR32 as I
> > do) is always fraught.
>
> All the relevant stuff is now upstream (2.6.26-rc4) except:
>
> - the userspace sysfs interface (which is in MM, and ISTR
> you were cc'd on that)
Yup, indeed.
>
> - an avr32 patch, appended (no response on the avr32 list)
>
> Nothing else touches core code; if you're using AVR32, then
> you won't care about at91 gpiolib and inlining support, or the
> patch sent this AM on LKML (which I've not yet reviewed).
Righteo, thanks.
--Ben.
>
> - Dave
>
>
>
> ====== CUT HERE
> From: David Brownell <dbrownell@users.sourceforge.net>
> Subject: AVR32: minor GPIO handling updates
>
> * gpio_direction_output() should disable the pullups just like
> at32_select_gpio(... AT32_GPIOF_OUTPUT) does, for consistency
> between those alternative initialization paths.
>
> * On the odd chance some code uses a pin as a GPIO IRQ without
> calling gpio_request() or gpio_direction_input(), the debug
> dump should still show its pin status.
>
> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> ---
> arch/avr32/mach-at32ap/pio.c | 3 +++
> 1 files changed, 3 insertions(+)
>
> --- a/arch/avr32/mach-at32ap/pio.c 2008-05-02 12:30:59.000000000 -0700
> +++ b/arch/avr32/mach-at32ap/pio.c 2008-05-02 12:41:29.000000000 -0700
> @@ -191,6 +191,7 @@ static int direction_output(struct gpio_
> return -EINVAL;
>
> gpio_set(chip, offset, value);
> + pio_writel(pio, PUDR, mask);
> pio_writel(pio, OER, mask);
> return 0;
> }
> @@ -318,6 +319,8 @@ static void pio_bank_show(struct seq_fil
> const char *label;
>
> label = gpiochip_is_requested(chip, i);
> + if (!label && (imr & mask))
> + label = "[irq]";
> if (!label)
> continue;
>
next prev parent reply other threads:[~2008-05-28 5:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 2:41 Ben Nizette
2008-05-28 4:44 ` David Brownell
2008-05-28 5:13 ` Ben Nizette [this message]
2008-05-28 8:14 ` Haavard Skinnemoen
2008-05-28 9:01 ` David Brownell
2008-05-28 9:21 ` Haavard Skinnemoen
2008-05-30 3:18 ` David Brownell
2008-06-10 11:58 ` Haavard Skinnemoen
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=1211951633.27810.72.camel@moss.renham \
--to=bn@niasdigital.com \
--cc=david-b@pacbell.net \
--cc=hskinnemoen@atmel.com \
--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
all inboxes | Powered by JetHome®