From: Vinod Koul <vinod.koul@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, liam.r.girdwood@linux.intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [RFC PATCH 3/8] ASoC: ACPI: add new fields for SOF support
Date: Tue, 26 Sep 2017 09:48:08 +0530 [thread overview]
Message-ID: <20170926041808.GK30097@localhost> (raw)
In-Reply-To: <20170908205702.1985-4-pierre-louis.bossart@linux.intel.com>
On Fri, Sep 08, 2017 at 03:56:57PM -0500, Pierre-Louis Bossart wrote:
> To prepare for SOF integration, we need new fields in the machine table.
> It is intended that the same table is used for both closed-source and
> open-source firmware to avoid repeating ACPI-related information
> multiple times
> No functional change
>
> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> ---
> include/sound/soc-acpi.h | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/include/sound/soc-acpi.h b/include/sound/soc-acpi.h
> index 75fb32e..3e61f93 100644
> --- a/include/sound/soc-acpi.h
> +++ b/include/sound/soc-acpi.h
> @@ -60,12 +60,29 @@ struct snd_soc_acpi_mach {
> const char *drv_name;
> /* firmware file name */
> const char *fw_filename;
> -
> /* board name */
> const char *board;
> struct snd_soc_acpi_mach * (*machine_quirk)(void *arg);
> const void *quirk_data;
> +
> + /* intended for platform data or machine specific-ops */
> void *pdata;
> +
> + /* SOF firmware file name */
> + const char *sof_fw_filename;
> + /* SOF default topology */
> + const char *sof_tplg_filename;
> +
> + /* ASoC platform name - used for binding machine drivers if non NULL */
> + const char *asoc_plat_name;
> +
> + /* machine driver private data fixup */
> + struct platform_device * (*new_mach_data)(void *pdata);
good comments, can we move them to kernel-doc style please
> +
> + /* FIXME: is this needed, was only used for BYTCR-detection
> + int (*confirm_mach)(struct device *dev,
> + const struct sof_dev_desc **desc);
> + */
this is dummy, lets remove it and add when required
--
~Vinod
next prev parent reply other threads:[~2017-09-26 4:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 20:56 [RFC PATCH 0/8] Prepare Sound Open Firmware (SOF) driver integration Pierre-Louis Bossart
2017-09-08 20:56 ` [RFC PATCH 1/8] ASoC: move ACPI common code out of Intel/sst tree Pierre-Louis Bossart
2017-09-08 20:56 ` [RFC PATCH 2/8] ASoC: Intel: common: use c99 syntax for ACPI/machine tables Pierre-Louis Bossart
2017-10-21 10:30 ` Applied "ASoC: Intel: common: use c99 syntax for ACPI/machine tables" to the asoc tree Mark Brown
2017-09-08 20:56 ` [RFC PATCH 3/8] ASoC: ACPI: add new fields for SOF support Pierre-Louis Bossart
2017-09-26 4:18 ` Vinod Koul [this message]
2017-09-26 19:14 ` Pierre-Louis Bossart
2017-09-08 20:56 ` [RFC PATCH 4/8] ASoC: Intel: move all ACPI match tables to common module Pierre-Louis Bossart
2017-09-26 4:23 ` Vinod Koul
2017-09-26 19:13 ` Pierre-Louis Bossart
2017-09-27 9:45 ` Vinod Koul
2017-09-27 17:06 ` Pierre-Louis Bossart
2017-09-27 17:31 ` Vinod Koul
2017-09-27 17:39 ` Pierre-Louis Bossart
2017-09-08 20:56 ` [RFC PATCH 5/8] ASoC: Intel: add SOF firmare/topology file information Pierre-Louis Bossart
2017-09-08 20:57 ` [RFC PATCH 6/8] ASoC: Intel: move machine drivers to dedicated KConfig Pierre-Louis Bossart
2017-10-21 10:29 ` Applied "ASoC: Intel: move machine drivers to dedicated KConfig" to the asoc tree Mark Brown
2017-09-08 20:57 ` [RFC PATCH 7/8] ASoC: Intel: reorder boards Kconfig by chronological order Pierre-Louis Bossart
2017-09-26 4:24 ` Vinod Koul
2017-10-21 10:28 ` Applied "ASoC: Intel: reorder boards Kconfig by chronological order" to the asoc tree Mark Brown
2017-09-08 20:57 ` [RFC PATCH 8/8] ASoC: Intel: clarify Kconfig dependencies Pierre-Louis Bossart
2017-10-21 10:27 ` Applied "ASoC: Intel: clarify Kconfig dependencies" to the asoc tree Mark Brown
2017-09-25 19:09 ` [RFC PATCH 0/8] Prepare Sound Open Firmware (SOF) driver integration Mark Brown
2017-09-25 21:49 ` Liam Girdwood
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=20170926041808.GK30097@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@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