From: Cezary Rojewski <cezary.rojewski@intel.com>
To: "Liao, Bard" <bard.liao@intel.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"tiwai@suse.com" <tiwai@suse.com>,
"perex@perex.cz" <perex@perex.cz>,
"amade@asmblr.net" <amade@asmblr.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yung-chuan.liao@linux.intel.com"
<yung-chuan.liao@linux.intel.com>,
"pierre-louis.bossart@linux.dev" <pierre-louis.bossart@linux.dev>,
"vkoul@kernel.org" <vkoul@kernel.org>
Subject: Re: [PATCH 3/7] soundwire: intel: Split PDIs and DAIs initialization
Date: Tue, 3 Nov 2026 09:59:02 +0100 [thread overview]
Message-ID: <61aceb15-de8c-4a15-9cc6-79dd02418244@intel.com> (raw)
In-Reply-To: <SJ2PR11MB8424F37260E9A70E14744CC7FF692@SJ2PR11MB8424.namprd11.prod.outlook.com>
On 11/3/2026 3:35 AM, Liao, Bard wrote:
>> +int sdw_intel_init_pdis(struct sdw_intel *sdw);
>>
>> /* common bank switch routines */
>> int intel_pre_bank_switch(struct sdw_intel *sdw);
>> diff --git a/drivers/soundwire/intel_auxdevice.c
>> b/drivers/soundwire/intel_auxdevice.c
>> index 5983fbc5725a..114dadedfa14 100644
>> --- a/drivers/soundwire/intel_auxdevice.c
>> +++ b/drivers/soundwire/intel_auxdevice.c
>> @@ -423,6 +423,10 @@ int intel_link_startup(struct auxiliary_device *auxdev)
>> if (ret)
>> goto err_init;
>>
>> + ret = sdw_intel_init_pdis(sdw);
>
> intel_link_startup will be called by all Intel platforms, but the PDI
> initialization are different for the ACE2+ platforms. Please call
> sdw_intel_init_pdi in one of the sdw_intel_hw_ops ops.
Indeed. I'll add a new ops, init_pdis(), and update the ACE2+ related
code. When I've created these, around 2021, the ACE2+ wasn't there and
right now, avs-driver does not utilize SDW with ACE2+ either so nothing
shown in the tests.
Thank you, Bard!
>> + if (ret)
>> + goto err_init;
>
> This is after sdw_intel_link_power_up(), please goto err_power_up
Ack.
next prev parent reply other threads:[~2026-11-03 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 18:10 [PATCH 0/7] ASoC: Intel: avs: Soundwire support Cezary Rojewski
2026-11-02 18:10 ` [PATCH 1/7] soundwire: intel: Define stubs when library is disabled Cezary Rojewski
2026-11-02 18:10 ` [PATCH 2/7] soundwire: intel: Allow for dynamic assignment of PDIs Cezary Rojewski
2026-11-03 9:04 ` kernel test robot
2026-11-02 18:10 ` [PATCH 3/7] soundwire: intel: Split PDIs and DAIs initialization Cezary Rojewski
2026-11-03 2:35 ` Liao, Bard
2026-11-03 8:59 ` Cezary Rojewski [this message]
2026-11-02 18:10 ` [PATCH 4/7] ASoC: Intel: avs: Pass irq to dsp_interrupt callback Cezary Rojewski
2026-11-02 18:10 ` [PATCH 5/7] ASoC: Intel: avs: SoundWire support Cezary Rojewski
2026-11-02 18:10 ` [PATCH 6/7] ASoC: Intel: avs: Expose common PCM functions Cezary Rojewski
2026-11-02 18:18 ` Amadeusz Sławiński
2026-11-02 18:20 ` Cezary Rojewski
2026-11-02 18:10 ` [PATCH 7/7] ASoC: Intel: avs: SoundWire PCM BE operations Cezary Rojewski
2026-11-03 5:37 ` [PATCH 0/7] ASoC: Intel: avs: Soundwire support Vinod Koul
2026-11-03 9:18 ` 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=61aceb15-de8c-4a15-9cc6-79dd02418244@intel.com \
--to=cezary.rojewski@intel.com \
--cc=amade@asmblr.net \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.dev \
--cc=tiwai@suse.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 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®