Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: David Rivshin <drivshin@awxrd.com>
To: linux-gpio@vger.kernel.org, linux-omap@vger.kernel.org,
	Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
	Kevin Hilman <khilman@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-arm@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: [PATCH 0/2] gpio: omap: set_debounce fixes
Date: Thu, 16 Mar 2017 21:48:54 -0400	[thread overview]
Message-ID: <20170317014856.31449-1-drivshin@awxrd.com> (raw)

From: David Rivshin <drivshin@allworx.com>

This series fixes a couple of issues in the gpio-omap set_debounce logic.

Patches based ontop of v4.11-rc1, but apply cleanly to linux-gpio/fixes
and linux-next.

Tested on a (custom) AM335x board via gpio-keys.

(Apologies if anyone received this series twice, it seemed to fail
the first time due to a typo. Please ignore the any previous copy.)


David Rivshin (2):
  gpio: omap: return error if requested debounce time is not possible
  gpio: omap: compute debounce-time from actual debounce-clock rate

 drivers/gpio/gpio-omap.c | 26 +++++++++++++++++---------
 1 file changed, 17 insertions(+), 9 deletions(-)

-- 
2.9.3

base-commit: c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201

             reply	other threads:[~2017-03-17  1:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17  1:48 David Rivshin [this message]
2017-03-17  1:48 ` [PATCH 1/2] gpio: omap: return error if requested debounce time is not possible David Rivshin
2017-03-17  1:48 ` [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate David Rivshin

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=20170317014856.31449-1-drivshin@awxrd.com \
    --to=drivshin@awxrd.com \
    --cc=gnurou@gmail.com \
    --cc=grygorii.strashko@ti.com \
    --cc=khilman@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=stable@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