[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<MA0P287MB28221065B41ABE67768B98DEFE722@MA0P287MB2822.INDP287.PROD.OUTLOOK.COM>
Date: Wed, 17 Jan 2024 17:03:20 +0800
From: Chen Wang <unicorn_wang@...look.com>
To: Jisheng Zhang <jszhang@...nel.org>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Paul Walmsley
<paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Chao Wei <chao.wei@...hgo.com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org
Subject: Re: [PATCH 0/2] riscv: sophgo: add pinctrl support for cv1800b
On 2023/11/13 8:57, Jisheng Zhang wrote:
> This series adds pinctrl support for cv1800b reusing the
> pinctrl-single driver.
>
> Jisheng Zhang (2):
> riscv: dts: cv1800b: add pinctrl node for cv1800b
> riscv: dts: sophgo: set pinctrl for uart0
>
> arch/riscv/boot/dts/sophgo/cv-pinctrl.h | 19 +++++++++++++++++++
> .../boot/dts/sophgo/cv1800b-milkv-duo.dts | 11 +++++++++++
> arch/riscv/boot/dts/sophgo/cv1800b.dtsi | 10 ++++++++++
> 3 files changed, 40 insertions(+)
> create mode 100644 arch/riscv/boot/dts/sophgo/cv-pinctrl.h
One question, when we use "pinctrl-single" driver, should we enable
CONFIG_PINCTRL_SINGLE? Or just leave it to package vendor to configure
by themselves?
Powered by blists - more mailing lists