From: Shuming Fan via B4 Relay <devnull+shumingf.realtek.com@kernel.org>
To: broonie@kernel.org, lgirdwood@gmail.com
Cc: Shuming Fan <shumingf@realtek.com>,
derek.fang@realtek.com, lars@metafoo.de, oder_chiou@realtek.com,
linux-sound@vger.kernel.org, flove@realtek.com,
jack.yu@realtek.com
Subject: [PATCH v2 1/3] soundwire: intel_auxdevice: add rt766/rt767 codec to wake_capable_list
Date: Thu, 24 Sep 2026 13:53:02 +0800 [thread overview]
Message-ID: <20260924-rt766-v2-1-e0b63606a5e8@realtek.com> (raw)
In-Reply-To: <20260924-rt766-v2-0-e0b63606a5e8@realtek.com>
From: Shuming Fan <shumingf@realtek.com>
rt766/rt767 have wake capability. Add it to the wake_capable_list.
Signed-off-by: Shuming Fan <shumingf@realtek.com>
---
drivers/soundwire/intel_auxdevice.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/soundwire/intel_auxdevice.c b/drivers/soundwire/intel_auxdevice.c
index a8407560bf4f..bcf94ea38cab 100644
--- a/drivers/soundwire/intel_auxdevice.c
+++ b/drivers/soundwire/intel_auxdevice.c
@@ -73,6 +73,8 @@ static struct wake_capable_part wake_capable_list[] = {
{0x025d, 0x717},
{0x025d, 0x721},
{0x025d, 0x722},
+ {0x025d, 0x766},
+ {0x025d, 0x767},
{0x04b3, 0x9356},
};
--
2.55.0
next prev parent reply other threads:[~2026-09-24 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 5:53 [PATCH v2 0/3] Add ASoC machine driver support for the RT766 and RT767 codecs Shuming Fan via B4 Relay
2026-09-24 5:53 ` Shuming Fan via B4 Relay [this message]
2026-09-24 5:53 ` [PATCH v2 2/3] ASoC: sdw_utils: Add rt766/rt767 support Shuming Fan via B4 Relay
2026-09-24 5:53 ` [PATCH v2 3/3] ASoC: rt766: avoid re-initialize the blind write Shuming Fan via B4 Relay
2026-09-24 18:46 ` (subset) [PATCH v2 0/3] Add ASoC machine driver support for the RT766 and RT767 codecs Mark Brown
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=20260924-rt766-v2-1-e0b63606a5e8@realtek.com \
--to=devnull+shumingf.realtek.com@kernel.org \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=shumingf@realtek.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