From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 2/2] ASoC: Intel: sst-acpi: Request firmware before SST platform driver probing
Date: Wed, 19 Feb 2014 09:09:57 +0200 [thread overview]
Message-ID: <530458C5.9070603@linux.intel.com> (raw)
In-Reply-To: <530455F1.5000309@linux.intel.com>
On 02/19/2014 08:57 AM, Jarkko Nikula wrote:
> Hi
>
> On 02/18/2014 04:58 PM, Takashi Iwai wrote:
>> At Tue, 18 Feb 2014 16:42:03 +0200,
>> Jarkko Nikula wrote:
>>> -sst_err:
>>> - platform_device_unregister(sst_acpi->pdev_pcm);
>>> - return ret;
>>> + /* continue SST probing after firmware is loaded */
>>> + return request_firmware_nowait(THIS_MODULE, true,
>>> desc->fw_filename,
>>> + dev, GFP_KERNEL, pdev, sst_acpi_fw_cb);
>> sst_acpi->pdev_mach still should be unregistered when
>> request_firmware_nowait() returns an error.
> I was thinking to leave that for sst_acpi_remove but you are right, it
> doesn't make sense to leave it registered for instance if
> request_firmware_nowait fails because of -ENOMEM or some other fatal
> issue.
>
Answering myself after cup of coffee... Obviously probe function must
free whatever it allocated when it returns with an error. In other words
module loading fails and we won't ever call the remove function.
--
Jarkko
next prev parent reply other threads:[~2014-02-19 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 14:42 [PATCH 1/2] ASoC: Intel: Move extended fw base and size fields in struct sst_pdata Jarkko Nikula
2014-02-18 14:42 ` [PATCH 2/2] ASoC: Intel: sst-acpi: Request firmware before SST platform driver probing Jarkko Nikula
2014-02-18 14:58 ` Takashi Iwai
2014-02-19 6:57 ` Jarkko Nikula
2014-02-19 7:09 ` Jarkko Nikula [this message]
2014-02-19 7:15 ` Takashi Iwai
2014-02-19 7:28 ` Jarkko Nikula
2014-02-19 4:41 ` [PATCH 1/2] ASoC: Intel: Move extended fw base and size fields in struct sst_pdata Mark Brown
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=530458C5.9070603@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=tiwai@suse.de \
/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