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 1/4] ASoC: SDCA: Add SDCA IRQ enable/disable helpers
Date: Tue, 6 Jan 2026 18:17:10 +0100 [thread overview]
Message-ID: <b09dc2bc-43dd-48c5-b0f8-ed75bbf50a1b@linux.dev> (raw)
In-Reply-To: <20251218113520.1287693-2-ckeepax@opensource.cirrus.com>
only a couple of nit-picks below:
> +/**
> + * sdca_irq_enable_early - Re-enable early SDCA IRQs for a given function
> + * @function: Pointer to the SDCA Function.
> + * @info: Pointer to the SDCA interrupt info for this device.
> + */
> +void sdca_irq_enable_early(struct sdca_function_data *function,
> + struct sdca_interrupt_info *info)
> +{
> + irq_enable_flags(function, info, true);
> +}
> +EXPORT_SYMBOL_NS_GPL(sdca_irq_enable_early, "SND_SOC_SDCA");
> +
> +/**
> + * sdca_irq_enable_early - Re-enable SDCA IRQs for a given function
copy-paste from above making this kernel-doc description incorrect.
> + * @function: Pointer to the SDCA Function.
> + * @info: Pointer to the SDCA interrupt info for this device.
> + */
> +void sdca_irq_enable(struct sdca_function_data *function,
> + struct sdca_interrupt_info *info)
> +{
> + irq_enable_flags(function, info, false);
> +}
> +EXPORT_SYMBOL_NS_GPL(sdca_irq_enable, "SND_SOC_SDCA");
> +
> +/**
> + * sdca_irq_disable - Disable SDCA IRQs for a given function
> + * @function: Pointer to the SDCA Function.
> + * @info: Pointer to the SDCA interrupt info for this device.
> + */
> +void sdca_irq_disable(struct sdca_function_data *function,
> + struct sdca_interrupt_info *info)
maybe explain why we have an _early version for enable but not a _late for disable?
> +{
> + struct sdca_interrupt *interrupt;
> + int i;
> +
> + for (i = 0; i < SDCA_MAX_INTERRUPTS; i++) {
> + interrupt = &info->irqs[i];
> +
> + if (!interrupt || interrupt->function != function)
> + continue;
> +
> + disable_irq(interrupt->irq);
> + }
> +}
> +EXPORT_SYMBOL_NS_GPL(sdca_irq_disable, "SND_SOC_SDCA");
next prev parent 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 [this message]
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
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=b09dc2bc-43dd-48c5-b0f8-ed75bbf50a1b@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.