Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: David Rivshin <drivshin@awxrd.com>,
	linux-gpio@vger.kernel.org, linux-omap@vger.kernel.org
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.orglinux-kernel"@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate
Date: Fri, 17 Mar 2017 14:43:02 -0500	[thread overview]
Message-ID: <adc98bfd-ebce-49f0-5991-3c6a1e99ec25@ti.com> (raw)
In-Reply-To: <20170317005704.11971-3-drivshin@awxrd.com>



  parent reply	other threads:[~2017-03-17 19:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170317005704.11971-1-drivshin@awxrd.com>
     [not found] ` <20170317005704.11971-2-drivshin@awxrd.com>
2017-03-17 16:45   ` [PATCH 1/2] gpio: omap: return error if requested debounce time is not possible Grygorii Strashko
2017-03-17 17:54     ` David Rivshin
2017-03-17 18:54       ` Grygorii Strashko
2017-03-17 20:50         ` David Rivshin
2017-03-17 21:43           ` Grygorii Strashko
2017-03-17 23:42             ` David Rivshin
2017-04-20 14:44               ` David Rivshin
2017-04-20 15:19                 ` Grygorii Strashko
     [not found] ` <20170317005704.11971-3-drivshin@awxrd.com>
2017-03-17 19:43   ` Grygorii Strashko [this message]
2017-03-17 23:14     ` [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate David Rivshin
2017-03-18  0:06       ` Grygorii Strashko
2017-04-20 13:53         ` David Rivshin
2017-03-17  1:48 [PATCH 0/2] gpio: omap: set_debounce fixes 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=adc98bfd-ebce-49f0-5991-3c6a1e99ec25@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc="linux-arm@vger.kernel.orglinux-kernel"@vger.kernel.org \
    --cc=drivshin@awxrd.com \
    --cc=gnurou@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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