From: Linus Walleij <linus.walleij@linaro.org>
To: Coiby Xu <coiby.xu@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] pinctrl: amd: fix incorrect way to disable debounce filter
Date: Tue, 10 Nov 2020 14:18:30 +0100 [thread overview]
Message-ID: <CACRpkdb51B-bx3SPHZOeFG=+Qu5Ev-Sv9=wsFqXs3d-ykzcJ2A@mail.gmail.com> (raw)
In-Reply-To: <20201105231912.69527-2-coiby.xu@gmail.com>
On Fri, Nov 6, 2020 at 12:19 AM Coiby Xu <coiby.xu@gmail.com> wrote:
> The correct way to disable debounce filter is to clear bit 5 and 6
> of the register.
>
> Cc: Hans de Goede <hdegoede@redhat.com>
> Link: https://lore.kernel.org/linux-gpio/df2c008b-e7b5-4fdd-42ea-4d1c62b52139@redhat.com/
> Signed-off-by: Coiby Xu <coiby.xu@gmail.com>
This patch applied for fixes and tagged for stable.
Yours,
Linus Walleij
next prev parent reply other threads:[~2020-11-10 13:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201105231912.69527-1-coiby.xu@gmail.com>
2020-11-05 23:19 ` [PATCH v3 1/4] pinctrl: amd: fix incorrect way to disable debounce filter Coiby Xu
2020-11-09 13:50 ` Hans de Goede
2020-11-10 13:18 ` Linus Walleij [this message]
2020-11-05 23:19 ` [PATCH v3 2/4] pinctrl: amd: use higher precision for 512 RtcClk Coiby Xu
2020-11-09 13:50 ` Hans de Goede
2020-11-10 13:19 ` Linus Walleij
2020-11-05 23:19 ` [PATCH v3 3/4] pinctrl: amd: print debounce filter info in debugfs Coiby Xu
2020-11-10 13:21 ` Linus Walleij
2020-11-05 23:19 ` [PATCH v3 4/4] pinctrl: amd: remove debounce filter setting in IRQ type setting Coiby Xu
2020-11-09 13:52 ` Hans de Goede
2020-11-10 8:26 ` Coiby Xu
2020-11-10 8:35 ` Hans de Goede
2020-11-10 13:23 ` Linus Walleij
2020-11-10 13:57 ` Andy Shevchenko
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='CACRpkdb51B-bx3SPHZOeFG=+Qu5Ev-Sv9=wsFqXs3d-ykzcJ2A@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=coiby.xu@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).