From: Linus Walleij <linus.walleij@linaro.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v3 3/3] gpio: Add Spreadtrum PMIC EIC driver support
Date: Tue, 27 Mar 2018 15:52:28 +0200 [thread overview]
Message-ID: <CACRpkdYF_dBi27jHEsO52SZs3sYR9JG_+ZDpH8bmDZ5ew4uskA@mail.gmail.com> (raw)
In-Reply-To: <c84c05b6619a17848a11335f881f42153a4e51c0.1520218279.git.baolin.wang@linaro.org>
On Mon, Mar 5, 2018 at 3:56 AM, Baolin Wang <baolin.wang@linaro.org> wrote:
> The Spreadtrum PMIC EIC controller contains only one bank of debounce EIC,
> and this bank contains 16 EICs. Each EIC can only be used as input mode,
> as well as supporting the debounce and the capability to trigger interrupts
> when detecting input signals.
>
> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
> ---
> Changes since v2:
> - Fix coding style issue.
> - Fix possible overflow.
> - Use for_each_set_bit().
Patch applied!
Also added Andy's review tag on all of the patches.
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-03-27 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 2:56 [PATCH v3 1/3] dt-bindings: gpio: Add Spreadtrum EIC controller documentation Baolin Wang
2018-03-05 2:56 ` [PATCH v3 2/3] gpio: Add Spreadtrum EIC driver support Baolin Wang
2018-03-27 13:49 ` Linus Walleij
2018-03-05 2:56 ` [PATCH v3 3/3] gpio: Add Spreadtrum PMIC " Baolin Wang
2018-03-05 15:46 ` Andy Shevchenko
2018-03-27 9:10 ` Baolin Wang
2018-03-27 13:52 ` Linus Walleij [this message]
2018-03-27 13:48 ` [PATCH v3 1/3] dt-bindings: gpio: Add Spreadtrum EIC controller documentation Linus Walleij
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=CACRpkdYF_dBi27jHEsO52SZs3sYR9JG_+ZDpH8bmDZ5ew4uskA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).