All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>, ojab // <ojab@ojab.ru>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [alsa-devel] No sound since 5.4 on skl_n88l25_s4567
Date: Thu, 16 Jan 2020 14:57:08 +0000	[thread overview]
Message-ID: <20200116145708.GQ3897@sirena.org.uk> (raw)
In-Reply-To: <6d0f1830-a2f0-997a-99cc-05c268acefc6@linux.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 482 bytes --]

On Wed, Jan 15, 2020 at 07:04:48PM -0600, Pierre-Louis Bossart wrote:

> Maybe we could have some sort of boolean flag in the component->driver
> definition and explicitly request a backwards-compatible behavior (e.g. for
> all SKL/KBL machine drivers) when that driver is known to be flaky. There's
> already things like 'fully_routed', maybe we can add something such as
> 'disable_route_check'?

A quirk for old stuff that can't be fixed sounds like a sensible
solution to this.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2020-01-16 14:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKzrAgTD2oeyajKGOaPea98vZ-uKJOn6uOqABA+CKtpvYpWYvQ@mail.gmail.com>
     [not found] ` <CAKzrAgTCE4btXr04pkvLUG6PPbtn9dm5h_9rjqDYG0HrTZ0zbg@mail.gmail.com>
2020-01-15  0:23   ` [alsa-devel] No sound since 5.4 on skl_n88l25_s4567 Kuninori Morimoto
2020-01-15  1:41     ` Pierre-Louis Bossart
2020-01-15 11:57       ` ojab //
2020-01-15 15:07         ` Pierre-Louis Bossart
2020-01-15 17:54           ` ojab //
2020-01-15 19:38             ` Pierre-Louis Bossart
2020-01-16  0:32               ` Kuninori Morimoto
2020-01-16  1:04                 ` Pierre-Louis Bossart
2020-01-16  1:42                   ` Kuninori Morimoto
2020-01-16 14:57                   ` Mark Brown [this message]
2020-02-17 15:10                     ` ojab //
2020-02-18 16:24                       ` Pierre-Louis Bossart
2020-02-20 17:19                         ` ojab //
2020-01-15 11:59     ` ojab //

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=20200116145708.GQ3897@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=ojab@ojab.ru \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@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 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.