[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <663067.14695.qm@web180316.mail.gq1.yahoo.com>
Date: Fri, 21 May 2010 06:23:12 -0700 (PDT)
From: David Brownell <david-b@...bell.net>
To: felipe.balbi@...ia.com
Cc: "Balbi Felipe \(Nokia-D/Helsinki\)" <felipe.balbi@...ia.com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Tony Lindgren <tony@...mide.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/5] gpiolib: introduce set_debounce method
> > Not all GPIOs have hardware debounce though, so
> offering this
> > capability sort of begs the question of where/how to
> provide a software debounce mechanism too...
>
> how about adding a flag for supported features and if that
> hardware doesn't support we simply return,
Presense of a debounce method would suffice when gpiolib is
in use (vs direct implementation of the API provided by gpiolib).
> or fallback to
> software emulation if chosen by the user.
ISTR that if you look back to the original discussion about
GPIO debouncing, you will find such a software implementation;
and maybe such an integration ...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists