From: Linus Walleij <linus.walleij@linaro.org>
To: "Alexander Graf" <agraf@suse.de>,
"Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Grant Likely <grant.likely@arm.com>,
Mark Brown <broonie@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
boot-architecture@lists.linaro.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH] driver core: make deferring probe forever optional
Date: Mon, 14 May 2018 00:01:31 +0200 [thread overview]
Message-ID: <CACRpkdaYN-wKErERP_65T2NH6L-+8O_ugSgg7pXfkaLkn1A2KQ@mail.gmail.com> (raw)
In-Reply-To: <91dad272-e07d-2ab6-2afa-538294e9cefa@suse.de>
On Wed, May 9, 2018 at 11:44 AM, Alexander Graf <agraf@suse.de> wrote:
> On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
>> Can you please name platform that has enough support for Alexander to
>> care about backwards and forwards compatibility but lacks a pinctrl
>> driver.
>
> ZynqMP is one example that immediately comes to my mind. I'm sure there are
> others too.
Why isn't that using drivers/pinctrl/pinctrl-zynq.c?
How is it so very different from (old) Zynq as it is already using
the same GPIO driver?
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-05-13 22:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 21:31 [RFC PATCH] driver core: make deferring probe forever optional Rob Herring
2018-05-01 22:08 ` Greg Kroah-Hartman
2018-05-02 11:40 ` Robin Murphy
2018-05-02 14:48 ` Rob Herring
2018-05-02 18:49 ` Robin Murphy
2018-05-05 1:25 ` Mark Brown
2018-05-07 13:37 ` Rob Herring
2018-05-02 13:16 ` Alexander Graf
2018-05-07 18:31 ` Bjorn Andersson
2018-05-07 19:55 ` Rob Herring
2018-05-07 22:34 ` Bjorn Andersson
2018-05-09 9:18 ` Mark Brown
2018-05-09 9:57 ` Alexander Graf
2018-05-09 22:34 ` Rob Herring
2018-05-09 22:30 ` Rob Herring
2018-05-09 9:44 ` Alexander Graf
2018-05-13 22:01 ` Linus Walleij [this message]
2018-05-14 7:37 ` Alexander Graf
2018-05-14 12:44 ` Michal Simek
2018-05-16 14:38 ` 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=CACRpkdaYN-wKErERP_65T2NH6L-+8O_ugSgg7pXfkaLkn1A2KQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=agraf@suse.de \
--cc=bjorn.andersson@linaro.org \
--cc=boot-architecture@lists.linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=soren.brinkmann@xilinx.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).