From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: libin.yang@intel.com, "Lin, Mengdong" <mengdong.lin@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: HDMI hotplug on Skylake when power well is off
Date: Thu, 16 Jul 2015 14:09:08 +0530 [thread overview]
Message-ID: <20150716083908.GI5086@localhost> (raw)
In-Reply-To: <s5hmvyxn0uh.wl-tiwai@suse.de>
On Wed, Jul 15, 2015 at 12:59:02PM +0200, Takashi Iwai wrote:
> On Wed, 15 Jul 2015 11:05:22 +0200,
> David Henningsson wrote:
> >
> > Hi,
> >
> > I'm trying to debug an issue here where the HDMI hotplug events are not
> > delivered to the audio side when the power well is off. This is on a
> > Skylake machine (running in HDA mode).
> >
> > I'm not sure whether the problem is upstream or due to my own patches
> > while testing, so I was wondering how this is supposed to be working, so
> > I can troubleshoot further?
> >
> > Should there be an IRQ on the HDA controller even if the power well is
> > off, and if not, how should the audio driver be notified that an HDMI
> > hotplug event has happened?
>
> I thought this has been always a problem when the runtime PM is
> enabled, no matter whether the power well state is.
Shouldn't the hotplug action turn on the power well? Then notification for
audio side should get propagated as power well is On
>
> IMO, a cleaner solution would be rather the notifier implementation in
> software, e.g. extend the i915 component to pass the audio side ops
> for notification.
Yes that should be added but I would prefer we have hw do that as well
--
~Vinod
next prev parent reply other threads:[~2015-07-16 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 9:05 HDMI hotplug on Skylake when power well is off David Henningsson
2015-07-15 10:59 ` Takashi Iwai
2015-07-16 8:39 ` Vinod Koul [this message]
2015-07-16 9:34 ` David Henningsson
2015-07-16 10:02 ` Vinod Koul
2015-07-16 10:06 ` Takashi Iwai
2015-07-16 11:35 ` Vinod Koul
2015-07-16 12:21 ` Takashi Iwai
2015-07-16 13:37 ` David Henningsson
2015-07-16 13:57 ` Takashi Iwai
2015-07-17 11:17 ` Vinod Koul
2015-07-17 13:06 ` Takashi Iwai
2015-07-17 11:14 ` Vinod Koul
2015-07-17 13: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=20150716083908.GI5086@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=libin.yang@intel.com \
--cc=mengdong.lin@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 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.