From: Bard Liao <yung-chuan.liao@linux.intel.com>
To: broonie@kernel.org, tiwai@suse.de, vkoul@kernel.org
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, pierre-louis.bossart@linux.dev,
bard.liao@intel.com, peter.ujfalusi@linux.intel.com
Subject: [PATCH 0/2] ASoC/SoundWire: Simply interrupt enabling for Intel
Date: Mon, 7 Oct 2024 20:12:39 +0800 [thread overview]
Message-ID: <20241007121241.30914-1-yung-chuan.liao@linux.intel.com> (raw)
It is more logical to couple interrupt enabling/disabling with
power-up/down sequences.
The change is mainly on ASoC tree. Can we go via ASoC tree with Vinod's
Acked-by tag?
Pierre-Louis Bossart (2):
ASoC: SOF: Intel: hda-mlink: expose unlocked interrupt enable routine
ASoC/SoundWire: Intel: lnl: enable interrupts after first
power-up/before last power-down
drivers/soundwire/intel_ace2x.c | 7 +++++++
include/sound/hda-mlink.h | 4 ++++
sound/soc/sof/intel/hda-dsp.c | 5 -----
sound/soc/sof/intel/hda-mlink.c | 18 ++++++++++++++++++
sound/soc/sof/intel/hda.c | 2 --
sound/soc/sof/intel/lnl.c | 10 ----------
6 files changed, 29 insertions(+), 17 deletions(-)
--
2.43.0
next reply other threads:[~2024-10-07 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 12:12 Bard Liao [this message]
2024-10-07 12:12 ` [PATCH 1/2] ASoC: SOF: Intel: hda-mlink: expose unlocked interrupt enable routine Bard Liao
2024-10-07 12:12 ` [PATCH 2/2] ASoC/SoundWire: Intel: lnl: enable interrupts after first power-up/before last power-down Bard Liao
2024-10-11 5:02 ` Vinod Koul
2024-10-12 12:50 ` [PATCH 0/2] ASoC/SoundWire: Simply interrupt enabling for Intel 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=20241007121241.30914-1-yung-chuan.liao@linux.intel.com \
--to=yung-chuan.liao@linux.intel.com \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=tiwai@suse.de \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
/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