From: Laxman Dewangan <ldewangan@nvidia.com>
To: <swarren@wwwdotorg.org>, <linus.walleij@linaro.org>,
<gnurou@gmail.com>, <thierry.reding@gmail.com>,
<linux-gpio@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH V5 0/4] gpio: tegra: Cleanups and support for debounce
Date: Mon, 25 Apr 2016 16:08:30 +0530 [thread overview]
Message-ID: <1461580714-22479-1-git-send-email-ldewangan@nvidia.com> (raw)
Add support for the debounce as Tegra210 support debounce in HW.
Also do the clenaups to remove all global variables.
Changes from V3:
- Rearranging debounce registers and lock the DB CNT registers.
Changes from V4:
- Get rid of tegra_gpio_chip and tegra_irq_chip as global.
Laxman Dewangan (4):
gpio: tegra: Don't open code of_device_get_match_data()
gpio: tegra: Make of_device_id compatible data to constant
gpio: tegra: Get rid of all file scoped global variables
gpio: tegra: Add support for gpio debounce
drivers/gpio/gpio-tegra.c | 407 +++++++++++++++++++++++++++++-----------------
1 file changed, 261 insertions(+), 146 deletions(-)
--
2.1.4
next reply other threads:[~2016-04-25 10:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 10:38 Laxman Dewangan [this message]
2016-04-25 10:38 ` [PATCH V5 1/4] gpio: tegra: Don't open code of_device_get_match_data() Laxman Dewangan
2016-04-29 8:59 ` Linus Walleij
2016-04-25 10:38 ` [PATCH V5 2/4] gpio: tegra: Make of_device_id compatible data to constant Laxman Dewangan
2016-04-29 9:00 ` Linus Walleij
2016-04-25 10:38 ` [PATCH V5 3/4] gpio: tegra: Get rid of all file scoped global variables Laxman Dewangan
2016-04-29 9:01 ` Linus Walleij
2016-04-25 10:38 ` [PATCH V5 4/4] gpio: tegra: Add support for gpio debounce Laxman Dewangan
2016-04-28 5:58 ` Alexandre Courbot
2016-04-29 9:03 ` Linus Walleij
2016-04-29 9:07 ` [PATCH V5 0/4] gpio: tegra: Cleanups and support for debounce Linus Walleij
2016-04-29 9:20 ` Laxman Dewangan
2016-04-30 11:07 ` Linus Walleij
2016-05-02 6:44 ` Laxman Dewangan
2016-05-02 16:12 ` Stephen Warren
2016-05-02 17:58 ` Laxman Dewangan
2016-05-02 18:44 ` Stephen Warren
2016-05-02 19:06 ` Laxman Dewangan
2016-05-03 15:59 ` Stephen Warren
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=1461580714-22479-1-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).