From: sashiko-bot@kernel.org
To: "Cezary Rojewski" <cezary.rojewski@intel.com>,
linux-sound@vger.kernel.org
Subject: Re: [PATCH v2 2/7] soundwire: intel: Allow for dynamic assignment of PDIs
Date: Tue, 03 Nov 2026 14:00:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-195411@kernel.org> (raw)
In-Reply-To: <20261103134958.2089136-3-cezary.rojewski@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] soundwire: intel: sdw_intel_pdi_config() adds separate layer over DAI ops
--
commit e83fbc567de1bac187beea3bd11c5b0304d25e97
Author: Cezary Rojewski <cezary.rojewski@intel.com>
soundwire: intel: Allow for dynamic assignment of PDIs
This commit introduces sdw_cdns_assign_pdi() and sdw_cdns_release_pdi() for
dynamic PDI assignment, along with sdw_intel_pdi_config() to configure PDIs
separately from assignment.
> diff --git a/drivers/soundwire/intel.c b/drivers/soundwire/intel.c
> index af65214836b4d..d53fa3d299bc7 100644
> --- a/drivers/soundwire/intel.c
> +++ b/drivers/soundwire/intel.c
> @@ -674,6 +674,22 @@ intel_pdi_alh_configure(struct sdw_intel *sdw, struct sdw_cdns_pdi *pdi)
> intel_writel(alh, SDW_ALH_STRMZCFG(pdi->intel_alh_id), conf);
> }
>
> +/**
> + * sdw_intel_pdi_config - Configure specified PDI
> + * @bus: SoundWire bus instance
> + * @pdi: PDI instance to configure
> + */
> +void sdw_intel_pdi_config(struct sdw_bus *bus, struct sdw_cdns_pdi *pdi)
> +{
> + struct sdw_cdns *cdns = bus_to_cdns(bus);
> + struct sdw_intel *sdw = cdns_to_intel(cdns);
> +
> + intel_pdi_shim_configure(sdw, pdi);
> + intel_pdi_alh_configure(sdw, pdi);
> + sdw_cdns_config_stream(cdns, pdi->ch_count, pdi->dir, pdi);
> +}
> +EXPORT_SYMBOL(sdw_intel_pdi_config);
[Severity: Medium]
As reported by Vinod Koul on v1 [1], exporting sdw_intel_pdi_config() adds a
separate layer in drivers/soundwire/intel.c for external driver-specific DAI
handling while leaving the existing DAI operations in intel_hw_params()
unchanged:
drivers/soundwire/intel.c:intel_hw_params() {
...
pdi = sdw_cdns_alloc_pdi(cdns, &cdns->pcm, ch, dir, dai->id);
if (!pdi)
return -EINVAL;
/* do run-time configurations for SHIM, ALH and PDI/PORT */
intel_pdi_shim_configure(sdw, pdi);
intel_pdi_alh_configure(sdw, pdi);
sdw_cdns_config_stream(cdns, ch, dir, pdi);
...
}
Instead of exporting sdw_intel_pdi_config() for external callers while
intel_hw_params() continues to allocate PDIs statically by DAI ID and call
intel_pdi_shim_configure(), intel_pdi_alh_configure(), and
sdw_cdns_config_stream() directly, could the SoundWire Intel driver itself be
updated to handle both startup and hw_params uniformly across SOF and AVS
drivers?
[1] https://lore.kernel.org/r/aulzN9MCl5CJB1Al@parshuram
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103134958.2089136-1-cezary.rojewski@intel.com?part=2
next prev parent reply other threads:[~2026-11-03 14:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 13:49 [PATCH v2 0/7] ASoC: Intel: avs: Soundwire support Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 1/7] soundwire: intel: Define stubs when library is disabled Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 2/7] soundwire: intel: Allow for dynamic assignment of PDIs Cezary Rojewski
2026-11-03 14:00 ` sashiko-bot [this message]
2026-11-03 13:49 ` [PATCH v2 3/7] soundwire: intel: Split PDIs and DAIs initialization Cezary Rojewski
2026-11-03 13:58 ` sashiko-bot
2026-11-03 13:49 ` [PATCH v2 4/7] ASoC: Intel: avs: Pass irq to dsp_interrupt callback Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 5/7] ASoC: Intel: avs: SoundWire support Cezary Rojewski
2026-11-03 14:13 ` sashiko-bot
2026-11-03 13:49 ` [PATCH v2 6/7] ASoC: Intel: avs: Expose common PCM functions Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 7/7] ASoC: Intel: avs: SoundWire PCM BE operations Cezary Rojewski
2026-11-03 14:07 ` sashiko-bot
2026-11-03 17:20 ` [PATCH v2 0/7] ASoC: Intel: avs: Soundwire support Pierre-Louis Bossart
2026-11-04 9:14 ` Cezary Rojewski
2026-11-04 11:52 ` Pierre-Louis Bossart
2026-11-04 13:33 ` Vinod Koul
2026-11-04 14:31 ` Cezary Rojewski
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=sashiko-outbox-195411@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=linux-sound@vger.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