mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Bryan Wu" <cooloney@kernel.org>
Cc: "pHilipp Zabel" <philipp.zabel@gmail.com>,
	dbrownell@users.sourceforge.net, dmitry.torokhov@gmail.com,
	linux-kernel@vger.kernel.org,
	"Michael Hennerich" <michael.hennerich@analog.com>
Subject: Re: [PATCH 1/1] [INPUT/KEYPAD] gpio keypad: Replace current blackfin specific pfbutton driver with kernel generic gpio key driver
Date: Mon, 12 May 2008 08:47:23 -0400	[thread overview]
Message-ID: <8bd0f97a0805120547g5c46973fl538ad18d81a4aebc@mail.gmail.com> (raw)
In-Reply-To: <386072610805120511p5d1254cch26e2c8d5d0f755c7@mail.gmail.com>

On Mon, May 12, 2008 at 8:11 AM, Bryan Wu <cooloney@kernel.org> wrote:
> On Mon, May 12, 2008 at 7:42 PM, Mike Frysinger <vapier.adi@gmail.com> wrote:
>> On Mon, May 12, 2008 at 7:27 AM, pHilipp Zabel
<philipp.zabel@gmail.com> wrote:
>>  > On Mon, May 12, 2008 at 12:17 PM, Bryan Wu <cooloney@kernel.org> wrote:
>>  >> From: Michael Hennerich <michael.hennerich@analog.com>
>>  >>
>>  >>  It's an actual deficiency in the hardware that we can't address,
>>  >>  so it needs to be worked around in software.
>>  >>
>>  >>  Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
>>  >>  Signed-off-by: Bryan Wu <cooloney@kernel.org>
>>  >>  ---
>>  >>   drivers/input/keyboard/gpio_keys.c |   15 ++++++++++++++-
>>  >>   1 files changed, 14 insertions(+), 1 deletions(-)
>>  >>
>>  >>  diff --git a/drivers/input/keyboard/gpio_keys.c
>>  b/drivers/input/keyboard/gpio_keys.c
>>  >>  index bbd00c3..d856eb9 100644
>>  >>  --- a/drivers/input/keyboard/gpio_keys.c
>>  >>  +++ b/drivers/input/keyboard/gpio_keys.c
>>  >>  @@ -26,6 +26,18 @@
>>  >>
>>  >>   #include <asm/gpio.h>
>>  >>
>>  >>  +#if defined(CONFIG_BLACKFIN) && !defined(BF548_FAMILY)
>>  >>  +
>>  >>  +/*
>>  >>  + * On some Blackfin CPUs reading edge triggered
>>  >>  + * GPIOs doesn't return the current value
>>  >>  + */
>>  >
>>  > If this is a generic problem, shouldn't this be addressed inside
gpio_get_value?
>>
>>  it's an issue only when the GPIO is an interrupt source and the
>>  trigger condition is set to both rising and falling.  but i guess your
>>  point is that in gpio_get_value(), we can check to see if these
>>  conditions are met and if so, temporarily fiddle things there ?
>>
>>  Michael: that sounds reasonable, what do you think ?
>
> IMO, maybe it is feasible for fix this in generic GPIO layer, or will
> break other things?

where are you referring to ?  i think what's being proposed is to move
these checks to arch/blackfin/kernel/bfin_gpio.c ... any call to
gpio_get_value() under these circumstances will need the edge sense
toggle ...
-mike

  reply	other threads:[~2008-05-12 12:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 10:17 Bryan Wu
2008-05-12 11:27 ` pHilipp Zabel
2008-05-12 11:42   ` Mike Frysinger
2008-05-12 12:11     ` Bryan Wu
2008-05-12 12:47       ` Mike Frysinger [this message]
2008-05-12 14:42         ` Bryan Wu
2008-05-12 16:54           ` David Brownell
2008-05-12 16:59             ` Mike Frysinger
2008-05-13  7:53               ` Hennerich, Michael
2008-05-12 16:55 ` 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=8bd0f97a0805120547g5c46973fl538ad18d81a4aebc@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=cooloney@kernel.org \
    --cc=dbrownell@users.sourceforge.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=philipp.zabel@gmail.com \
    /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®