From: Mark Brown <broonie@kernel.org>
To: tiwai@suse.de, Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: linux-sound@vger.kernel.org, pierre-louis.bossart@linux.dev,
bard.liao@intel.com
Subject: Re: [PATCH] ASoC: rt1320: set wake_capable = 0 explicitly
Date: Wed, 05 Mar 2025 16:54:32 +0000 [thread overview]
Message-ID: <174119367245.160083.4867604816412375464.b4-ty@kernel.org> (raw)
In-Reply-To: <20250305134113.201326-1-yung-chuan.liao@linux.intel.com>
On Wed, 05 Mar 2025 21:41:13 +0800, Bard Liao wrote:
> "generic_new_peripheral_assigned: invalid dev_num 1, wake supported 1"
> is reported by our internal CI test.
>
> Rt1320's wake feature is not used in Linux and that's why it is not in
> the wake_capable_list[] list in intel_auxdevice.c.
> However, BIOS may set it as wake-capable. Overwrite wake_capable to 0
> in the codec driver to align with wake_capable_list[].
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: rt1320: set wake_capable = 0 explicitly
commit: 927e6bec5cf3624665b0a2e9f64a1d32f3d22cdd
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2025-03-05 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:41 [PATCH] ASoC: rt1320: set wake_capable = 0 explicitly Bard Liao
2025-03-05 16:54 ` Mark Brown [this message]
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=174119367245.160083.4867604816412375464.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=bard.liao@intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=tiwai@suse.de \
--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