From: Takashi Iwai <tiwai@suse.de>
To: Matthew Anderson <ruinairas1992@gmail.com>
Cc: tanure@linux.com, voreck-lukas@tutanota.com,
Bagasdotme <bagasdotme@gmail.com>,
Alsa Devel <alsa-devel@alsa-project.org>,
Andy Chi <andy.chi@canonical.com>,
David Rhodes <david.rhodes@cirrus.com>,
Faenkhauser <faenkhauser@gmail.com>,
James Schulman <james.schulman@cirrus.com>,
Kailang <kailang@realtek.com>, L Guzenko <l.guzenko@web.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Sound <linux-sound@vger.kernel.org>, Luke <luke@ljones.dev>,
Overloader <overloader@tutanota.com>,
Patches <patches@opensource.cirrus.com>, Perex <perex@perex.cz>,
Rf <rf@opensource.cirrus.com>,
Sbinding <sbinding@opensource.cirrus.com>,
Shenghao Ding <shenghao-ding@ti.com>, Tiwai <tiwai@suse.com>,
Tsengalb99 <tsengalb99@gmail.com>,
Vitalyr <vitalyr@opensource.cirrus.com>,
Yangyuchi66 <yangyuchi66@gmail.com>
Subject: Re: Fwd: No sound drivers on HP Envy x360 ey0xxx
Date: Thu, 04 Jan 2024 10:36:06 +0100 [thread overview]
Message-ID: <87cyuha1a1.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAEnG5GADVZeFe55dPyEDbQA_jeNqQLNvCRPK4vBCMPCq25gmdA@mail.gmail.com>
On Wed, 03 Jan 2024 17:19:31 +0100,
Matthew Anderson wrote:
>
> They have something working around it on Windows. It's the same issue we've
> had to work around on Asus devices such as the ROG Ally.
>
> You can use DSDT overrides to enable audio on Linux but this is dangerous
> and not recommended because we have no way of knowing the safe values to
> use.
>
> Asus eventually pushed an update adding the missing information for the ROG
> ally so it's no longer an issue. This is the proper solution.
There are recent additions to apply the static configuration for such
machines with broken BIOSen. For HP, it'll be included in 6.8,
currently found in for-next branch (or topic/cs35l41 branch) of
sound.git tree.
You'd need to adjust the quirk tables in both
sound/pci/hda/patch_realtek.c and sound/pci/hda/cs35l41_hda_property.c
to match with yours.
HTH,
Takashi
>
> On Wed, Jan 3, 2024, 9:56 AM Lucas Tanure <tanure@linux.com> wrote:
>
> >
> >
> > On Wed, 3 Jan 2024, 11:47 Matthew Anderson, <ruinairas1992@gmail.com>
> > wrote:
> >
> >> The issue is that HP does not provide the DSD information in the BIOS for
> >> the Cirrus Amp. I've already emailed HP informing them of the issue. I too
> >> have a newer HP Envy X360 which has the same problem.
> >>
> >> On Wed, Jan 3, 2024, 8:28 AM Lucas Tanure <tanure@linux.com> wrote:
> >>
> >>>
> >>>
> >>> On Wed, 3 Jan 2024, 08:23 , <voreck-lukas@tutanota.com> wrote:
> >>>
> >>>> I hope I'm responding correctly
> >>>>
> >>>> On bugzilla I was asked to attach dmesg and lspci output. I'm sending
> >>>> both as attachments (cause of their length) and hope it works, it's my
> >>>> first time working with these mailing lists.
> >>>>
> >>>
> >>> Hi,
> >>>
> >>> The most important thing to start is the DSDT dump from your Bios.
> >>> That should describe the key points about the hardware configuration.
> >>>
> >>> Thanks
> >>> Lucas Tanure
> >>>
> >>
> > Are you sure?
> > How the can Windows driver be loaded without that?
> >
> >>
next prev parent reply other threads:[~2024-01-04 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 11:23 Fwd: No sound drivers on HP Envy x360 ey0xxx voreck-lukas
[not found] ` <CAJX_Q+0NL1_dkLD2oePhW+EjvGiPLQ7S-1jarz4dANm12iHNMg@mail.gmail.com>
[not found] ` <CAEnG5GAsD_Db7G3TGkfA+bjO64V6tJuGph1dLOnvGhYicvLW_Q@mail.gmail.com>
[not found] ` <CAJX_Q+1OoXdBAv=tMFdD1-Kfg0sDdnDjbYDpU9g8YfOeECwukA@mail.gmail.com>
[not found] ` <CAEnG5GADVZeFe55dPyEDbQA_jeNqQLNvCRPK4vBCMPCq25gmdA@mail.gmail.com>
2024-01-04 9:36 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 3:28 Bagas Sanjaya
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=87cyuha1a1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andy.chi@canonical.com \
--cc=bagasdotme@gmail.com \
--cc=david.rhodes@cirrus.com \
--cc=faenkhauser@gmail.com \
--cc=james.schulman@cirrus.com \
--cc=kailang@realtek.com \
--cc=l.guzenko@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=overloader@tutanota.com \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=ruinairas1992@gmail.com \
--cc=sbinding@opensource.cirrus.com \
--cc=shenghao-ding@ti.com \
--cc=tanure@linux.com \
--cc=tiwai@suse.com \
--cc=tsengalb99@gmail.com \
--cc=vitalyr@opensource.cirrus.com \
--cc=voreck-lukas@tutanota.com \
--cc=yangyuchi66@gmail.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