From: "Krzysztof Wilczyński" <kw@linux.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
nicolarevelant44@gmail.com, Liam Girdwood <lgirdwood@gmail.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
sound-open-firmware@alsa-project.org, linux-pci@vger.kernel.org
Subject: Re: [Bug 214995] New: Sof audio didn't recognize Intel Smart Sound (SST) speakers, microphone and headphone jack
Date: Tue, 16 Nov 2021 17:53:06 +0100 [thread overview]
Message-ID: <YZPh8rnetEltL/v5@rocinante> (raw)
In-Reply-To: <4cf00ae5-f3d7-ecb5-7dae-f8629becc0d2@linux.intel.com>
Hello,
[...]
> That seems like a known issue already tracked at
> https://github.com/thesofproject/linux/issues/3248
>
> There's a set of devices based on the ES8316/36 I2S audio codec which
> needs dedicated quirks. In the existing reports the Huawei Matebook D15
> is listed as using that codec.
>
> The latest experimental code we have is here:
> https://github.com/thesofproject/linux/pull/3107/commits
>
> If confirmed, can we track this on GitHub so that all results for this
> sort of devices are collected in one place? Thanks!
Collecting details is definitely a good idea, however if possible, we
should open a new issue (if there isn't one about this already) using
Kernel's Bugzilla, and track it there.
A lot more users looks there (including kernel maintainers and driver
developers) for bug reports and such.
This is just a suggestion, though.
Krzysztof
prev parent reply other threads:[~2021-11-16 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-214995-41252@https.bugzilla.kernel.org/>
2021-11-12 22:24 ` [Bug 214995] New: Sof audio didn't recognize Intel Smart Sound (SST) speakers, microphone and headphone jack Bjorn Helgaas
2021-11-15 17:49 ` Pierre-Louis Bossart
2021-11-16 16:53 ` Krzysztof Wilczyński [this message]
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=YZPh8rnetEltL/v5@rocinante \
--to=kw@linux.com \
--cc=daniel.baluta@nxp.com \
--cc=helgaas@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=nicolarevelant44@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
/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).