[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fc297c1b-1d7b-9f22-ca9f-16d288eee5ac@theobroma-systems.com>
Date: Wed, 6 Sep 2023 10:27:12 +0200
From: Quentin Schulz <quentin.schulz@...obroma-systems.com>
To: Rob Herring <robh@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>
Cc: linux-rockchip@...ts.infradead.org,
Heiko Stuebner <heiko@...ech.de>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-gpio@...r.kernel.org,
kernel@...gutronix.de,
Michael Riesch <michael.riesch@...fvision.net>,
Linus Walleij <linus.walleij@...aro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>
Subject: Re: [PATCH 2/3] dt-bindings: pinctrl: rockchip: Add io domain
properties
Hi Rob,
On 9/5/23 20:14, Rob Herring wrote:
> On Mon, Sep 04, 2023 at 01:58:15PM +0200, Sascha Hauer wrote:
>> Add rockchip,io-domains property to the Rockchip pinctrl driver. This
>> list of phandles points to the IO domain device(s) the pins of the
>> pinctrl driver are supplied from.
>
> Is there an actual need for multiple IO devices with multiple pinctrl
> blocks? If not, you don't need a property, just lookup the IO domain
> node by compatible.
>
Yes. There can be multiple IO domain devices on Rockchip SoCs and we
typically have only one pinctrl controller. Each pinctrl "pin" (for a
lack of the appropriate term to use here) belongs to one domain of one
of the IO domain controller/device.
However what I don't like here is that we do not explicit this link
between the pinctrl "pin" and the IO domain controller it belongs to
(even less so on which domain of the IO domain controller, which to be
fair we do not represent in the DT at the moment except through a
phandle property in the IO domain controller, c.f.
https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/bindings/power/rockchip-io-domain.yaml#L84).
Cheers,
Quentin
Powered by blists - more mailing lists