Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Bough Chen <haibo.chen@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: imx93-9x9-qsb: add CAN support
Date: Mon, 1 Dec 2025 12:10:01 -0500	[thread overview]
Message-ID: <aS3L6cPxHE11FF4p@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <DU0PR04MB94968BBFFF9FC757C177C14E90DFA@DU0PR04MB9496.eurprd04.prod.outlook.com>

On Thu, Nov 27, 2025 at 02:01:47AM +0000, Bough Chen wrote:
> > -----Original Message-----
> > From: Frank Li <frank.li@nxp.com>
> > Sent: 2025年11月27日 0:22
> > To: Bough Chen <haibo.chen@nxp.com>
> > Cc: Shawn Guo <shawnguo@kernel.org>; Sascha Hauer
> > <s.hauer@pengutronix.de>; Pengutronix Kernel Team
> > <kernel@pengutronix.de>; Fabio Estevam <festevam@gmail.com>; Rob
> > Herring <robh@kernel.org>; Krzysztof Kozlowski <krzk+dt@kernel.org>; Conor
> > Dooley <conor+dt@kernel.org>; imx@lists.linux.dev;
> > linux-arm-kernel@lists.infradead.org; devicetree@vger.kernel.org;
> > linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH] arm64: dts: imx93-9x9-qsb: add CAN support
> >
> > On Wed, Nov 26, 2025 at 02:20:07PM +0800, Haibo Chen wrote:
> >
> > subject suggested,  add CAN support overlay file
> >
> > > CAN1 and Micfil share pins on imx93-9x9-qsb board, use TMUX1574RSVR to
> > > control the connection: put sel to high, select CAN1, put sel to low,
> > > select Micfil. In default, sel keep low.
> > >
> > > To support CAN1, need to put the sel to high. Besides, CAN1 use phy
> > > TJA1057GT/3.
> > >
> > > ---
> > > Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
> > > ---
> > >  arch/arm64/boot/dts/freescale/Makefile             |  2 +
> > >  .../boot/dts/freescale/imx93-9x9-qsb-can1.dtso     | 63
> > ++++++++++++++++++++++
> > >  2 files changed, 65 insertions(+)
> > >
> > > diff --git a/arch/arm64/boot/dts/freescale/Makefile
> > > b/arch/arm64/boot/dts/freescale/Makefile
> > > index
> > >
> > f30d3fd724d0ce6b38f7bef10e3970ac34f70f4a..1142d3312c8651b4292837bce3
> > cb
> > > e46ab95f7e09 100644
> > > --- a/arch/arm64/boot/dts/freescale/Makefile
> > > +++ b/arch/arm64/boot/dts/freescale/Makefile
> > > @@ -373,7 +373,9 @@ dtb-$(CONFIG_ARCH_MXC) +=
> > > imx91-tqma9131-mba91xxca.dtb
> > >  dtb-$(CONFIG_ARCH_MXC) += imx93-9x9-qsb.dtb
> > >
> > >  imx93-9x9-qsb-i3c-dtbs += imx93-9x9-qsb.dtb imx93-9x9-qsb-i3c.dtbo
> > > +imx93-9x9-qsb-can1-dtbs += imx93-9x9-qsb.dtb imx93-9x9-qsb-can1.dtbo
> >
> > Keep order by alphabet.
> >
> > >  dtb-$(CONFIG_ARCH_MXC) += imx93-9x9-qsb-i3c.dtb
> > > +dtb-$(CONFIG_ARCH_MXC) += imx93-9x9-qsb-can1.dtb
> >
> > the same here
> >
> > can1 should before i3c.
>
> Okay
>
> >
> > >
> > >  dtb-$(CONFIG_ARCH_MXC) += imx93-11x11-evk.dtb
> > >  dtb-$(CONFIG_ARCH_MXC) += imx93-14x14-evk.dtb diff --git
> > > a/arch/arm64/boot/dts/freescale/imx93-9x9-qsb-can1.dtso
> > > b/arch/arm64/boot/dts/freescale/imx93-9x9-qsb-can1.dtso
> > > new file mode 100644
> > > index
> > >
> > 0000000000000000000000000000000000000000..62d4fa6c21d794f91da59f51
> > 1d6f
> > > 0162037e9271
> > > --- /dev/null
> > > +++ b/arch/arm64/boot/dts/freescale/imx93-9x9-qsb-can1.dtso
> > > @@ -0,0 +1,63 @@
> > ...
> > > +
> > > +&pcal6524 {
> > > +	/*
> > > +	 * mic-can-sel-hog have property 'output-low', dt overlay don't
> > > +	 * support /delete-property/. Both 'output-low' and 'output-high'
> > > +	 * will be exist under hog nodes if overlay file set 'output-high'.
> > > +	 * Workaround is disable this hog and create new hog with
> > > +	 * 'output-high'.
> > > +	 */
> > > +	mic-can-sel-hog {
> > > +		status = "disabled";
> > > +	};
> >
> > are you sure 'status' work for hogs?
>
> Yes, I test on board, this method works.
>

Okay, I just want to make sure it works.

Frank

> Any better solution?
>
> Regards
> Haibo Chen
> >
> > Frank
> > > +
> > > +	/*
> > > +	 * Config the MIC/CAN_SEL to high, chose B
> > > +	 * port, connect to CAN.
> > > +	 */
> > > +	mic-can-high-sel-hog {
> > > +		gpio-hog;
> > > +		gpios = <0x11 0x00>;
> > > +		output-high;
> > > +	};
> > > +};
> > >
> > > ---
> > > base-commit: 422f3140bbcb657e1b86c484296972ab76f6d1ff
> > > change-id: 20251125-b4-9391-can-dts-2f4849978fc2
> > >
> > > Best regards,
> > > --
> > > Haibo Chen <haibo.chen@nxp.com>
> > >


      reply	other threads:[~2025-12-01 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  6:20 [PATCH] arm64: dts: imx93-9x9-qsb: add CAN support Haibo Chen
2025-11-26 16:22 ` Frank Li
2025-11-27  2:01   ` Bough Chen
2025-12-01 17:10     ` Frank Li [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=aS3L6cPxHE11FF4p@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=haibo.chen@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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