All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Yang <gary.yang@cixtech.com>
To: Jun Guo <jun.guo@cixtech.com>
Cc: <peter.chen@cixtech.com>, <fugang.duan@cixtech.com>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<vkoul@kernel.org>, <ychuang3@nuvoton.com>, <schung@nuvoton.com>,
	<robin.murphy@arm.com>, <Frank.Li@kernel.org>,
	<dmaengine@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <cix-kernel-upstream@cixtech.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v7 2/2] arm64: dts: cix: add sky1 DMA-350 node with channel IRQ entries
Date: Mon, 20 Jul 2026 10:18:36 +0800	[thread overview]
Message-ID: <al2FfGPKCukLbDIx@gary-System-Product-Name> (raw)
In-Reply-To: <20260521072924.3000282-3-jun.guo@cixtech.com>

On 2026-05-21 15:29, Jun Guo wrote:

> Describe the DMA-350 channel interrupt sources in DT using 8
> interrupt entries, while all entries map to the same GIC SPI
> as wired on this platform.
> 
> Signed-off-by: Jun Guo <jun.guo@cixtech.com>

Applied, thanks!

Gary
> ---
>  arch/arm64/boot/dts/cix/sky1.dtsi | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/cix/sky1.dtsi b/arch/arm64/boot/dts/cix/sky1.dtsi
> index bb5cfb1f2113..823adeef51f1 100644
> --- a/arch/arm64/boot/dts/cix/sky1.dtsi
> +++ b/arch/arm64/boot/dts/cix/sky1.dtsi
> @@ -444,6 +444,20 @@ iomuxc: pinctrl@4170000 {
>  			reg = <0x0 0x04170000 0x0 0x1000>;
>  		};
>  
> +		fch_dmac: dma-controller@4190000 {
> +			compatible = "arm,dma-350";
> +			reg = <0x0 0x4190000 0x0 0x10000>;
> +			interrupts = <GIC_SPI 303 IRQ_TYPE_LEVEL_HIGH 0>,
> +				     <GIC_SPI 303 IRQ_TYPE_LEVEL_HIGH 0>,
> +				     <GIC_SPI 303 IRQ_TYPE_LEVEL_HIGH 0>,
> +				     <GIC_SPI 303 IRQ_TYPE_LEVEL_HIGH 0>,
> +				     <GIC_SPI 303 IRQ_TYPE_LEVEL_HIGH 0>,
> +				     <GIC_SPI 303 IRQ_TYPE_LEVEL_HIGH 0>,
> +				     <GIC_SPI 303 IRQ_TYPE_LEVEL_HIGH 0>,
> +				     <GIC_SPI 303 IRQ_TYPE_LEVEL_HIGH 0>;
> +			#dma-cells = <1>;
> +		};
> +
>  		mbox_ap2se: mailbox@5060000 {
>  			compatible = "cix,sky1-mbox";
>  			reg = <0x0 0x05060000 0x0 0x10000>;
> -- 
> 2.34.1
> 

  reply	other threads:[~2026-07-20  2:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  7:29 [PATCH v7 0/2] dmaengine: arm-dma350: handle shared channel IRQ wiring on sky1 Jun Guo
2026-05-21  7:29 ` [PATCH v7 1/2] dmaengine: arm-dma350: enable ANYCH interrupt for shared IRQ wiring Jun Guo
2026-05-21  7:52   ` sashiko-bot
2026-07-15 12:31   ` Robin Murphy
2026-05-21  7:29 ` [PATCH v7 2/2] arm64: dts: cix: add sky1 DMA-350 node with channel IRQ entries Jun Guo
2026-07-20  2:18   ` Gary Yang [this message]
2026-07-15  7:42 ` [PATCH v7 0/2] dmaengine: arm-dma350: handle shared channel IRQ wiring on sky1 Jun Guo
2026-07-17 12:35 ` (subset) " Vinod Koul

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=al2FfGPKCukLbDIx@gary-System-Product-Name \
    --to=gary.yang@cixtech.com \
    --cc=Frank.Li@kernel.org \
    --cc=cix-kernel-upstream@cixtech.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=fugang.duan@cixtech.com \
    --cc=jun.guo@cixtech.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.chen@cixtech.com \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=schung@nuvoton.com \
    --cc=vkoul@kernel.org \
    --cc=ychuang3@nuvoton.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.