From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm pxa: remove "direction input" forcing for IRQ GPIOs
Date: Tue, 17 Nov 2009 14:06:53 +0100 [thread overview]
Message-ID: <20091117130653.GX14091@buzzloop.caiaq.de> (raw)
In-Reply-To: <20091117125953.GI8008@gundam.enneenne.com>
On Tue, Nov 17, 2009 at 01:59:53PM +0100, Rodolfo Giometti wrote:
> On Tue, Nov 17, 2009 at 01:43:34PM +0100, Daniel Mack wrote:
> > On Tue, Nov 17, 2009 at 01:37:21PM +0100, Rodolfo Giometti wrote:
> > > On Tue, Nov 17, 2009 at 01:34:22PM +0100, Daniel Mack wrote:
> > > > For such situations, the pullup/pulldown functions are normally used.
> > > > Have you tried that?
> > >
> > > Yes, the code has been tested on my board and it works perfectly.
> >
> > What I mean is a mfp_cfg_t configuration as input pin with pull flags
> > MFP_PULL_{HIGH,LOW} set.
>
> I see... no I didn't noticed such possibility.
>
> however I suppose that even using such flags my patch is needed in
> order to avoid pxa_gpio_irq_type() forcing the input direction...
No, that's exactly my point. You don't need to set the pin to output
direction to make use of those pull features. More than that, when
confiugured as output, the pull flags actually don't make sense.
As an IRQ is always inbound, I agree with Eric that the code should
stay in there for safety and sanity.
Daniel
next prev parent reply other threads:[~2009-11-17 13:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 11:21 [PATCH] arm pxa: remove "direction input" forcing for IRQ GPIOs Rodolfo Giometti
2009-11-17 11:44 ` Daniel Mack
2009-11-17 12:05 ` Rodolfo Giometti
2009-11-17 12:12 ` Eric Miao
2009-11-17 12:34 ` Daniel Mack
2009-11-17 12:37 ` Rodolfo Giometti
2009-11-17 12:43 ` Daniel Mack
2009-11-17 12:59 ` Rodolfo Giometti
2009-11-17 13:06 ` Daniel Mack [this message]
2009-11-17 13:16 ` Rodolfo Giometti
2009-11-17 14:38 ` Rodolfo Giometti
2009-11-17 17:11 ` Daniel Mack
2009-11-17 18:02 ` Rodolfo Giometti
2009-11-17 19:28 ` Russell King - ARM Linux
2009-11-17 17:00 ` H Hartley Sweeten
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=20091117130653.GX14091@buzzloop.caiaq.de \
--to=daniel@caiaq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.