All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>, alsa-devel@alsa-project.org
Cc: sound-open-firmware@alsa-project.org,
	linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Mark Brown <broonie@kernel.org>,
	Daniel Baluta <daniel.baluta@nxp.com>
Subject: Re: [PATCH 3/7] ASoC: Intel: avs: Move snd_hdac_i915_init to before probe_work.
Date: Wed, 19 Jul 2023 17:54:34 +0200	[thread overview]
Message-ID: <a913df90-174c-7132-bbfa-bf30f0664d9c@linux.intel.com> (raw)
In-Reply-To: <18fb40b9-f5b4-60d8-79df-e0719cf48231@intel.com>

Hey,

On 2023-07-19 17:26, Cezary Rojewski wrote:
> On 2023-07-18 10:45 AM, Maarten Lankhorst wrote:
>> Now that we can use -EPROBE_DEFER, it's no longer required to spin off
>> the snd_hdac_i915_init into a workqueue. It's likely the whole workqueue
>> can be destroyed, but I don't have the means to test this.
>>
>> Removing the workqueue would simplify init even further, but is left
>> as exercise for the reviewer.
>>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> ---
>>   sound/soc/intel/avs/core.c | 13 +++++++++----
>>   1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> diff --git a/sound/soc/intel/avs/core.c b/sound/soc/intel/avs/core.c
>> index 3311a6f142001..d3a7f42387e9b 100644
>> --- a/sound/soc/intel/avs/core.c
>> +++ b/sound/soc/intel/avs/core.c
>> @@ -191,10 +191,6 @@ static void avs_hda_probe_work(struct work_struct 
>> *work)
>>       pm_runtime_set_active(bus->dev); /* clear runtime_error flag */
>> -    ret = snd_hdac_i915_init(bus, true);
>> -    if (ret < 0)
>> -        dev_info(bus->dev, "i915 init unsuccessful: %d\n", ret);
>> -
>>       snd_hdac_display_power(bus, HDA_CODEC_IDX_CONTROLLER, true);
>>       avs_hdac_bus_init_chip(bus, true);
>>       avs_hdac_bus_probe_codecs(bus);
>> @@ -465,10 +461,19 @@ static int avs_pci_probe(struct pci_dev *pci, 
>> const struct pci_device_id *id)
>>       pci_set_drvdata(pci, bus);
>>       device_disable_async_suspend(dev);
>> +    ret = snd_hdac_i915_init(bus, false);
>> +    if (ret == -EPROBE_DEFER)
>> +        goto err_unmaster;
>> +    else if (ret < 0)
>> +        dev_info(bus->dev, "i915 init unsuccessful: %d\n", ret);
>> +
> 
> While our tests are currently passing I have my doubts about 
> EPROBE_DEFER. We do want to have audio functionality there even if some 
> problems with HDMI arise along the way - some audio is better than no 
> audio. Here, i915 may ruin the day for a platform equipped with 
> hda/hdmi/i2c/dmic chips simultaneously.
> 
> Also, why call snd_hdac_i915_init() _after_ setting drvdata?

I wanted to make the most cautious change. The previous flow called the 
function immediately from probe_work, so I moved it to right before the 
scheduling of probe_work

>>       schedule_work(&adev->probe_work);
>>       return 0;
>> +err_unmaster:
>> +    pci_clear_master(pci);
>> +    pci_set_drvdata(pci, NULL);
> 
> Not a fan. It's hard to grasp entire error-step within name of a single 
> label. Thus I'd suggest "err_<cause>" naming pattern instead. Even here, 
> under "unmaster" you hid clearing master and drvdata both. Let's do 
> "err_i915_init" instead.
> 
Ok, will rename.

~Maarten

  parent reply	other threads:[~2023-07-21  8:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18  8:45 [PATCH 0/7] sound: Use -EPROBE_DEFER instead of i915 module loading Maarten Lankhorst
2023-07-18  8:45 ` [PATCH 1/7] ALSA: hda/i915: Add an allow_modprobe argument to snd_hdac_i915_init Maarten Lankhorst
2023-07-18  8:45 ` [PATCH 2/7] ALSA: hda/i915: Allow xe as match for i915_component_master_match Maarten Lankhorst
2023-07-18  8:45 ` [PATCH 3/7] ASoC: Intel: avs: Move snd_hdac_i915_init to before probe_work Maarten Lankhorst
2023-07-18 14:11   ` Mark Brown
2023-07-19 15:26   ` Cezary Rojewski
2023-07-19 15:31     ` Takashi Iwai
2023-07-19 15:54     ` Maarten Lankhorst [this message]
2023-07-18  8:45 ` [PATCH 4/7] ASoC: Intel: Skylake: " Maarten Lankhorst
2023-07-18 14:12   ` Mark Brown
2023-07-18  8:45 ` [PATCH 5/7] ALSA: hda/intel: " Maarten Lankhorst
2023-07-18  9:57   ` Takashi Iwai
2023-07-18 11:57     ` [v2 PATCH 1/2] ALSA: hda/intel: Fix error handling in azx_probe() Maarten Lankhorst
2023-07-18 12:17       ` Takashi Iwai
2023-07-18 11:58     ` [v2 PATCH 2/2] ALSA: hda/intel: Move snd_hdac_i915_init to before probe_work Maarten Lankhorst
2023-07-18  8:45 ` [PATCH 6/7] ASoC: SOF: Intel: Remove deferred probe for SOF Maarten Lankhorst
2023-07-18 14:13   ` Mark Brown
2023-07-18 17:04   ` Kai Vehmanen
2023-07-19  6:01     ` Takashi Iwai
2023-07-19  9:48       ` Maarten Lankhorst
2023-07-19 11:06         ` Takashi Iwai
2023-07-19 12:13           ` [PATCH] " Maarten Lankhorst
2023-07-19 12:39             ` Mark Brown
2023-07-19 15:59               ` Maarten Lankhorst
2023-07-19 12:47             ` Takashi Iwai
2023-07-19 13:32         ` [PATCH 6/7] " Kai Vehmanen
2023-07-19 13:32           ` Kai Vehmanen
2023-07-18  8:45 ` [PATCH 7/7] ALSA: hda/i915: Remove extra argument from snd_hdac_i915_init Maarten Lankhorst
2023-07-18  9:50 ` [PATCH 0/7] sound: Use -EPROBE_DEFER instead of i915 module loading Takashi Iwai

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=a913df90-174c-7132-bbfa-bf30f0664d9c@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=daniel.baluta@nxp.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=tiwai@suse.com \
    --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.