From: Anup Kulkarni <anup.kulkarni@oss.qualcomm.com>
To: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: mukesh.savaliya@oss.qualcomm.com,
viken.dadhaniya@oss.qualcomm.com,
Anup Kulkarni <anup.kulkarni@oss.qualcomm.com>
Subject: [PATCH v1] arm64: dts: qcom: Enable CAN RX via GPIO expander
Date: Thu, 2 Apr 2026 16:22:53 +0530 [thread overview]
Message-ID: <20260402105253.3009382-1-anup.kulkarni@oss.qualcomm.com> (raw)
Few CAN controllers, part of RTSS sub-system on LeMans, route
their RX signal through a I2C GPIO expander at address 0x3b.
RTSS subsystem is an MCU like sub-system on LeMans with independent
booting capability through OSPI interface and supports peripherals like
RGMII, CAN-FD, UART, I2C, SPI etc.
Describe this hardware wiring by configuring the expander GPIO 4 pin as
hog with output-high, asserting the selected line during boot.
Signed-off-by: Anup Kulkarni <anup.kulkarni@oss.qualcomm.com>
---
arch/arm64/boot/dts/qcom/lemans-evk.dts | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/lemans-evk.dts b/arch/arm64/boot/dts/qcom/lemans-evk.dts
index a1ef4eba2a20..b8371bdf9933 100644
--- a/arch/arm64/boot/dts/qcom/lemans-evk.dts
+++ b/arch/arm64/boot/dts/qcom/lemans-evk.dts
@@ -615,6 +615,13 @@ expander3: gpio@3b {
interrupts-extended = <&tlmm 39 IRQ_TYPE_LEVEL_LOW>;
pinctrl-0 = <&expander3_int>;
pinctrl-names = "default";
+
+ rtss-can-sel-hog {
+ gpio-hog;
+ gpios = <4 GPIO_ACTIVE_HIGH>;
+ output-high;
+ line-name = "rtss-can-sel";
+ };
};
eeprom@50 {
--
2.34.1
next reply other threads:[~2026-04-02 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 10:52 Anup Kulkarni [this message]
2026-04-14 15:07 ` [PATCH v1] arm64: dts: qcom: Enable CAN RX via GPIO expander Konrad Dybcio
2026-04-14 16:08 ` Dmitry Baryshkov
2026-04-14 16:20 ` Konrad Dybcio
2026-04-14 18:09 ` Dmitry Baryshkov
2026-04-15 8:56 ` Konrad Dybcio
2026-04-16 12:11 ` Anup Kulkarni
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=20260402105253.3009382-1-anup.kulkarni@oss.qualcomm.com \
--to=anup.kulkarni@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=viken.dadhaniya@oss.qualcomm.com \
/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