From: Zhang Yi <zhangyi@everest-semi.com>
To: broonie@kernel.org, tiwai@suse.com, linux-sound@vger.kernel.org
Cc: peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
ckeepax@opensource.cirrus.com, vkoul@kernel.org,
Zhang Yi <zhangyi@everest-semi.com>
Subject: [PATCH v12 6/6] soundwire: intel_auxdevice: Add es9356 to wake_capable_list
Date: Sat, 9 May 2026 18:11:02 +0800 [thread overview]
Message-ID: <20260509101102.10286-7-zhangyi@everest-semi.com> (raw)
In-Reply-To: <20260509101102.10286-1-zhangyi@everest-semi.com>
Add es9356 to the wake_capable_list
because it can generate jack events whilst the bus is stopped
Signed-off-by: Zhang Yi <zhangyi@everest-semi.com>
---
drivers/soundwire/intel_auxdevice.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soundwire/intel_auxdevice.c b/drivers/soundwire/intel_auxdevice.c
index ee951be15..0b8107bec 100644
--- a/drivers/soundwire/intel_auxdevice.c
+++ b/drivers/soundwire/intel_auxdevice.c
@@ -72,6 +72,7 @@ static struct wake_capable_part wake_capable_list[] = {
{0x025d, 0x717},
{0x025d, 0x721},
{0x025d, 0x722},
+ {0x04b3, 0x9356},
};
static bool is_wake_capable(struct sdw_slave *slave)
--
2.17.1
next prev parent reply other threads:[~2026-05-09 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 10:10 [PATCH v12 0/6] Add es9356 focused SoundWire CODEC Zhang Yi
2026-05-09 10:10 ` [PATCH v12 1/6] ASoC: sdw_utils: add soc_sdw_es9356 Zhang Yi
2026-05-10 11:44 ` Mark Brown
2026-05-09 10:10 ` [PATCH v12 2/6] ASoC: sdw_utils: add ES9356 in codec_info_list Zhang Yi
2026-05-09 10:10 ` [PATCH v12 3/6] ASoC: es9356-sdca: Add ES9356 SDCA driver Zhang Yi
2026-05-09 10:11 ` [PATCH v12 4/6] ASoC: Intel: soc-acpi: arl: Add es9356 support Zhang Yi
2026-05-09 10:11 ` [PATCH v12 5/6] ASoC: Intel: sof_sdw: add " Zhang Yi
2026-05-09 10:11 ` Zhang Yi [this message]
2026-05-09 11:58 ` [PATCH v12 0/6] Add es9356 focused SoundWire CODEC Pierre-Louis Bossart
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=20260509101102.10286-7-zhangyi@everest-semi.com \
--to=zhangyi@everest-semi.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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