[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaYN-wKErERP_65T2NH6L-+8O_ugSgg7pXfkaLkn1A2KQ@mail.gmail.com>
Date: Mon, 14 May 2018 00:01:31 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Alexander Graf <agraf@...e.de>,
Sören Brinkmann <soren.brinkmann@...inx.com>
Cc: Bjorn Andersson <bjorn.andersson@...aro.org>,
Rob Herring <robh@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Grant Likely <grant.likely@....com>,
Mark Brown <broonie@...nel.org>,
Stephen Boyd <sboyd@...nel.org>,
boot-architecture@...ts.linaro.org,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC PATCH] driver core: make deferring probe forever optional
On Wed, May 9, 2018 at 11:44 AM, Alexander Graf <agraf@...e.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
Powered by blists - more mailing lists