[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5830451.DvuYhMxLoT@qlaptoparch>
Date: Fri, 19 Apr 2024 15:40:55 +0000
From: Qi Qi <ArcticLampyrid@...look.com>
To: Charles Keepax <ckeepax@...nsource.cirrus.com>
CC: "sbinding@...nsource.cirrus.com" <sbinding@...nsource.cirrus.com>,
"david.rhodes@...rus.com" <david.rhodes@...rus.com>,
"james.schulman@...rus.com" <james.schulman@...rus.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-sound@...r.kernel.org" <linux-sound@...r.kernel.org>,
"patches@...nsource.cirrus.com" <patches@...nsource.cirrus.com>,
"rf@...nsource.cirrus.com" <rf@...nsource.cirrus.com>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH v3 2/2] ALSA: hda/realtek: Fix internal speakers for
Legion Y9000X 2022 IAH7
I believe we should obey the type declared in DSDT table if it exists, in
general case.
Could you please explain why it did not solve the interrupt? Is it a
misleading item in DSDT?
Thanks for your reply.
Powered by blists - more mailing lists