From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: patches.audio@intel.com, Liam <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org, Mark <broonie@kernel.org>,
Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH 0/2] ASoC: Remove mfld dead code
Date: Wed, 10 Jan 2018 14:05:55 -0600 [thread overview]
Message-ID: <0a879ca2-703b-cab6-f891-837442d0700a@linux.intel.com> (raw)
In-Reply-To: <20180110173458.GA18649@localhost>
On 1/10/18 11:34 AM, Vinod Koul wrote:
> On Wed, Jan 10, 2018 at 02:41:52PM +0200, Andy Shevchenko wrote:
>> On Wed, 2018-01-10 at 15:59 +0530, Vinod Koul wrote:
>>> Medfield machine was not compiling for long on mainline. Since no one
>>> complained, lets remove the dead code and associated codec.
>>
>> While this change seems okay per se, please keep in mind that Intel
>> Merrifield would be still in use (yes, we have no confirmation right now
>> about the status of the driver in vanilla kernel, I hope in the future
>> with SOF it could be much easier to get into working solution on Intel
>> Edison platform).
>
> This is the mfld machine and codec, mrfld machine is separate and platform
> is supported by the mfld pcm driver (which also supports byt, bsw, cht and
> so on) that is not removed so wont impact tng core work.
Getting Merrifield/Edison to work with both SOF and the closed-source
firmware is one of my objectives when I find spare cycles.
prev parent reply other threads:[~2018-01-10 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 10:29 [PATCH 0/2] ASoC: Remove mfld dead code Vinod Koul
2018-01-10 10:29 ` [PATCH 1/2] ASoC: Intel: remove mfld_machine Vinod Koul
2018-01-10 11:12 ` Applied "ASoC: Intel: remove mfld_machine" to the asoc tree Mark Brown
2018-01-10 10:29 ` [PATCH 2/2] ASoC: sn95031: remove this code Vinod Koul
2018-01-10 11:12 ` Applied "ASoC: sn95031: remove this code" to the asoc tree Mark Brown
2018-01-10 12:41 ` [PATCH 0/2] ASoC: Remove mfld dead code Andy Shevchenko
2018-01-10 17:34 ` Vinod Koul
2018-01-10 18:01 ` Andy Shevchenko
2018-01-10 20:05 ` Pierre-Louis Bossart [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=0a879ca2-703b-cab6-f891-837442d0700a@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--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