From: Mario Limonciello <mario.limonciello@amd.com>
To: potturu venkata prasad <venkataprasad.potturu@amd.com>,
"..." <end.to.start@mail.ru>, Mark Brown <broonie@kernel.org>
Cc: Vijendar.Mukunda@amd.com, Basavaraj.Hiregoudar@amd.com,
Sunil-kumar.Dommati@amd.com, syed.sabakareem@amd.com,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Jiawei Wang <me@jwang.link>,
"open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..."
<linux-sound@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] ASoC: amd: yc: Fix the wrong return value
Date: Tue, 17 Dec 2024 08:14:15 -0600 [thread overview]
Message-ID: <511e8690-f5a7-4d59-af3f-58184727dc1b@amd.com> (raw)
In-Reply-To: <e5a42dbb-ff8e-486d-ab2c-66798af1fd80@amd.com>
On 12/17/2024 04:34, potturu venkata prasad wrote:
> Hi,
>
> On 12/17/24 15:52, ... wrote:
>> the patch that has already been added to the kernel breaks the work of
>> acp6x and the microphone no longer works, so far I am looking for the
>> reason in this person's code, but it is obvious that this patch breaks
>> the work of acp6x.
> We have tested this patch at our end, it's working fine.
> Could you please share the dev_dbg logs.
>
> With this patch if ACPI method read failure then jump to check dmi
> entry, if dmi entries also not found then driver won't register sound
> card it will return -ENODEV.
>
> Could you please share more details on this issue.
>
Do you perhaps have microphone disabled in your BIOS?
I think it would be really helpful to open a kernel bugzilla and attach
the output of the following:
1) acpidump > acpidump.bin
(attach acpidump.bin)
2) dmesg > dmesg.txt
(attach dmesg.txt)
3) dmidecode > dmidecode.txt
(attach dmidecode.txt)
prev parent reply other threads:[~2024-12-17 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 9:10 Venkata Prasad Potturu
2024-12-10 14:51 ` Mark Brown
[not found] ` <1734430927.112015823@f318.i.mail.ru>
2024-12-17 10:34 ` potturu venkata prasad
2024-12-17 14:14 ` Mario Limonciello [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=511e8690-f5a7-4d59-af3f-58184727dc1b@amd.com \
--to=mario.limonciello@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=end.to.start@mail.ru \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=me@jwang.link \
--cc=perex@perex.cz \
--cc=syed.sabakareem@amd.com \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.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
all inboxes | Powered by JetHome®