Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Icenowy Zheng" <zhengxingda@iscas.ac.cn>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 4/5] riscv: dts: thead: Add IO labels for the IO expansion on I2C1
Date: Tue, 14 Jul 2026 07:56:49 +0000	[thread overview]
Message-ID: <20260714075649.D17CA1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260714074515.1959352-5-zhengxingda@iscas.ac.cn>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `gpio-line-names` array added for `ioexp2` incorrectly labels pin 4 as `wl_host_wake` and pin 7 as `bt_host_wake`. This is physically and logically incorrect because the PCA9557 IO expander lacks interrupt output capability, meaning it cannot be used to receive asynchronous wake signals from peripherals to wake the host. Furthermore, pin 4 is already configured in the base device tree as a `reset-gpios` output for the `wifi_pwrseq` node, directly contradicting the input nature of a host wake signal.
--

--- Patch [4]: [PATCH v2 4/5] riscv: dts: thead: Add IO labels for the IO expansion on I2C1 ---
commit 0fffc115b12752f1a08b3dcb530cafc2d17759f7
Author: Emil Renner Berthing <emil.renner.berthing@canonical.com>

riscv: dts: thead: Add IO labels for the IO expansion on I2C1

This commit adds labels for GPIOs on the IO expansion chip on the I2C1 bus.

> diff --git a/arch/riscv/boot/dts/thead/th1520-lichee-pi-4a.dts b/arch/riscv/boot/dts/thead/th1520-lichee-pi-4a.dts
> index 74b120c6b063a..78f5979a56c14 100644
> --- a/arch/riscv/boot/dts/thead/th1520-lichee-pi-4a.dts
> +++ b/arch/riscv/boot/dts/thead/th1520-lichee-pi-4a.dts
> @@ -128,6 +128,14 @@ ioexp2: gpio@18 {
>  		reg = <0x18>;
>  		gpio-controller;
>  		#gpio-cells = <2>;
> +		gpio-line-names = "",
> +				  "cam0_reset",
> +				  "cam1_reset",
> +				  "cam2_reset",
> +				  "wl_host_wake",
> +				  "bt_resetn",
> +				  "",
> +				  "bt_host_wake";

[Severity: Low]
The PCA9557 IO expander lacks interrupt output capability, meaning it cannot
receive asynchronous wake signals from peripherals to wake the host.

Additionally, pin 4 is already configured as a reset output in the base
device tree for the wifi_pwrseq node:

arch/riscv/boot/dts/thead/th1520-lichee-pi-4a.dts:
	wifi_pwrseq: wifi-pwrseq {
		...
		reset-gpios = <&ioexp2 4 GPIO_ACTIVE_LOW>;
	};

This configuration contradicts the input nature of a host wake signal.

Are the labels wl_host_wake and bt_host_wake correct for this IO expander?

>  	};
>  };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260714074515.1959352-1-zhengxingda@iscas.ac.cn?part=4

  reply	other threads:[~2026-07-14  7:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  7:45 [PATCH v2 0/5] Add remaining IO expansions on Lichee Pi 4A Icenowy Zheng
2026-07-14  7:45 ` [PATCH v2 1/5] riscv: dts: thead: th1520: remove pclk for I2C1 Icenowy Zheng
2026-07-14  7:45 ` [PATCH v2 2/5] riscv: dts: thead: Add TH1520 I2C nodes Icenowy Zheng
2026-07-14  7:45 ` [PATCH v2 3/5] riscv: dts: thead: lpi4a: sort nodes Icenowy Zheng
2026-07-14  7:45 ` [PATCH v2 4/5] riscv: dts: thead: Add IO labels for the IO expansion on I2C1 Icenowy Zheng
2026-07-14  7:56   ` sashiko-bot [this message]
2026-07-14  7:45 ` [PATCH v2 5/5] riscv: dts: thead: Add remaining Lichee Pi 4A IO expansions Icenowy Zheng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260714075649.D17CA1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=zhengxingda@iscas.ac.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox