From: "Heiko Stübner" <heiko@sntech.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: David Wu <david.wu@rock-chips.com>,
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] pinctrl: rockchip: Add rk3328 pinctrl support
Date: Thu, 26 Jan 2017 16:07:46 +0100 [thread overview]
Message-ID: <24353895.ALOnc7lYnh@diego> (raw)
In-Reply-To: <CACRpkdaJEEGFnfX0_eBtwLMqYtSTShB5u6WCaA-YZG53OMnk+w@mail.gmail.com>
Am Donnerstag, 26. Januar 2017, 14:29:17 CET schrieb Linus Walleij:
> On Sun, Jan 22, 2017 at 9:38 AM, David Wu <david.wu@rock-chips.com> wrote:
> > From: "david.wu" <david.wu@rock-chips.com>
> >
> > This patch supports 3bit width iomux type.
> > Note, the iomux of following pins are special, need to
> > be handled specially.
> >
> > - gpio2_b0 ~ gpio2_b6
> > - gpio2_b7
> > - gpio2_c7
> > - gpio3_b0
> > - gpio3_b1 ~ gpio3_b7
> >
> > And therefore add IOMUX_RECALCED_FLAG to indicate which
> > iomux source of the bank need to be recalced. If the mux
> > recalced callback and IOMUX_RECALCED_FLAG were set, recalc
> > the related pins' iomux.
> >
> > Signed-off-by: david.wu <david.wu@rock-chips.com>
>
> Heiko, could you review this?
it's on my todo list, I just didn't have the time this week so far.
Heiko
next prev parent reply other threads:[~2017-01-26 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 8:38 [PATCH] pinctrl: rockchip: Add rk3328 pinctrl support David Wu
2017-01-26 13:29 ` Linus Walleij
2017-01-26 15:07 ` Heiko Stübner [this message]
[not found] ` <1485074286-7863-1-git-send-email-david.wu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-01-27 16:03 ` Heiko Stuebner
2017-02-06 8:50 ` David.Wu
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=24353895.ALOnc7lYnh@diego \
--to=heiko@sntech.de \
--cc=david.wu@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=linus.walleij@linaro.org \
--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 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).