From: Andrew Cooks <andrew.cooks@opengear.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-gpio@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nehal Shah <Nehal-bakulchandra.Shah@amd.com>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
Ken Xue <Ken.Xue@amd.com>,
Tobias Diedrich <ranma+kernel@tdiedrich.de>,
Sudheesh Mavila <sudheesh.mavila@amd.com>,
platypus-sw <platypus-sw@opengear.com>,
Timur Tabi <timur@codeaurora.org>
Subject: Re: pinctrl-amd: What hardware does it apply to?
Date: Fri, 22 Dec 2017 10:44:06 +1000 [thread overview]
Message-ID: <669cceb3-3225-f93a-41bf-5ad9dc22e7fe@opengear.com> (raw)
In-Reply-To: <CACRpkdaHj8SFL5AfSkAqDG0mHpgRVbmHuyrhwMUkEH2c4p0VDg@mail.gmail.com>
Hi Linus
On 21/12/17 20:11, Linus Walleij wrote:
> Hi Andrew!
>
> Thank you for your mail!
>
> On Wed, Dec 20, 2017 at 11:25 PM, Andrew Cooks
> <andrew.cooks@opengear.com> wrote:
>
>> Another driver (gpio-sb8xx) was submitted for upstream inclusion, but was
>> knocked back with the suggestion that pinctrl is the way forward[3].
>
> Hm I cannot follow link [3] right now. And I don't remember the submission :(
> It doesn't seem to be in my mail archives either.
Here's the same thread in a different list archive: https://marc.info/?t=143483759600001&r=1&w=2
>
> Timur Tabi from CodeAurora is currently
> floating a patch set that makes it possible to remove entire sets of
> lines as "controlled by someone else" (read: ACPI BIOS).
> This will apply to the whole GPIO chip.
> https://marc.info/?l=linux-gpio&m=151379704013464&w=2
>
> This is however under heavy discussion.
Thanks, I'm following that discussion.
Andrew
next prev parent reply other threads:[~2017-12-22 0:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 22:25 Andrew Cooks
2017-12-21 10:11 ` Linus Walleij
2017-12-21 12:12 ` Mika Westerberg
2017-12-22 0:37 ` Andrew Cooks
2017-12-22 6:05 ` Mika Westerberg
2017-12-22 0:44 ` Andrew Cooks [this message]
[not found] ` <CAOdcoTnpiWkPu4_eOJ6bzUE58PqRHw-y5yHY2T8M3Ymp_2v0MQ@mail.gmail.com>
2017-12-22 1:05 ` Andrew Cooks
2017-12-21 13:02 ` Christian Lamparter
2017-12-22 1:17 ` Andrew Cooks
2017-12-22 7:48 ` Linus Walleij
2017-12-22 17:49 ` Christian Lamparter
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=669cceb3-3225-f93a-41bf-5ad9dc22e7fe@opengear.com \
--to=andrew.cooks@opengear.com \
--cc=Ken.Xue@amd.com \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=platypus-sw@opengear.com \
--cc=ranma+kernel@tdiedrich.de \
--cc=sudheesh.mavila@amd.com \
--cc=timur@codeaurora.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
all inboxes | Powered by JetHome®