From: Jelly Jia <Jelly.Jia@cixtech.com>
To: vkoul@kernel.org, Frank.Li@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, tglx@kernel.org
Cc: devicetree@vger.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,
radu@rendec.net
Subject: [PATCH v5 3/6] clk: cix: Preserve Sky1 AUDSS interrupt and reset context
Date: Fri, 20 Nov 2026 13:35:26 +0800 [thread overview]
Message-ID: <20261120053529.371923-4-Jelly.Jia@cixtech.com> (raw)
In-Reply-To: <20261120053529.371923-1-Jelly.Jia@cixtech.com>
The AUDSS CRU saves its clock configuration before runtime suspend, but
the save list does not include the AP interrupt gates or software reset
state. If that state is lost across a CRU power transition, restoring
the clocks alone does not restore the configuration of its consumers.
Add INFO_AP_IRQC and INFO_SW_RESETN to the existing save and restore
list so the interrupt gate and reset configuration is preserved with
the rest of the CRU context.
Signed-off-by: Jelly Jia <Jelly.Jia@cixtech.com>
---
drivers/clk/cix/clk-sky1-audss.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/clk/cix/clk-sky1-audss.c b/drivers/clk/cix/clk-sky1-audss.c
index e096b8121df3..1da86f6def4f 100644
--- a/drivers/clk/cix/clk-sky1-audss.c
+++ b/drivers/clk/cix/clk-sky1-audss.c
@@ -18,7 +18,9 @@
#define INFO_CLK_GATE 0x10
#define INFO_CLK_DIV 0x14
#define INFO_CLK_MUX 0x18
+#define INFO_AP_IRQC 0x54
#define INFO_MCLK 0x70
+#define INFO_SW_RESETN 0x78
#define SKY1_AUDSS_CLK_PARENTS_CNT 4
#define SKY1_AUDSS_NUM_CLKS (CLK_MCLK4 + 1)
@@ -28,7 +30,9 @@ static u32 sky1_reg_save[][2] = {
{ INFO_CLK_GATE, 0 },
{ INFO_CLK_DIV, 0 },
{ INFO_CLK_MUX, 0 },
+ { INFO_AP_IRQC, 0 },
{ INFO_MCLK, 0 },
+ { INFO_SW_RESETN, 0 },
};
static const char * const sky1_audss_clk_names[SKY1_AUDSS_CLK_PARENTS_CNT] = {
--
2.54.0
next prev parent reply other threads:[~2026-11-20 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 5:35 [PATCH v5 0/6] soc: cix: Add the Sky1 AUDSS DMA-350 interrupt path Jelly Jia
2026-11-20 5:35 ` [PATCH v5 1/6] dt-bindings: soc: cix: Describe the Sky1 AUDSS DMA IRQ controller Jelly Jia
2026-11-20 5:35 ` [PATCH v5 2/6] irqchip: Add the Sky1 AUDSS auxiliary interrupt controller Jelly Jia
2026-11-20 5:35 ` Jelly Jia [this message]
2026-11-20 5:35 ` [PATCH v5 4/6] clk: cix: Register the Sky1 AUDSS IRQ auxiliary device Jelly Jia
2026-11-20 5:35 ` [PATCH v5 5/6] dt-bindings: dma: arm,dma-350: Document dma-channel-mask Jelly Jia
2026-11-20 5:35 ` [PATCH v5 6/6] dmaengine: arm-dma350: Honour dma-channel-mask 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=20261120053529.371923-4-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=radu@rendec.net \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sboyd@kernel.org \
--cc=tglx@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®