MIME-Version: 1.0
In-Reply-To: <CA+55aFypOcK6fiiUo8FtN1srw8M9FZtqcSsFfA2eVeFu7Nug7w@mail.gmail.com>
References: <1440449403.2469.35.camel@loki>
	<1440489900.2419.4.camel@loki>
	<rbhuamrc6ajy3l1qereb60l8.1440494220682@email.android.com>
	<20150825193408.GR8051@wotan.suse.de>
	<s5h4mjnnobb.wl-tiwai@suse.de>
	<CAKdAkRR+HUM_6SaSwPL0m9_B=Rb3HiXzCS1QGwnYr9HgSCigeA@mail.gmail.com>
	<E7B1D079BA13FB44A978CC8F69C7D6A9055A1C48@SHSMSX101.ccr.corp.intel.com>
	<s5h1teqpqbn.wl-tiwai@suse.de>
	<E7B1D079BA13FB44A978CC8F69C7D6A9055A1CFB@SHSMSX101.ccr.corp.intel.com>
	<1440576394.2443.17.camel@loki>
	<CA+55aFypOcK6fiiUo8FtN1srw8M9FZtqcSsFfA2eVeFu7Nug7w@mail.gmail.com>
Date: Thu, 27 Aug 2015 08:55:13 +0800
Message-ID: <CACVXFVMhhS1UNvK2KZJ4UUWL-H+OGy+Y4iLKSHtjsUry9rFrgw@mail.gmail.com>
Subject: Re: Problems loading firmware using built-in drivers with kernels
 that use initramfs.
From: Ming Lei <ming.lei@canonical.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
        "Jie, Yang" <yang.jie@intel.com>, Takashi Iwai <tiwai@suse.de>,
        Dmitry Torokhov <dmitry.torokhov@gmail.com>,
        "Luis R. Rodriguez" <mcgrof@suse.com>,
        "joonas.lahtinen@linux.intel.com" <joonas.lahtinen@linux.intel.com>,
        Tom Gundersen <teg@jklm.no>, Al Viro <viro@zeniv.linux.org.uk>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Kay Sievers <kay@vrfy.org>, David Woodhouse <dwmw2@infradead.org>,
        Luis Rodriguez <mcgrof@do-not-panic.com>,
        lkml <linux-kernel@vger.kernel.org>,
        yalin wang <yalin.wang2010@gmail.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1564
Lines: 37

On Thu, Aug 27, 2015 at 2:07 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Wed, Aug 26, 2015 at 1:06 AM, Liam Girdwood
> <liam.r.girdwood@linux.intel.com> wrote:
>>
>> I think the options are to either :-
>>
>> 1) Don not support audio DSP drivers using topology data as built-in
>> drivers. Audio is not really a critical system required for booting
>> anyway.
>
> Yes, forcing it to be a module and not letting people compile it in by
> mistake (and then not have it work) is an option.
>
> That said, there are situations where people don't want to use
> modules. I used to eschew them for security reasons, for example - now
> I instead just do a one-time temporary key. But others may have other
> reasons to try to avoid modules.
>
>> 2) Create a default PCM for every driver that has topology data on the
>> assumption that every sound card will at least 1 PCM. This PCM can then
>> be re-configured when the FW is loaded.
>
> That would seem to be the better option if it is reasonably implementable.
>
> Of course, some kind of timer-based retry (limited *somehow*) of the
> fw loading could work too, but smells really really hacky.

Yeah, years ago, we discussed to use -EPROBE_DEFER for the situation,
which should be one kind of fix, but looks there were objections at that time.

thanks,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/