From: Linus Walleij <linus.walleij@linaro.org>
To: Yixun Lan <yixun.lan@amlogic.com>,
Carlo Caione <carlo@caione.org>,
Beniamino Galvani <b.galvani@gmail.com>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Xingyu Chen <xingyu.chen@amlogic.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-gpio@vger.kernel.org,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] pinctrl: meson: use one uniform 'function' name
Date: Thu, 11 Jan 2018 10:46:38 +0100 [thread overview]
Message-ID: <CACRpkdZ6pW_3QTeQMGVbpa=1WTgR59fi+0aWCqmbRBzOn+F0cA@mail.gmail.com> (raw)
In-Reply-To: <20180108073328.205769-1-yixun.lan@amlogic.com>
On Mon, Jan 8, 2018 at 8:33 AM, Yixun Lan <yixun.lan@amlogic.com> wrote:
> These two patches are general improvement for meson pinctrl driver.
> It make the two pinctrl trees (ee/ao) to share one uniform 'function' name for
> one hardware block even its pin groups live inside two differet hardware domains,
> which for example EE vs AO domain here.
>
> This idea is motivated by Martin's question at [1]
>
> [1]
> http://lkml.kernel.org/r/CAFBinCCuQ-NK747+GHDkhZty_UMMgzCYOYFcNTrRDJgU8OM=Gw@mail.gmail.com
There seems to be controversy here so I'd like input from Carlo
and/or Beniamino if possible.
Yours,
Linus Walleij
prev parent reply other threads:[~2018-01-11 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 7:33 [PATCH 0/2] pinctrl: meson: use one uniform 'function' name Yixun Lan
2018-01-08 7:33 ` [PATCH 1/2] pinctrl: meson: introduce a macro to have name/groups seperated Yixun Lan
2018-01-08 7:33 ` [PATCH 2/2] pinctrl: meson-axg: correct the pin expansion of UART_AO_B Yixun Lan
2018-01-08 8:52 ` [PATCH 0/2] pinctrl: meson: use one uniform 'function' name Jerome Brunet
2018-01-10 2:12 ` Yixun Lan
2018-01-10 7:28 ` Jerome Brunet
2018-01-10 12:00 ` Yixun Lan
2018-01-17 0:14 ` Kevin Hilman
2018-01-18 13:54 ` Yixun Lan
2018-01-11 9:46 ` 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='CACRpkdZ6pW_3QTeQMGVbpa=1WTgR59fi+0aWCqmbRBzOn+F0cA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=b.galvani@gmail.com \
--cc=carlo@caione.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=xingyu.chen@amlogic.com \
--cc=yixun.lan@amlogic.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).