From: Sven Frotscher <sven.frotscher@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
mario.limonciello@amd.com, git@augustwikerfors.se,
alsa-devel@alsa-project.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v4] ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM
Date: Mon, 02 Oct 2023 15:17:33 +0200 [thread overview]
Message-ID: <9XKW1S.IRRCIDM08XWX1@gmail.com> (raw)
In-Reply-To: <89698b5f-a616-4f49-802a-21326a868c7f@sirena.org.uk>
>> > Until someone tests or otherwise provides specific information on
>> a
>> > given machine we're just guessing about how it's wired up.
>
>> What specific information are we talking about here? I have the
>> 82YM in
>> front of me and could help investigate.
>
> We need to know what magic set of quirks makes the thing work. Are
> you
> saying that your patch doesn't actually do that?
It does.
Maybe the non-quirk check (ll. 395-403, seems to be using ACPI) is too
specific? But I'm a bit out of my depth here, so I can't investigate
that by myself.
next prev parent reply other threads:[~2023-10-05 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 22:36 [PATCH v4] ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM Sven Frotscher
2023-10-02 9:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-02 11:52 ` Mark Brown
2023-10-02 12:28 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-02 12:54 ` Mark Brown
2023-10-02 13:00 ` Sven Frotscher
2023-10-02 13:04 ` Mark Brown
2023-10-02 13:17 ` Sven Frotscher [this message]
2023-10-02 13:47 ` Mark Brown
2023-10-02 13:47 ` Mario Limonciello
2023-10-02 14:13 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-02 14:20 ` Mario Limonciello
2023-10-02 14:36 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-02 14:40 ` Sven Frotscher
2023-10-02 18:51 ` Mark Brown
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=9XKW1S.IRRCIDM08XWX1@gmail.com \
--to=sven.frotscher@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=git@augustwikerfors.se \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.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.