From: Jelly Jia <Jelly.Jia@cixtech.com>
To: vkoul@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, robin.murphy@arm.com, sboyd@kernel.org,
bmasney+clk@redhat.com, jbrunet+clk@baylibre.com
Cc: devicetree@vger.kernel.org, Frank.Li@kernel.org,
cix-kernel-upstream@cixtech.com, dmaengine@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jelly.Jia@cixtech.com,
linux-clk@vger.kernel.org, joakim.zhang@cixtech.com
Subject: [PATCH v3 0/5] soc: cix: Add the Sky1 AUDSS DMA-350 interrupt path
Date: Fri, 6 Nov 2026 09:35:15 +0800 [thread overview]
Message-ID: <20261106013520.1134450-1-Jelly.Jia@cixtech.com> (raw)
Hello,
This series adds the CIX Sky1 AUDSS DMA-350 and its interrupt path through
the audio subsystem CRU. The DMA, CRU and DT changes are posted together
because the controller depends on the CRU interrupt gates, while
dma-channel-mask describes which channels Linux may use. Keeping them
together allows the complete interrupt path to be reviewed. If separate
submissions are preferred, they can be split in the next revision. No
audio client drivers are added here.
It depends on the companion v6 series, "dmaengine: arm-dma350: Add slave
support and Sky1 integration", for slave/cyclic transfers and integration
clock and reset support. Apply that series first.
The CRU gates the AP interrupt path for each of the eight DMA channels
and combines enabled inputs onto GIC SPI 230. Channels may be reserved
for firmware or the DSP; dma-channel-mask limits those available to Linux.
The AP gate bits control interrupt delivery, not channel ownership, and
this series does not implement runtime AP/DSP ownership transfer.
Conor suggested interrupt-map when the routing was described as being
configured by firmware. This series instead manages each AP gate via
irq_mask and irq_unmask. A static interrupt-map alone would translate
child specifiers to the shared GIC SPI but would not provide that gate
control. Model the CRU as an irqchip so the register owner manages the
gates, without CRU register accesses in the DMA driver. Feedback on this
choice of irqchip rather than a static interrupt-map is welcome.
The gate register exposes no per-channel pending status. The chained
handler polls every enabled child, and each DMA channel handler checks
its own status. The children use level flow handling with IRQ_IS_POLLED
so disabled and oneshot-threaded interrupts remain masked, while inactive
channels returning IRQ_NONE do not accumulate spurious-IRQ counts.
The AUDSS DT describes a 1 MiB peripheral window and a 512 MiB DRAM window
with dma-ranges. The prerequisite series allocates linked commands from
a coherent DMA pool, so successfully allocated commands are reachable
through the controller's DMA address windows.
Changes since v2:
- Drop the unnecessary 32-channel guard from the channel-mask check:
DMA-350 implements at most eight channels. (Frank.)
- Use cix,sky1-dma350 with an arm,dma-350 fallback in the AUDSS node,
matching the companion binding update. (Frank.)
- Update the prerequisite to DMA v6. The CRU irqchip and both AUDSS
bindings are unchanged; retain Krzysztof's Reviewed-by for the mask
binding.
Previous version:
https://lore.kernel.org/r/20261104124437.296753-1-Jelly.Jia@cixtech.com
Jelly Jia (5):
dt-bindings: soc: cix: Describe the Sky1 AUDSS DMA IRQ controller
clk: cix: Handle Sky1 AUDSS DMA interrupt gates as an irqchip
dt-bindings: dma: arm,dma-350: Document dma-channel-mask
dmaengine: arm-dma350: Honour dma-channel-mask
arm64: dts: cix: Add the Sky1 AUDSS DMA-350 integration
.../devicetree/bindings/dma/arm,dma-350.yaml | 3 +
.../bindings/soc/cix/cix,sky1-audss-cru.yaml | 37 +++-
arch/arm64/boot/dts/cix/sky1.dtsi | 26 ++-
drivers/clk/cix/Kconfig | 1 +
drivers/clk/cix/clk-sky1-audss.c | 181 +++++++++++++++++-
drivers/dma/arm-dma350.c | 19 +-
6 files changed, 260 insertions(+), 7 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
prerequisite-patch-id: aad1bc3c30a4825048143a3e0395e696201548e9
prerequisite-patch-id: 2185a7427f3937ac50c3a68c96eb5494e29f027e
prerequisite-patch-id: 62385082b538a0f354f44a70c2c251771238e047
prerequisite-patch-id: fe66cae6b72d01c2e405e991bbd49b519f8bf577
prerequisite-patch-id: 4db79975ed1255550e9a7712354a9db233257c09
--
2.54.0
next reply other threads:[~2026-11-06 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:35 Jelly Jia [this message]
2026-11-06 1:35 ` [PATCH v3 1/5] dt-bindings: soc: cix: Describe the Sky1 AUDSS DMA IRQ controller Jelly Jia
2026-11-06 1:35 ` [PATCH v3 2/5] clk: cix: Handle Sky1 AUDSS DMA interrupt gates as an irqchip Jelly Jia
2026-11-06 1:35 ` [PATCH v3 3/5] dt-bindings: dma: arm,dma-350: Document dma-channel-mask Jelly Jia
2026-11-06 1:35 ` [PATCH v3 4/5] dmaengine: arm-dma350: Honour dma-channel-mask Jelly Jia
2026-11-06 1:35 ` [PATCH v3 5/5] arm64: dts: cix: Add the Sky1 AUDSS DMA-350 integration Jelly Jia
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=20261106013520.1134450-1-Jelly.Jia@cixtech.com \
--to=jelly.jia@cixtech.com \
--cc=Frank.Li@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=joakim.zhang@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sboyd@kernel.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®