From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
ojab // <ojab@ojab.ru>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] No sound since 5.4 on skl_n88l25_s4567
Date: Tue, 14 Jan 2020 19:41:27 -0600 [thread overview]
Message-ID: <130af222-1086-ebcf-6a0f-9a390f9afbc3@linux.intel.com> (raw)
In-Reply-To: <87h80x8t41.wl-kuninori.morimoto.gx@renesas.com>
>>> Please take a look, I want my sound back ._.
>>
>> Forgot to mention, it's reproducible on linux master git.
>
> Hmm...
> This patch
> 1) removes unneeded if check
> 2) adds missing error check.
>
> 1) shouldn't have effect to your PC.
> Thus, maybe your PC failed by 2).
> It had been worked by accident before ?
> I guess your kernel is telling some message like this ?
>
> ASoC: no dapm match for %s --> %s --> %s
It's likely that the topology file does not contain all the widgets/dais
required by the hard-coded routes the machine driver, and by becoming
stricter warnings became errors which in turn prevent the card from
being created. It may be that we have to define a backwards compatible
behavior that's enabled only for Intel legacy cases.
Please post the results of alsa-info.sh somewhere so that we can take a
look.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2020-01-15 1:42 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 [this message]
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 //
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=130af222-1086-ebcf-6a0f-9a390f9afbc3@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=ojab@ojab.ru \
/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).