All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: David Wu <david.wu@rock-chips.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
	"Tao Huang" <huangtao@rock-chips.com>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] Add pinctrl input schmitt support
Date: Wed, 22 Feb 2017 16:04:58 +0100	[thread overview]
Message-ID: <CACRpkdYZg42hVuP_s1aacecsHg1XHEMO2W-yAjUBdoWbcZc5hw@mail.gmail.com> (raw)
In-Reply-To: <1487068541-14120-1-git-send-email-david.wu@rock-chips.com>

On Tue, Feb 14, 2017 at 11:35 AM, David Wu <david.wu@rock-chips.com> wrote:

> From: "david.wu" <david.wu@rock-chips.com>
>
> Some pins need to enable Schmitt triggers which are used
> in open loop configurations for noise immunity and closed
> loop configurations to implement function generators.

Just waiting for Heiko's review on this series before I queue it.

Yours,
Linus Walleij

      parent reply	other threads:[~2017-02-22 15:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 10:35 [PATCH v1 0/2] Add pinctrl input schmitt support David Wu
     [not found] ` <1487068541-14120-1-git-send-email-david.wu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-02-14 10:35   ` [PATCH v1 1/2] pinctrl: rockchip：Add " David Wu
2017-02-14 10:35     ` David Wu
2017-02-23 16:51     ` Heiko Stuebner
2017-02-28 11:12       ` David.Wu
2017-02-28 11:12         ` David.Wu
2017-02-14 10:35 ` [PATCH v1 2/2] pinctrl: rockchip: Add input schmitt support for rk3328 David Wu
2017-02-23 16:53   ` Heiko Stuebner
2017-02-22 15:04 ` Linus Walleij [this message]

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=CACRpkdYZg42hVuP_s1aacecsHg1XHEMO2W-yAjUBdoWbcZc5hw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=david.wu@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.