From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>, libin.yang@intel.com
Cc: alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH v2] ASoC: codec: hdac_hdmi add device_link to card device
Date: Tue, 16 Apr 2019 05:37:53 -0500 [thread overview]
Message-ID: <f34e1a6f-7d8a-a432-5e9f-387e891f6b4f@linux.intel.com> (raw)
In-Reply-To: <s5hpnpm5jv1.wl-tiwai@suse.de>
On 4/16/19 5:23 AM, Takashi Iwai wrote:
> On Sat, 13 Apr 2019 15:18:12 +0200,
> libin.yang@intel.com wrote:
>>
>> From: Libin Yang <libin.yang@intel.com>
>>
>> In resume from S3, HDAC HDMI codec driver dapm event callback may be
>> operated before HDMI codec driver turns on the display audio power
>> domain because of the contest between display driver and hdmi codec driver.
>>
>> This patch adds the device_link between soc card device (consumer) and
>> hdmi codec device (supplier) to make sure the sequence is always correct.
>>
>> Signed-off-by: Libin Yang <libin.yang@intel.com>
>
> Reviewed-by: Takashi Iwai <tiwai@suse.de>
>
> Is it an issue that has been present for older released kernels?
> If so, it deserves for Cc-to-stable.
Yes and no. In theory the same problem impacts the Skylake driver.
However its support for HDMI has been flaky at best, see e.g. the
probe/timing issues on Linus' laptop and a variety of devices in
December, and the only real distribution using it - ChromeOS - does not
resume from S3. Not to mention that products typically use 3.18 to 4.9.
next prev parent reply other threads:[~2019-04-16 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 13:18 [PATCH v2] ASoC: codec: hdac_hdmi add device_link to card device libin.yang
2019-04-16 10:23 ` Takashi Iwai
2019-04-16 10:37 ` Pierre-Louis Bossart [this message]
2019-04-17 1:28 ` Yang, Libin
2019-04-17 1:12 ` Yang, Libin
2019-04-19 15:17 ` Pierre-Louis Bossart
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=f34e1a6f-7d8a-a432-5e9f-387e891f6b4f@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=libin.yang@intel.com \
--cc=tiwai@suse.de \
/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).