From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>, Daniel Baluta <daniel.baluta@gmail.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>, "S.j. Wang" <shengjiu.wang@nxp.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Curtis Malainey <cujomalainey@google.com>,
Guido Roncarolo <guido.roncarolo@nxp.com>
Subject: Re: [alsa-devel] [ANNOUNCE] 2019 Linux Audio miniconference
Date: Thu, 10 Oct 2019 11:43:42 -0500 [thread overview]
Message-ID: <47378afc-f7ef-d6fa-7b0d-efc3fbe494e0@linux.intel.com> (raw)
In-Reply-To: <20191010155716.GE4741@sirena.org.uk>
On 10/10/19 10:57 AM, Mark Brown wrote:
> On Wed, Oct 09, 2019 at 09:48:14PM +0300, Daniel Baluta wrote:
>> On Wed, Oct 9, 2019 at 9:15 PM Mark Brown <broonie@kernel.org> wrote:
>
>> My topics:
>
> I'll add these to the agenda.
>
>> - SOF driver: ACPI / DT unification
>
> Are there concrete plans to discuss here or is this more of a
> "what are we doing" kind of thing? ACPI standardization has been
> an issue :/
I took this agenda item as "how machine drivers are handled in SOF".
Currently the core creates a platform device which will result in a
machine driver being probe and the card created. This is mainly due to
the lack of 'machine device' in existing DSDT tables. DT has explicit
support for machine drivers, so we need to have a solution that caters
to both.
>
>> - SOF driver: Handling built-in driver use case
>
> What's the issue here?
The SOF driver (or any existing driver with closed-source firmware) will
not work when compiled as built-in due to the request_firmware()
dependency. This wasn't too much of an issue for Intel so far, but for
i.MX platforms it's quite common to have no modules.
Daniel, did I get things right?
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-10 19:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 18:13 [alsa-devel] [ANNOUNCE] 2019 Linux Audio miniconference Mark Brown
2019-10-09 18:48 ` Daniel Baluta
2019-10-10 15:57 ` Mark Brown
2019-10-10 16:43 ` Pierre-Louis Bossart [this message]
2019-10-10 19:43 ` Daniel Baluta
2019-10-09 19:16 ` Pierre-Louis Bossart
2019-10-25 10:05 ` Vinod Koul
2019-10-14 19:47 ` Liam Girdwood
2019-10-14 20:16 ` Curtis Malainey
2019-10-15 20:11 ` Mark Brown
2019-10-15 20:11 ` Mark Brown
2019-10-22 18:59 ` Mark Brown
2019-10-23 9:20 ` Jerome Brunet
2019-10-23 16:53 ` Mark Brown
2019-10-24 14:20 ` Patrick Lai
2019-10-24 14:31 ` Pierre-Louis Bossart
2019-10-25 9:45 ` Vinod Koul
2019-10-25 14:27 ` Pierre-Louis Bossart
2019-10-25 17:26 ` Patrick Lai
2019-10-24 19:15 ` 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=47378afc-f7ef-d6fa-7b0d-efc3fbe494e0@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cujomalainey@google.com \
--cc=daniel.baluta@gmail.com \
--cc=guido.roncarolo@nxp.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=shengjiu.wang@nxp.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