From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752898AbbHZSHV (ORCPT ); Wed, 26 Aug 2015 14:07:21 -0400 Received: from mail-ig0-f179.google.com ([209.85.213.179]:38786 "EHLO mail-ig0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751727AbbHZSHS (ORCPT ); Wed, 26 Aug 2015 14:07:18 -0400 MIME-Version: 1.0 In-Reply-To: <1440576394.2443.17.camel@loki> References: <1440449403.2469.35.camel@loki> <1440489900.2419.4.camel@loki> <20150825193408.GR8051@wotan.suse.de> <1440576394.2443.17.camel@loki> Date: Wed, 26 Aug 2015 11:07:18 -0700 X-Google-Sender-Auth: UrFCLTqVj7V9LuAZ1JGMsT2dE3E Message-ID: Subject: Re: Problems loading firmware using built-in drivers with kernels that use initramfs. From: Linus Torvalds To: Liam Girdwood Cc: "Jie, Yang" , Takashi Iwai , Dmitry Torokhov , "Luis R. Rodriguez" , "joonas.lahtinen@linux.intel.com" , Tom Gundersen , Ming Lei , Al Viro , Greg Kroah-Hartman , Kay Sievers , David Woodhouse , Luis Rodriguez , lkml , yalin wang Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 26, 2015 at 1:06 AM, Liam Girdwood 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. Linus