public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Joy Zou <joy.zou@nxp.com>
To: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>, Frank Li <Frank.Li@nxp.com>,
	Peng Fan <peng.fan@nxp.com>, Ye Li <ye.li@nxp.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx95: Reserve eDMA channels 0-1 for V2X
Date: Wed, 21 Jan 2026 14:27:55 +0800	[thread overview]
Message-ID: <20260121062755.GA2474386@shlinux88> (raw)
In-Reply-To: <993363fb-8ce4-4a89-b6c4-8fbf181ad410@gmail.com>

On Tue, Jan 20, 2026 at 04:30:32AM -0800, Laurentiu Mihalcea wrote:
> 
> On 1/20/2026 12:35 AM, Joy Zou wrote:
> > Reserve eDMA channels 0 and 1 on the AXI eDMA controller for exclusive
> > use by V2X (Vehicle-to-Everything) fast hash operations.
> >
> > Signed-off-by: Joy Zou <joy.zou@nxp.com>
> > ---
> > ---
> >  arch/arm64/boot/dts/freescale/imx95.dtsi | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi b/arch/arm64/boot/dts/freescale/imx95.dtsi
> > index 55e2da094c889fc7c1096d0e36f31ae118d2a982..24d02aa18b2f480bbffdc30bc41c658fb3aaf67a 100644
> > --- a/arch/arm64/boot/dts/freescale/imx95.dtsi
> > +++ b/arch/arm64/boot/dts/freescale/imx95.dtsi
> > @@ -631,6 +631,7 @@ edma2: dma-controller@42000000 {
> >  				reg = <0x42000000 0x210000>;
> >  				#dma-cells = <3>;
> >  				dma-channels = <64>;
> > +				dma-channel-mask = <0x3>;
> >  				interrupts = <GIC_SPI 128 IRQ_TYPE_LEVEL_HIGH>,
> >  					     <GIC_SPI 128 IRQ_TYPE_LEVEL_HIGH>,
> >  					     <GIC_SPI 129 IRQ_TYPE_LEVEL_HIGH>,
> >
> > ---
> > base-commit: d08c85ac8894995d4b0d8fb48d2f6a3e53cd79ab
> > change-id: 20260120-b4-imx95-v2x-3e01c7bc6881
> >
> > Best regards,
> 
> 
> Thanks, this fixes the kernel panics on MX95-15x15-FRDM and MX95-19x19-EVK after
> 
> AP access is removed from said channels via SM.
> 
> 
> Just one thing: can you do this change for imx95-19x19-evk-sof.dts as well?
> 
> If not, I'll just send a patch for that later on.
Will change imx95-19x19-evk-sof.dts.
BR
Joy Zou
> 
> 
> Either way:
> 
> Reviewed-by: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
> 
> Tested-by: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com> # MX95-15x15-FRDM, MX95-19x19-EVK
> 

  reply	other threads:[~2026-01-21  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20  8:35 [PATCH] arm64: dts: imx95: Reserve eDMA channels 0-1 for V2X Joy Zou
2026-01-20 12:30 ` Laurentiu Mihalcea
2026-01-21  6:27   ` Joy Zou [this message]
2026-01-20 16:25 ` Frank Li
2026-01-21 10:31   ` Joy Zou

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=20260121062755.GA2474386@shlinux88 \
    --to=joy.zou@nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=laurentiumihalcea111@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=ye.li@nxp.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