From: Anshuman Gupta <anshuman.gupta@intel.com>
To: puneethx.prabhu@intel.com, lgirdwood@gmail.com,
broonie@kernel.org, perex@perex.cz, rafael@kernel.org
Cc: alsa-devel@alsa-project.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, anshuman.gupta@intel.com
Subject: [PATCH v2 0/1] cover-letter hdac-codec runtime suspended at PM:Suspend.
Date: Sat, 18 Aug 2018 23:42:02 +0530 [thread overview]
Message-ID: <1534615923-8541-1-git-send-email-anshuman.gupta@intel.com> (raw)
In-Reply-To: <CAJZ5v0hyk=jto8Wt0er==YmKEsgvfvZhO2wDbGOhxZaWWCNgBg@mail.gmail.com>
Current implementation of hdac hdmi codec driver uses its
suspend/resume operation callback in its prepare/complete callback
which has issues with hdac direct-complete, it has been reviewed earlier
that hdac hdmi codec driver requires a rework
(https://patchwork.kernel.org/patch/10276021/),
but as there is no rework with driver, it require to fix hdac direct complete
issue to leverage hdac direct complete in order to optimize its resume latency
while resuming from system wide suspend.
Anshuman Gupta (1):
hdac-codec runtime suspended at PM:Suspend.
sound/soc/codecs/hdac_hdmi.c | 6 ++++++
1 file changed, 6 insertions(+)
--
2.7.4
next prev parent reply other threads:[~2018-08-18 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 11:17 [PATCH] [sound] hdac-codec runtime suspended at PM:Suspend Anshuman Gupta
2018-03-12 11:26 ` Rafael J. Wysocki
[not found] ` <5aa8fbe9.4251620a.c3daa.3711SMTPIN_ADDED_BROKEN@mx.google.com>
2018-03-14 10:53 ` Rafael J. Wysocki
[not found] ` <20180314153714.GA11459@anshuman.gupta@intel.com>
2018-03-15 10:42 ` Subhransu S. Prusty
[not found] ` <20180315153230.GA16531@anshuman.gupta@intel.com>
2018-03-26 7:03 ` Subhransu S. Prusty
2018-03-26 7:30 ` Takashi Iwai
2018-03-27 15:36 ` Lukas Wunner
2018-08-18 18:12 ` Anshuman Gupta [this message]
2018-08-18 18:12 ` [PATCH v2 1/1] " Anshuman Gupta
2018-08-28 16:34 ` Anshuman Gupta
2018-08-28 17:05 ` 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=1534615923-8541-1-git-send-email-anshuman.gupta@intel.com \
--to=anshuman.gupta@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=perex@perex.cz \
--cc=puneethx.prabhu@intel.com \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).