All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>, broonie@kernel.org
Cc: lgirdwood@gmail.com, vkoul@kernel.org,
	yung-chuan.liao@linux.intel.com, peter.ujfalusi@linux.intel.com,
	shumingf@realtek.com, linux-sound@vger.kernel.org,
	patches@opensource.cirrus.com
Subject: Re: [PATCH v2 2/4] ASoC: SDCA: Add basic system suspend support
Date: Tue, 6 Jan 2026 18:23:17 +0100	[thread overview]
Message-ID: <720ffab9-1c09-433a-b3a0-40ed496119fb@linux.dev> (raw)
In-Reply-To: <20251218113520.1287693-3-ckeepax@opensource.cirrus.com>


> +static int class_suspend(struct device *dev)
> +{
> +	struct sdca_class_drv *drv = dev_get_drvdata(dev);
> +	int ret;
> +
> +	disable_irq(drv->sdw->irq);
> +
> +	ret = pm_runtime_force_suspend(dev);
> +	if (ret) {
> +		dev_err(dev, "Failed to force suspend: %d\n", ret);

suggestion: since this is going to be fairly generic code used by multiple devices, it'd be useful to add a device identifier or string to the error log, no?

This can be done later in a follow-up patch if agreed.


> +	if (drv->suspended) {
> +		sdca_irq_enable_early(drv->function, drv->core->irq_info);
> +		sdca_irq_enable(drv->function, drv->core->irq_info);

maybe add a comment on why the two calls are done sequentially. You did mention it somewhere, it'd be good to capture the design.

looks good otherwise.

  reply	other threads:[~2026-01-06 17:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18 11:35 [PATCH v2 0/4] SDCA System Suspend Support Charles Keepax
2025-12-18 11:35 ` [PATCH v2 1/4] ASoC: SDCA: Add SDCA IRQ enable/disable helpers Charles Keepax
2026-01-06 17:17   ` Pierre-Louis Bossart
2026-01-07 10:02     ` Charles Keepax
2025-12-18 11:35 ` [PATCH v2 2/4] ASoC: SDCA: Add basic system suspend support Charles Keepax
2026-01-06 17:23   ` Pierre-Louis Bossart [this message]
2026-01-07 10:04     ` Charles Keepax
2026-01-08 10:18       ` Pierre-Louis Bossart
2026-01-08 10:40         ` Charles Keepax
2026-01-08 15:15           ` Pierre-Louis Bossart
2025-12-18 11:35 ` [PATCH v2 3/4] ASoC: SDCA: Device boot into the system suspend process Charles Keepax
2025-12-18 11:35 ` [PATCH v2 4/4] ASoC: SDCA: Add lock to serialise the Function initialisation Charles Keepax

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=720ffab9-1c09-433a-b3a0-40ed496119fb@linux.dev \
    --to=pierre-louis.bossart@linux.dev \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=shumingf@realtek.com \
    --cc=vkoul@kernel.org \
    --cc=yung-chuan.liao@linux.intel.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.