Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>, Peng Fan <peng.fan@nxp.com>,
	 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>
Cc: imx@lists.linux.dev, dmaengine@vger.kernel.org,
	 devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org, Joy Zou <joy.zou@nxp.com>
Subject: Re: (subset) [PATCH v2 0/3] dmaengine: fsl-edma: add error irq to help debug problem
Date: Thu, 24 Apr 2025 11:06:59 +0530	[thread overview]
Message-ID: <174547301902.316124.419798258552986948.b4-ty@kernel.org> (raw)
In-Reply-To: <20250407-edma_err-v2-0-9d7e5b77fcc4@nxp.com>


On Mon, 07 Apr 2025 12:46:34 -0400, Frank Li wrote:
> Change binding to support optional error irq.
> Add error irq handle for fsl-edma drivers.
> imx93 dts add dma error irq interupt.
> 
> 

Applied, thanks!

[1/3] dt-bindings: dma: fsl-edma: increase maxItems of interrupts and interrupt-names
      commit: a9ea01f28408169431dd3e6464ed2e48539f4280
[2/3] dmaegnine: fsl-edma: add edma error interrupt handler
      commit: d175222f5e90b7e1f23713378823c338fabb3258

Best regards,
-- 
~Vinod




      parent reply	other threads:[~2025-04-24  5:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 16:46 [PATCH v2 0/3] dmaengine: fsl-edma: add error irq to help debug problem Frank Li
2025-04-07 16:46 ` [PATCH v2 1/3] dt-bindings: dma: fsl-edma: increase maxItems of interrupts and interrupt-names Frank Li
2025-04-07 23:50   ` Rob Herring (Arm)
2025-04-07 16:46 ` [PATCH v2 2/3] dmaegnine: fsl-edma: add edma error interrupt handler Frank Li
2025-04-07 16:46 ` [PATCH v2 3/3] arm64: dtsi: imx93: add edma error interrupt support Frank Li
2025-04-10  7:50   ` Alberto Merciai
2025-04-24  5:36 ` Vinod Koul [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=174547301902.316124.419798258552986948.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=joy.zou@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --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 \
    /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