Re: [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate
From: Grygorii Strashko <grygorii.strashko@xxxxxx>
Date: Fri, 17 Mar 2017 14:43:02 -0500
Cc: Santosh Shilimkar <ssantosh@xxxxxxxxxx>, Kevin Hilman <khilman@xxxxxxxxxx>, Linus Walleij <linus.walleij@xxxxxxxxxx>, Alexandre Courbot <gnurou@xxxxxxxxx>, <"linux-arm@vger.kernel.orglinux-kernel"@vger.kernel.org>, <stable@xxxxxxxxxxxxxxx>
In-reply-to: <20170317005704.11971-3-drivshin@awxrd.com>
References: <20170317005704.11971-1-drivshin@awxrd.com> <20170317005704.11971-3-drivshin@awxrd.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Follow-Ups:
- Re: [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate
  - From: David Rivshin

Prev by Date: Re: [PATCHv2 5/9] ARM: OMAP2+: hwmod: assign main clock from DT if available
Next by Date: Re: [PATCHv2 5/9] ARM: OMAP2+: hwmod: assign main clock from DT if available
Previous by thread: Re: [PATCH 1/2] gpio: omap: return error if requested debounce time is not possible
Next by thread: Re: [PATCH 2/2] gpio: omap: compute debounce-time from actual debounce-clock rate
Index(es):
- Date
- Thread

[Index of Archives] [Linux Arm (vger)] [ARM Kernel] [ARM MSM] [Linux Tegra] [Linux WPAN Networking] [Linux Wireless Networking] [Maemo Users] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux SCSI]

Powered by Linux