alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Rojewski, Cezary" <cezary.rojewski@intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH] ASoC: Intel: Do not load legacy SST driver on BYT when SND_SOC_SOF_BAYTRAIL is enabled
Date: Mon, 12 Oct 2020 09:42:23 +0200	[thread overview]
Message-ID: <6fbc7ba0-646a-27b9-8879-e9f4045385fa@redhat.com> (raw)
In-Reply-To: <b92b6b6d382048829a37ae803d4f9451@intel.com>

Hi,

On 10/12/20 9:24 AM, Rojewski, Cezary wrote:
> On 2020-10-11 11:53 AM, Hans de Goede wrote:
>> The legacy 80860F28 / sst_acpi_baytrail_desc match in sst_acpi_match
>> is already conditional on the the newer SND_SST_IPC_ACPI driver not
>> being enabled.
>>
>> But now that we have an even newer driver in the form of SOF support
>> for BYT devices, we also need to take this into account, so we also
>> must not include the sst_acpi_baytrail_desc match when
>> SND_SOC_SOF_BAYTRAIL is enabled.
>>
>> This fixes snd-soc-sst-acpi binding to the 80860F28 platform device,
>> blocking snd-sof-acpi from binding, which breaks audio support.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
> 
> Hello,
> 
> Series:
> [PATCH v2 00/13] ASoC: Intel: Remove obsolete solutions and components
> https://lore.kernel.org/alsa-devel/20201006064907.16277-1-cezary.rojewski@intel.com/
> 
> removes sst-acpi component along with many others so further changes to
> said component will only cause conflicts -or- require commit reordering.
> I'd advice against that.

As I already mentioned in the private-thread which Pierre-Louis started
with me, Jaroslav Kysela and Liam about this I would advice against applying
that series for now. First we need to put in more work to make sure that
the new drivers are actually ready.

Also I must say that I'm quite disappointed that since I, as the person
who more or less single handedly have made sure that audio works properly o
Bay Trail and Cherry Traul devices (*), has not been Cc-ed on that series,
that seems like a huge oversight.

Anyways I will reply in the thread of the series and ask Mark to revert
the entire series. Since IMHO the new drivers are clearly not ready yet.
Yesterday I ran my first set of tested and I immediately hit a DSP
hang doing just a few very basic tests.

Regards,

Hans



*) And kept it working properly despite other people breaking it with changes
like moving the userspace stuff to UCM2.


  reply	other threads:[~2020-10-12  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11  9:53 [PATCH] ASoC: Intel: Do not load legacy SST driver on BYT when SND_SOC_SOF_BAYTRAIL is enabled Hans de Goede
2020-10-12  7:24 ` Rojewski, Cezary
2020-10-12  7:42   ` Hans de Goede [this message]
2020-10-12  7:58     ` Rojewski, Cezary
2020-10-12  8:12       ` Hans de Goede

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=6fbc7ba0-646a-27b9-8879-e9f4045385fa@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pierre-louis.bossart@linux.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).