On Mon, Mar 8, 2021 at 7:37 PM Rob Herring wrote:
> Can we remove the ones we have already for GPIO?
I think we would get pretty hard pushback if we attempt that.
We have all these drivers that utilize it:
gpio-clps711x.c:id = of_alias_get_id(np, "gpio");
gpio-mvebu.c: id = of_alias_g
On Tue, Mar 02, 2021 at 05:21:23PM +0100, Linus Walleij wrote:
> On Tue, Mar 2, 2021 at 2:18 AM Alexander Sverdlin
> wrote:
>
> > Currently the naming of the GPIO chips depends on their order in the DT,
> > but also on the kernel version (I've noticed the change from v5.10.x to
> > v5.11). Honor
On Tue, Mar 2, 2021 at 2:18 AM Alexander Sverdlin
wrote:
> Currently the naming of the GPIO chips depends on their order in the DT,
> but also on the kernel version (I've noticed the change from v5.10.x to
> v5.11). Honor the persistent enumeration in the "aliases" node like other
> GPIO drivers
On 02/03/2021 03:18, Alexander Sverdlin wrote:
Currently the naming of the GPIO chips depends on their order in the DT,
but also on the kernel version (I've noticed the change from v5.10.x to
v5.11). Honor the persistent enumeration in the "aliases" node like other
GPIO drivers do.
Signed-off
Currently the naming of the GPIO chips depends on their order in the DT,
but also on the kernel version (I've noticed the change from v5.10.x to
v5.11). Honor the persistent enumeration in the "aliases" node like other
GPIO drivers do.
Signed-off-by: Alexander Sverdlin
---
Yes, I noticed checkpat
5 matches
Mail list logo
