[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYD6pkccYoy90AfzV3KT7oYkBPD2_4ZW-AXzT1eUVpchA@mail.gmail.com>
Date: Thu, 12 Oct 2023 09:25:20 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: AKASHI Takahiro <takahiro.akashi@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
Rob Herring <robh@...nel.org>, sudeep.holla@....com,
cristian.marussi@....com, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, Oleksii_Moisieiev@...m.com,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [RFC v2 5/5] dt-bindings: gpio: Add bindings for pinctrl based
generic gpio driver
On Tue, Oct 10, 2023 at 7:25 AM AKASHI Takahiro
<takahiro.akashi@...aro.org> wrote:
> > We can probably mandate that this has to be inside a pin controller
> > since it is a first.
>
> Yeah, my U-Boot implementation tentatively supports both (inside and
> outside pin controller). But it is not a user's choice, but we should
> decide which way to go.
OK I have decided we are going to put it inside the pin control node,
as a subnode. (I don't expect anyone to object.)
It makes everything easier and clearer for users I think.
Yours,
Linus Walleij
Powered by blists - more mailing lists