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: Fri, 17 Jul 2015 16:47:24 +0530 [thread overview]
Message-ID: <20150717111724.GQ5086@localhost> (raw)
In-Reply-To: <s5hio9kjjdc.wl-tiwai@suse.de>
On Thu, Jul 16, 2015 at 03:57:03PM +0200, Takashi Iwai wrote:
> > >>> Yes. This was supposed to work with WAKEEN bits, but this didn't work
> > >>> as expected, after all.
> >
> > But this applies only to HDMI codecs and the power well, right? Analog
> > controllers could go into D3 and WAKEEN would wake them up? Or did we
> > never get that working either?
>
> Well, the analog codec wakeup never worked in my tests. Maybe some
> hardware works, who knows.
So essentialy both for analog and hdmi this never works reliably ?
I was under the impression taht this was working okay
> > Anyhow, I went searching in the video drivers for things to match on,
> > inspired by your thoughts about submitting information from the graphics
> > driver to the audio driver. See new attached patch (still writing blind
> > drafts). Let me know what you think.
>
> Thanks, this looks promising!
>
> > I think "connector->name" seems what the most reasonable thing to export
> > to userspace to indicate what gfx output is related to which audio nid,
> > and the port being what maps 1-to-1 to a nid - we'll use that for our
> > own lookup (this lookup might differ between hardware generations).
>
> Yeah, this mapping is the unresolved mystery. This mythos has to be
> revealed by Intel people.
Are you talking about nid to connctor name mapping or something else?
--
~Vinod
next prev parent reply other threads:[~2015-07-17 11:15 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
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 [this message]
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=20150717111724.GQ5086@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.