The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Anup Kulkarni <anup.kulkarni@oss.qualcomm.com>
Cc: dmitry.baryshkov@oss.qualcomm.com, 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,  mukesh.savaliya@oss.qualcomm.com,
	viken.dadhaniya@oss.qualcomm.com
Subject: Re: [PATCH v2] arm64: dts: qcom: Enable CAN RX via GPIO expander
Date: Thu, 7 May 2026 16:10:25 -0500	[thread overview]
Message-ID: <afz-FMEGqMQFw7iH@baldur> (raw)
In-Reply-To: <20260507115324.1814329-1-anup.kulkarni@oss.qualcomm.com>

On Thu, May 07, 2026 at 05:23:24PM +0530, Anup Kulkarni wrote:

The subject prefix is there to quickly inform the reader of "git log
--oneline" what area is being changed. Add "lemans-evk" to match other
changes in this file.

> Few CAN controllers, part of RTSS sub-system on LeMans, route
> their RX signal through a I2C GPIO expander at address 0x3b.

If only a few of them route their RX signal through some I2C GPIO
expander, what are the other ones doing? And how does this relate to a
gpio hog?

> 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.
> 

https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
has the following statement in the first paragraph:
"Convince the reviewer that there is a problem worth fixing and that it
makes sense for them to read past the first paragraph."

> Describe LeMans EVK hardware  wiring by configuring the

Double space...

> expander GPIO 4 pin as hog with output-high,

You're not describing the wiring, you're hogging a GPIO to be high.

> asserting the selected line during boot.

But does that GPIO relate to RTSS, the CAN controller, the RX signal,
some form of chip select? Why should this pin be high?

Regards,
Bjorn

> 
> Signed-off-by: Anup Kulkarni <anup.kulkarni@oss.qualcomm.com>
> ---
> v1->v2
> - Fixed commit text to include platform name.
> ---
>  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 c665db6a4595..34dfc8d22b6a 100644
> --- a/arch/arm64/boot/dts/qcom/lemans-evk.dts
> +++ b/arch/arm64/boot/dts/qcom/lemans-evk.dts
> @@ -616,6 +616,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
> 

      reply	other threads:[~2026-05-07 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 11:53 [PATCH v2] arm64: dts: qcom: Enable CAN RX via GPIO expander Anup Kulkarni
2026-05-07 21:10 ` Bjorn Andersson [this message]

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=afz-FMEGqMQFw7iH@baldur \
    --to=andersson@kernel.org \
    --cc=anup.kulkarni@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --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