[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cabfb078-8aed-4e4e-8eec-194f2a24df93@amlogic.com>
Date: Wed, 8 Jan 2025 11:14:48 +0800
From: Xianwei Zhao <xianwei.zhao@...ogic.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Neil Armstrong <neil.armstrong@...aro.org>,
Kevin Hilman <khilman@...libre.com>, Jerome Brunet <jbrunet@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Bartosz Golaszewski <brgl@...ev.pl>, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org
Subject: Re: [PATCH v2 2/5] pinctrl: pinconf-generic: Add API for pinmux
propertity in DTS file
Hi Linus,
Thanks for your reply.
On 2025/1/7 23:18, Linus Walleij wrote:
> [ EXTERNAL EMAIL ]
>
> On Thu, Dec 26, 2024 at 8:57 AM Xianwei Zhao via B4 Relay
> <devnull+xianwei.zhao.amlogic.com@...nel.org> wrote:
>
>> From: Xianwei Zhao <xianwei.zhao@...ogic.com>
>>
>> When describing pin mux func through pinmux propertity,
>> a standard API is added for support. The pinmux contains pin
>> identification and mux values, which can include multiple
>> pins. And groups configuration use other word. DTS such as:
>>
>> func-name {
>> group_alias: group-name{
>> pinmux= <pin_id << 8 | mux_value)>,
>> <pin_id << 8 | mux_value)>;
>> bias-pull-up;
>> drive-strength-microamp = <4000>;
>> };
>> };
>>
>> Signed-off-by: Xianwei Zhao <xianwei.zhao@...ogic.com>
>
> There are some build errors, but I really like the path taken with
> the utility function here!
>
I will fix the issue Reported by kernel test robot next version.
> Yours,
> Linus Walleij
Powered by blists - more mailing lists