[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170531083523.GD6735@localhost>
Date: Wed, 31 May 2017 10:35:23 +0200
From: Johan Hovold <johan@...nel.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Johan Hovold <johan@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Peter Chen <peter.chen@...escale.com>,
Rob Herring <robh@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Sricharan R <sricharan@...eaurora.org>,
Zhang Rui <rui.zhang@...el.com>,
Eduardo Valentin <edubezval@...il.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/7] driver core: fix automatic pinctrl management
On Wed, May 31, 2017 at 02:39:28AM +0200, Linus Walleij wrote:
> On Tue, May 30, 2017 at 6:25 PM, Johan Hovold <johan@...nel.org> wrote:
>
> > Commit ab78029ecc34 ("drivers/pinctrl: grab default handles from device
> > core") added automatic pin-control management to driver core by looking
> > up and setting any default pinctrl state found in device tree while a
> > device is being probed.
>
> Actually we do not just support device tree, but also passing pin control
> states from board files. It is handled by the core all the same.
> So it's not a device tree thing.
>
> One of those days we will have ACPI passing state tables too...
>
> But I understand what you mean.
Yes, I could have mentioned board files, but this problem only applies
to device-tree descriptions (for the time being at least).
> > Fix this by checking the new of_node_reused flag and skipping automatic
> > pinctrl configuration during probe if set.
>
> Seems like a solid idea. I hope we don't need another quirk for ACPI.
We should be able to just generalise and rename the flag (or add a
second one) if it turns out ACPI needs this too.
> Acked-by: Linus Walleij <linus.walleij@...aro.org>
Thanks,
Johan
Powered by blists - more mailing lists