From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>, vkoul@kernel.org
Cc: amadeuszx.slawinski@linux.intel.com, Mario.Limonciello@amd.com,
Sunil-kumar.Dommati@amd.com, Basavaraj.Hiregoudar@amd.com,
Mastan.Katragadda@amd.com, Arungopal.kondaveeti@amd.com,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Sanyog Kale <sanyog.r.kale@intel.com>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:SOUNDWIRE SUBSYSTEM"
<alsa-devel@alsa-project.org>
Subject: Re: [PATCH V2 2/8] soundwire: amd: Add support for AMD Manager driver
Date: Tue, 14 Feb 2023 07:21:33 -0600 [thread overview]
Message-ID: <e79dae39-faec-b2a4-82e6-e11325904f3e@linux.intel.com> (raw)
In-Reply-To: <7b5198f5-1894-5ab5-f84b-410cf102268d@amd.com>
>>> +static void amd_sdw_probe_work(struct work_struct *work)
>>> +{
>>> + struct amd_sdw_manager *amd_manager = container_of(work, struct amd_sdw_manager,
>>> + probe_work);
>>> + struct sdw_master_prop *prop;
>>> + int ret;
>>> +
>>> + prop = &amd_manager->bus.prop;
>>> + if (!prop->hw_disabled) {
>>> + amd_enable_sdw_pads(amd_manager);
>>> + ret = amd_init_sdw_manager(amd_manager);
>>> + if (ret)
>>> + return;
>>> + amd_enable_sdw_interrupts(amd_manager);
>>> + ret = amd_enable_sdw_manager(amd_manager);
>>> + if (ret)
>>> + return;
>>> + amd_sdw_set_frameshape(amd_manager);
>>> + }
>>> +}
>> There should be an explanation as to why you need a workqueue to
>> complete the probe.
> We want to separate the manager probe sequence and start up sequence.
> we will add the comment.
Do you need to split in two? For Intel, on some platforms we had a clear
power dependency, we had to wait until parts of the DSP were powered
before accessing SHIM registers, so we called the startup() when those
dependencies were resolved.
I am not sure you can count on the probe_work to enforce any kind of
delay, worst case the work function could be scheduled immediately.
next prev parent reply other threads:[~2023-02-14 19:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230213094031.2231058-1-Vijendar.Mukunda@amd.com>
2023-02-13 9:40 ` [PATCH V2 1/8] soundwire: export sdw_compute_slave_ports() function Vijendar Mukunda
2023-02-13 9:40 ` Vijendar Mukunda
2023-02-13 9:40 ` [PATCH V2 2/8] soundwire: amd: Add support for AMD Manager driver Vijendar Mukunda
2023-02-13 9:40 ` Vijendar Mukunda
2023-02-13 18:05 ` Pierre-Louis Bossart
2023-02-14 5:28 ` Mukunda,Vijendar
2023-02-14 13:21 ` Pierre-Louis Bossart [this message]
2023-02-14 22:29 ` Mukunda,Vijendar
2023-02-13 9:40 ` [PATCH V2 3/8] soundwire: amd: register soundwire manager dai ops Vijendar Mukunda
2023-02-13 9:40 ` Vijendar Mukunda
2023-02-13 18:09 ` Pierre-Louis Bossart
2023-02-14 5:49 ` Mukunda,Vijendar
2023-02-13 9:40 ` [PATCH V2 4/8] soundwire: amd: enable build for AMD soundwire manager driver Vijendar Mukunda
2023-02-13 9:40 ` Vijendar Mukunda
2023-02-13 9:40 ` [PATCH V2 5/8] soundwire: amd: add soundwire manager interrupt handling Vijendar Mukunda
2023-02-13 9:40 ` Vijendar Mukunda
2023-02-13 18:15 ` Pierre-Louis Bossart
2023-02-14 5:56 ` Mukunda,Vijendar
2023-02-14 7:54 ` Mukunda,Vijendar
2023-02-14 13:28 ` Pierre-Louis Bossart
2023-02-14 22:18 ` Mukunda,Vijendar
2023-02-13 9:40 ` [PATCH V2 6/8] soundwire: amd: add runtime pm ops for AMD soundwire manager driver Vijendar Mukunda
2023-02-13 9:40 ` Vijendar Mukunda
2023-02-13 18:20 ` Pierre-Louis Bossart
2023-02-14 6:13 ` Mukunda,Vijendar
2023-02-14 13:33 ` Pierre-Louis Bossart
2023-02-14 21:44 ` Mukunda,Vijendar
2023-02-13 9:40 ` [PATCH V2 7/8] soundwire: amd: handle soundwire wake enable interrupt Vijendar Mukunda
2023-02-13 9:40 ` Vijendar Mukunda
2023-02-13 18:24 ` Pierre-Louis Bossart
2023-02-14 6:15 ` Mukunda,Vijendar
2023-02-14 13:35 ` Pierre-Louis Bossart
2023-02-14 21:24 ` Mukunda,Vijendar
2023-02-13 9:40 ` [PATCH V2 8/8] soundwire: amd: add pm_prepare callback and pm ops support Vijendar Mukunda
2023-02-13 9:40 ` Vijendar Mukunda
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=e79dae39-faec-b2a4-82e6-e11325904f3e@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=Arungopal.kondaveeti@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Mastan.Katragadda@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sanyog.r.kale@intel.com \
--cc=vijendar.mukunda@amd.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.