All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Vinod Koul <vinod.koul@intel.com>,
	Jarkko Nikula <jarkko.nikula@linux.jf.intel.com>,
	lgirdwood@gmail.com, tiwai@suse.de, broonie@kernel.org,
	subhransu.s.prusty@intel.com
Subject: Re: [PATCH v2 0/5] ASoC: Intel: ACPI support and machines
Date: Tue, 04 Nov 2014 09:15:10 +0000	[thread overview]
Message-ID: <1415092510.7168.9.camel@loki> (raw)
In-Reply-To: <545896DE.4030305@linux.intel.com>

On Tue, 2014-11-04 at 11:05 +0200, Jarkko Nikula wrote:
> Hi
> 
> On 11/04/2014 10:25 AM, Vinod Koul wrote:
> > On Tue, Nov 04, 2014 at 10:09:40AM +0200, Jarkko Nikula wrote:
> >>
> >> I think there is need to have some consolidation with current
> >> byt-rt5640 and byt-max98090. Since existing drivers and this set are
> >> using the same ACPI IDs "80860F28" for the ADSP and "10EC5640" codec
> >> ACPIID for the machine driver probing these drivers won't work
> >> together.
> > Liam's suggestion was to remove the current driver when all the bits are
> > upstream

I think we need to keep the original driver around a bit longer until
the new driver is stable on rambi and other platforms the old driver
supports atm. A that point we can depricate the original driver with a
view to eventual removal.

> Yeah, I'm not against it but we must avoid regressions and perhaps try 
> to do seamless handover if possible. It's always more nice to find 
> regression in a small than big patch when bisecting :-)
> 

Liam

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

  reply	other threads:[~2014-11-04  9:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  5:31 [PATCH v2 0/5] ASoC: Intel: ACPI support and machines Vinod Koul
2014-11-04  5:31 ` [PATCH v2 1/5] ASoC: Intel: mrfld - remove unnecessary check for pointer Vinod Koul
2014-11-04  5:31 ` [PATCH v2 2/5] ASoC: Intel: mrfld - create separate module for pci part Vinod Koul
2014-11-04  5:31 ` [PATCH v2 3/5] ASoC: Intel: mrfld - add shim save restore Vinod Koul
2014-11-04  5:31 ` [PATCH v2 4/5] ASoC: Intel: mrfld- add ACPI module Vinod Koul
2014-11-04  5:31 ` [PATCH v2 5/5] ASoC: Intel: add BYTCR machine driver with RT5640 Vinod Koul
2014-11-04  9:19   ` Jarkko Nikula
2014-11-04  9:32     ` Vinod Koul
2014-11-05  7:54       ` Jarkko Nikula
2014-11-05  8:44         ` Vinod Koul
2014-11-04  8:09 ` [PATCH v2 0/5] ASoC: Intel: ACPI support and machines Jarkko Nikula
2014-11-04  8:25   ` Vinod Koul
2014-11-04  9:05     ` Jarkko Nikula
2014-11-04  9:15       ` Liam Girdwood [this message]
2014-11-04  9:31         ` Vinod Koul
2014-11-04  9:33       ` Vinod Koul
2014-11-04 11:15       ` Mark Brown
2014-11-05  7:49         ` Jarkko Nikula
2014-11-05  8:43           ` 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=1415092510.7168.9.camel@loki \
    --to=liam.r.girdwood@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jarkko.nikula@linux.jf.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=subhransu.s.prusty@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.