From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
ALSA ML <alsa-devel@alsa-project.org>,
Guneshwor Singh <guneshwor.o.singh@intel.com>,
Patches Audio <patches.audio@intel.com>
Subject: Re: [PATCH] ASoC: Intel: Boards: Add CNL RT274 I2S machine driver
Date: Thu, 17 May 2018 13:17:48 -0500 [thread overview]
Message-ID: <db1cfa70-8123-8eb8-bd70-5f619647d170@linux.intel.com> (raw)
In-Reply-To: <20180517063725.GM20254@sirena.org.uk>
On 5/17/18 1:37 AM, Mark Brown wrote:
> On Tue, Nov 28, 2017 at 10:44:50AM -0600, Pierre-Louis Bossart wrote:
>> On 11/28/2017 10:24 AM, Vinod Koul wrote:
>
>>> Since you are still working on the fixes, I guess this can sneak in before.
>>> The machine drivers are typically low hanging in terms on complexity so we
>>> can merge this first followed by the rework you are doing. I think that part
>>> will still take a bit to stabilize and cleanup.
>
>> the update goes out this afternoon, working on it, does this patch really
>> need to 'sneak in'?
>
> This seems to have got buried with all the Kconfig fixes and reworks? I
> was expecting a resend based on those given this discussion but that
> didn't seem to ever happen.
We have a small set of corrections to enable SOF to use this machine
driver (mainly to remove hard-coded routes that can be handled by
topology). The plan as I understand it is to first have Liam provide the
SOF core, and in a second step provide all the machine driver updates -
including this one.
next prev parent reply other threads:[~2018-05-17 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 12:44 [PATCH] ASoC: Intel: Boards: Add CNL RT274 I2S machine driver Guneshwor Singh
2017-11-27 14:45 ` Pierre-Louis Bossart
2017-11-28 16:24 ` Vinod Koul
2017-11-28 16:44 ` Pierre-Louis Bossart
2018-05-17 6:37 ` Mark Brown
2018-05-17 18:17 ` Pierre-Louis Bossart [this message]
2017-11-28 16:25 ` Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2017-11-09 3:20 Guneshwor Singh
2017-11-15 4:54 ` Vinod Koul
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=db1cfa70-8123-8eb8-bd70-5f619647d170@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guneshwor.o.singh@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@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;
as well as URLs for NNTP newsgroup(s).