linux-kernel - Re: [PATCH v2 0/3] Add initial support for Canaan Kendryte K230 pinctrl

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6a1a3e38-0c6b-4d79-a101-b3292a2ab3be@163.com>
Date: Tue, 8 Oct 2024 16:31:35 +0800
From: Ze Huang <18771902331@....com>
To: Conor Dooley <conor@...nel.org>, Linus Walleij <linus.walleij@...aro.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Paul Walmsley
 <paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
 Albert Ou <aou@...s.berkeley.edu>, linux-gpio@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v2 0/3] Add initial support for Canaan Kendryte K230
 pinctrl

On 10/1/24 8:32 PM, Conor Dooley wrote:
> On Tue, Oct 01, 2024 at 02:27:25PM +0200, Linus Walleij wrote:
>> On Thu, Sep 26, 2024 at 5:58 PM Ze Huang <18771902331@....com> wrote:
>>
>>> This patch series introduces support for the pinctrl driver of the Canaan
>>> K230 SoC. The K230 SoC features 64 IO pins, each of which can be configured
>>> for up to five different functions.
>>>
>>> The controller manages the entire pin configuration and multiplexing
>>> through a single register, which control features such as schmitt trigger,
>>> drive strength, bias pull-up/down, input/output enable, power source, and
>>> mux mode.
>>>
>>> The changes have been tested on CanMV-K230-V1.1 board.
>>>
>>> The pin function definition can be found here [1], and most of the DTS data
>>> was converted from the vendor's code [2].
>> Bindings ACKed and patches look good to I applied patch
>> 1 & 2 to the pin control tree.
>>
>> Please funnel patch 3 through the SoC tree.
>>
>>> prerequisite-message-id: <tencent_22BA0425B4DF1CA1713B62E4423C1BFBF809@...com>
>>> prerequisite-patch-id: 704efc6e76814e1877748959d7319d558c8386c1
>>> prerequisite-patch-id: c2144cf468c57b856830a61615ba6ba501e8ec58
>>> prerequisite-patch-id: ced4a01ccd8ddab2fd308d543ddf47bd1641518a
>>> prerequisite-patch-id: f8b983b301d0c14f1448b9e4c321262a509e061e
>>> prerequisite-patch-id: 834b65b6a2b037daed5cffc6a41963622568dc9c
>>> prerequisite-patch-id: 2401703b57448c9ea2c3dc7650b4502491a28944
>> I don't know about all this stuff but neither bindings or code seems
>> to contain anything that won't compile so I just assume that any of these
>> dependencies are purely for patch 3/3 and I nothing blocks me
>> merging patches 1 & 2 so I just went ahead with that.
> Yah, this should all be cos I haven't yet applied
> https://lore.kernel.org/all/tencent_22BA0425B4DF1CA1713B62E4423C1BFBF809@qq.com/
> as I am waiting for a clock driver to be sorted out.

Thank you very much for your time in reviewing and helping fix the bug!
Indeed, only patch 3 really depends on the previous patches. We are now
working on clock driver. Should we deal with patch 3 after that?