alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "ojab //" <ojab@ojab.ru>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	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: Mon, 17 Feb 2020 18:10:54 +0300	[thread overview]
Message-ID: <CAKzrAgQapgQtxMLYjEe9mSaXp_uYxMyH8fwvoJqM3Or0sqqfiw@mail.gmail.com> (raw)
In-Reply-To: <20200116145708.GQ3897@sirena.org.uk>

On Thu, Jan 16, 2020 at 5:57 PM Mark Brown <broonie@kernel.org> wrote:
>
> 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.

Any update on this?

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

  reply	other threads:[~2020-02-17 15:12 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
2020-02-17 15:10                     ` ojab // [this message]
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=CAKzrAgQapgQtxMLYjEe9mSaXp_uYxMyH8fwvoJqM3Or0sqqfiw@mail.gmail.com \
    --to=ojab@ojab.ru \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --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 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).