From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/8] ASoC: SDCA: export PM helpers keyed on sdca_class_drv
Date: Fri, 25 Sep 2026 16:11:15 +0100 [thread overview]
Message-ID: <512dc68e-d1cf-4d69-a8f7-52eee01e1dcc@oss.qualcomm.com> (raw)
In-Reply-To: <20260918134942.555421F000FF@smtp.kernel.org>
On 9/18/26 2:49 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] sdca_class: code and commit message mismatch for pm_ops export
This is fixed in v5.
--srini
> --
>
> commit 43543cd6fb0171b62979b93506768ae9a2b2e709
> Author: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
>
> ASoC: SDCA: export PM helpers keyed on sdca_class_drv
>
> The class PM callbacks pull sdca_class_drv out of drvdata, so the
> built-in class_sdw_driver owns the drvdata slot. This blocks codec
> drivers that want to embed sdca_class_drv in their own private struct.
> Split the four callbacks into exported helpers that take a
> struct sdca_class_drv * directly.
>
>> For the built-in class_sdw_driver, add small dev_pm_ops wrappers that
>> fetch drv from drvdata, wire them into sdca_class_pm_ops, and export
>> the ops so any generic SDCA slave can pick them up as-is.
>
>> diff --git a/sound/soc/sdca/sdca_class.c b/sound/soc/sdca/sdca_class.c
>> index d7444f442c71c..a092ebaa620aa 100644
>> --- a/sound/soc/sdca/sdca_class.c
>> +++ b/sound/soc/sdca/sdca_class.c
> [ ... ]
>> @@ -265,10 +283,37 @@ static int class_runtime_resume(struct device *dev)
> [ ... ]
>> -static const struct dev_pm_ops class_pm_ops = {
>> - SYSTEM_SLEEP_PM_OPS(class_suspend, class_resume)
>> - RUNTIME_PM_OPS(class_runtime_suspend, class_runtime_resume, NULL)
>> +static const struct dev_pm_ops sdca_class_pm_ops = {
>> + SYSTEM_SLEEP_PM_OPS(class_pm_system_suspend, class_pm_system_resume)
>> + RUNTIME_PM_OPS(class_pm_runtime_suspend, class_pm_runtime_resume, NULL)
>> };
>
> [Severity: Medium]
> The commit message states that sdca_class_pm_ops is exported so generic
> SDCA slaves can pick it up as-is, but it is defined statically here without
> an export macro.
>
> Will developers attempting to write a generic SDCA slave in another file
> encounter build or linkage errors when trying to reference sdca_class_pm_ops?
>
> Should this struct be exported to match the commit message description?
>
next prev parent reply other threads:[~2026-09-25 15:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 13:19 [PATCH v4 0/8] ASoC: Qualcomm Tambora (WCD9378) SDCA codec Srinivas Kandagatla
2026-09-18 13:19 ` [PATCH v4 1/8] ASoC: SDCA: allow building without ACPI Srinivas Kandagatla
2026-09-18 13:42 ` sashiko-bot
2026-09-25 15:15 ` Srinivas Kandagatla
2026-09-22 13:32 ` Mark Brown
2026-09-23 8:15 ` Srinivas Kandagatla
2026-09-18 13:19 ` [PATCH v4 2/8] ASoC: SDCA: export PM helpers keyed on sdca_class_drv Srinivas Kandagatla
2026-09-18 13:49 ` sashiko-bot
2026-09-25 15:11 ` Srinivas Kandagatla [this message]
2026-09-18 13:19 ` [PATCH v4 3/8] ASoC: SDCA: expose class SoundWire probe/remove as library Srinivas Kandagatla
2026-09-18 13:19 ` [PATCH v4 4/8] ASoC: SDCA: add class_ops with populate_function Srinivas Kandagatla
2026-09-18 14:08 ` sashiko-bot
2026-09-25 15:09 ` Srinivas Kandagatla
2026-09-18 14:15 ` Charles Keepax
2026-09-18 13:19 ` [PATCH v4 5/8] ASoC: SDCA: class_function: xlate sound-dai cell by entity index Srinivas Kandagatla
2026-09-18 13:19 ` [PATCH v4 6/8] ASoC: SDCA: add sdca_apply_default_control_classifiers() helper Srinivas Kandagatla
2026-09-18 14:16 ` Charles Keepax
2026-09-18 14:20 ` Srinivas Kandagatla
2026-09-18 13:19 ` [PATCH v4 7/8] dt-bindings: sound: qcom: add Tambora WCD9378 SDCA codec Srinivas Kandagatla
2026-09-18 13:51 ` Mark Brown
2026-09-23 8:05 ` Krzysztof Kozlowski
2026-09-18 13:19 ` [PATCH v4 8/8] ASoC: codecs: add Qualcomm Tambora (WCD9378) " Srinivas Kandagatla
2026-09-18 14:28 ` Charles Keepax
2026-09-18 14:37 ` sashiko-bot
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=512dc68e-d1cf-4d69-a8f7-52eee01e1dcc@oss.qualcomm.com \
--to=srinivas.kandagatla@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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