From: Vinod Koul <vkoul@kernel.org>
To: frank.li@oss.nxp.com,
Chaithanya Lagisetty <nagachaithanya9911@gmail.com>
Cc: Frank.Li@kernel.org, orsonzhai@gmail.com,
baolin.wang@linux.alibaba.com, zhang.lyra@gmail.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] dmaengine: sprd: use clk_bulk API to fix clock imbalance
Date: Thu, 10 Sep 2026 19:40:20 +0530 [thread overview]
Message-ID: <178904942062.118320.17575916116147698499.b4-ty@kernel.org> (raw)
In-Reply-To: <20260819053518.2825514-1-nagachaithanya9911@gmail.com>
On Wed, 19 Aug 2026 05:35:18 +0000, Chaithanya Lagisetty wrote:
> sprd_dma_enable() enabled sdev->clk and then the optional ashb_clk. If
> enabling ashb_clk failed, sdev->clk was left enabled: both callers
> (probe and resume) treat a non-zero return as "nothing was enabled" and
> bail out, leaking sdev->clk.
>
> Convert the driver to the clk_bulk API. clk_bulk_prepare_enable()
> enables all clocks and unwinds them on failure, and
> clk_bulk_disable_unprepare() disables them, which fixes the imbalance
> and simplifies the enable/disable paths. Both clocks are fetched with
> devm_clk_bulk_get_optional(); the optional ashb_eb clock simply becomes
> a NULL entry that the bulk helpers treat as a no-op, while the mandatory
> enable clock is still checked explicitly.
>
> [...]
Applied, thanks!
[1/1] dmaengine: sprd: use clk_bulk API to fix clock imbalance
commit: d09cd5e8bbc98969b5333015b45c525078ac0f6f
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-09-10 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 10:53 [PATCH] dmaengine: sprd: fix clock imbalance when enabling ashb_clk fails Chaithanya Lagisetty
2026-08-13 16:39 ` Frank Li
2026-08-16 5:50 ` [PATCH v2] dmaengine: sprd: use clk_bulk API to fix clock imbalance Chaithanya Lagisetty
2026-08-17 14:48 ` Frank Li
2026-08-19 5:35 ` [PATCH v3] " Chaithanya Lagisetty
2026-08-19 15:42 ` Frank Li
2026-09-10 14:10 ` 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=178904942062.118320.17575916116147698499.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dmaengine@vger.kernel.org \
--cc=frank.li@oss.nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nagachaithanya9911@gmail.com \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@gmail.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
all inboxes | Powered by JetHome®