[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZqSm-xfo8a8aFUe-Mbaw9tM+OmCAF3KWjOVDfC=oWj+Q@mail.gmail.com>
Date: Tue, 19 Jan 2021 11:20:24 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Saravana Kannan <saravanak@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
linux-tegra <linux-tegra@...r.kernel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Jon Hunter <jonathanh@...dia.com>,
Android Kernel Team <kernel-team@...roid.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] of: property: Add fw_devlink support for "gpio" and
"gpios" binding
On Tue, Jan 19, 2021 at 9:50 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> > Can we pull this into driver-core-next please? It fixes issues on some
> > boards with fw_devlink=on.
>
> On r8a77951-salvator-xs.dts, it introduces one more failure:
>
> OF: /soc/i2c@...d8000/gpio@...pcie-sata-switch-hog: could not get
> #gpio-cells for /cpus/cpu@102
>
> Seems like it doesn't parse gpios properties in GPIO hogs correctly.
Could it be that the code assumes no self-referencing phandles?
(Just guessing...)
Yours,
Linus Walleij
Powered by blists - more mailing lists