From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, vinod.koul@intel.com, alsa-devel@alsa-project.org,
broonie@kernel.org, andriy.shevchenko@linux.intel.com
Subject: Re: [PATCH 0/8] ASoC: Prepare Sound Open Firmware (SOF) driver integration
Date: Thu, 19 Oct 2017 22:18:49 +0100 [thread overview]
Message-ID: <1508447929.2004.13.camel@loki> (raw)
In-Reply-To: <20171012234945.30318-1-pierre-louis.bossart@linux.intel.com>
On Thu, 2017-10-12 at 18:49 -0500, Pierre-Louis Bossart wrote:
> The Sound Open Firmware work [1] is progressing quickly and drivers
> for the 1.0 release will soon be submitted upstream. Before we do so,
> there is a new to reshuffle the ACPI integration and Intel
> Kconfig/Makefiles.
>
> We already have three incompatible drivers (BYT/HSW/BDW, Atom/BYT/CHT,
> SKL+) for historical reasons, blindly adding yet another one would be
> silly. We need to avoid having the same ACPI routines and machine
> tables duplicated in 3 locations (soc/intel/common, soc/atom/sst and
> the upcoming soc/sof).
>
> The ACPI routines should be part of sound/soc since there is no real
> hardware dependency (ACPI is not limited to Intel).
>
> The ACPI table definitions and quirks are moved to a soc/intel/common module
> so that when new HIDs or quirks are added "legacy" and the SOF drivers
> are updated at once.
>
> The Makefiles/Kconfig are also modified to select the SOC(s) first and
> the machine driver(s) second. The existing code only exposes machine
> drivers which precludes reuse of machine drivers when SOF platform
> drivers are selected. SOF drivers will be exposed in parallel to the
> 'Intel SST' ones (with an exclusive choice needed), but machine
> drivers will be shared.
>
> These patches apply on top of broonie/for-next + all the patches I
> submitted this week (no dependency on SOF). For people with allergic
> reactions to patches over email, the code is here:
> https://github.com/plbossart/sound/commits/topic/acpi-updates6
>
> This patchset does not address the case where two drivers are selected
> for the same ACPI HID. I just don't know of any technical solution to
> that problem.
>
> changes since initial RFC:
> rebased to v4.14-rc2, used kernel style doc for machine descriptors,
> removed useless fields, split tables for each SOC
> corrected missing newlines
>
> Pierre-Louis Bossart (8):
> ASoC: move ACPI common code out of Intel/sst tree
> ASoC: Intel: common: use c99 syntax for ACPI/machine tables
> ASoC: ACPI: add new fields for SOF support
> ASoC: Intel: move all ACPI match tables to common module
> ASoC: Intel: add SOF firmare/topology file information
> ASoC: Intel: move machine drivers to dedicated KConfig
> ASoC: Intel: reorder boards Kconfig by chronological order
> ASoC: Intel: clarify Kconfig dependencies
All
Acked-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
prev parent reply other threads:[~2017-10-19 21:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 23:49 [PATCH 0/8] ASoC: Prepare Sound Open Firmware (SOF) driver integration Pierre-Louis Bossart
2017-10-12 23:49 ` [PATCH 1/8] ASoC: move ACPI common code out of Intel/sst tree Pierre-Louis Bossart
2017-10-12 23:49 ` [PATCH 2/8] ASoC: Intel: common: use c99 syntax for ACPI/machine tables Pierre-Louis Bossart
2017-10-12 23:49 ` [PATCH 3/8] ASoC: ACPI: add new fields for SOF support Pierre-Louis Bossart
2017-10-13 16:35 ` Andy Shevchenko
2017-10-13 17:17 ` Pierre-Louis Bossart
2017-10-21 10:30 ` Applied "ASoC: ACPI: add new fields for SOF support" to the asoc tree Mark Brown
2017-10-12 23:49 ` [PATCH 4/8] ASoC: Intel: move all ACPI match tables to common module Pierre-Louis Bossart
2017-10-13 16:38 ` Andy Shevchenko
2017-10-13 17:21 ` Pierre-Louis Bossart
2017-10-21 10:29 ` Applied "ASoC: Intel: move all ACPI match tables to common module" to the asoc tree Mark Brown
2017-10-12 23:49 ` [PATCH 5/8] ASoC: Intel: add SOF firmare/topology file information Pierre-Louis Bossart
2017-10-21 10:29 ` Applied "ASoC: Intel: add SOF firmare/topology file information" to the asoc tree Mark Brown
2017-10-12 23:49 ` [PATCH 6/8] ASoC: Intel: move machine drivers to dedicated KConfig Pierre-Louis Bossart
2017-10-12 23:49 ` [PATCH 7/8] ASoC: Intel: reorder boards Kconfig by chronological order Pierre-Louis Bossart
2017-10-12 23:49 ` [PATCH 8/8] ASoC: Intel: clarify Kconfig dependencies Pierre-Louis Bossart
2017-10-19 21:18 ` Liam Girdwood [this message]
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=1508447929.2004.13.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).