All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qi Qi <ArcticLampyrid@outlook.com>
To: Stefan Binding <sbinding@opensource.cirrus.com>
Cc: "david.rhodes@cirrus.com" <david.rhodes@cirrus.com>,
	"james.schulman@cirrus.com" <james.schulman@cirrus.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
	"rf@opensource.cirrus.com" <rf@opensource.cirrus.com>
Subject: Re: [PATCH v3 1/2] ALSA: cs35l41: obey the trigger type from DSDT
Date: Fri, 19 Apr 2024 15:43:06 +0000	[thread overview]
Message-ID: <4618242.LvFx2qVVIh@qlaptoparch> (raw)
In-Reply-To: <004201da926b$986d8040$c94880c0$@opensource.cirrus.com>

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.

  reply	other threads:[~2024-04-19 15:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 13:17 [PATCH v3 0/2] ALSA: hda/realtek: Fix internal speakers for Legion Y9000X 2022 IAH7 ArcticLampyrid
2024-04-18 13:19 ` [PATCH v3 1/2] ALSA: cs35l41: obey the trigger type from DSDT ArcticLampyrid
2024-04-19 15:09   ` Stefan Binding
2024-04-19 15:43     ` Qi Qi [this message]
2024-04-18 13:20 ` [PATCH v3 2/2] ALSA: hda/realtek: Fix internal speakers for Legion Y9000X 2022 IAH7 ArcticLampyrid
2024-04-18 13:59   ` Charles Keepax
2024-04-18 14:19     ` Qi Qi
2024-04-18 14:45       ` Greg KH
2024-04-19 15:40     ` Qi Qi

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=4618242.LvFx2qVVIh@qlaptoparch \
    --to=arcticlampyrid@outlook.com \
    --cc=004201da926b$986d8040$c94880c0$@opensource.cirrus.com \
    --cc=david.rhodes@cirrus.com \
    --cc=james.schulman@cirrus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.com \
    --cc=sbinding@opensource.cirrus.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.