From: Gergo Koteles <soyer@irl.hu>
To: Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
Baojun Xu <baojun.xu@ti.com>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, Gergo Koteles <soyer@irl.hu>
Subject: [PATCH 0/5] ALSA: hda/tas2781: restore power state after system_resume
Date: Fri, 8 Mar 2024 18:41:39 +0100 [thread overview]
Message-ID: <cover.1709918447.git.soyer@irl.hu> (raw)
This series makes some simplifications, speeding up the start of the
playback and restoring the power state of the amplifiers after
system_resume.
Gergo Koteles (5):
ALSA: hda/tas2781: use dev_dbg in system_resume
ALSA: hda/tas2781: add lock to system_suspend
ALSA: hda/tas2781: do not reset cur_* values in runtime_suspend
ALSA: hda/tas2781: do not call pm_runtime_force_* in
system_resume/suspend
ALSA: hda/tas2781: restore power state after system_resume
sound/pci/hda/tas2781_hda_i2c.c | 35 ++++++++++++++++-----------------
1 file changed, 17 insertions(+), 18 deletions(-)
base-commit: 90d35da658da8cff0d4ecbb5113f5fac9d00eb72
--
2.44.0
next reply other threads:[~2024-03-08 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 17:41 Gergo Koteles [this message]
2024-03-08 17:41 ` [PATCH 1/5] ALSA: hda/tas2781: use dev_dbg in system_resume Gergo Koteles
2024-03-08 17:41 ` [PATCH 2/5] ALSA: hda/tas2781: add lock to system_suspend Gergo Koteles
2024-03-08 17:41 ` [PATCH 3/5] ALSA: hda/tas2781: do not reset cur_* values in runtime_suspend Gergo Koteles
2024-03-08 17:41 ` [PATCH 4/5] ALSA: hda/tas2781: do not call pm_runtime_force_* in system_resume/suspend Gergo Koteles
2024-03-08 17:41 ` [PATCH 5/5] ALSA: hda/tas2781: restore power state after system_resume Gergo Koteles
2024-03-11 8:15 ` [PATCH 0/5] " Takashi Iwai
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=cover.1709918447.git.soyer@irl.hu \
--to=soyer@irl.hu \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=kevin-lu@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.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.