From: David Henningsson <david.henningsson@canonical.com>
To: "Yang, Libin" <libin.yang@intel.com>, 'Takashi Iwai' <tiwai@suse.de>
Cc: "'alsa-devel@alsa-project.org'" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA: hda_intel: add AZX_DCAPS_I915_POWERWELL for skl
Date: Wed, 01 Apr 2015 09:31:12 +0200 [thread overview]
Message-ID: <551B9EC0.2060308@canonical.com> (raw)
In-Reply-To: <96A12704CE18D347B625EE2D4A099D1962E18F@SHSMSX103.ccr.corp.intel.com>
On 2015-03-30 04:47, Yang, Libin wrote:
> From our silicon team's comment, it seems we need power on
> the powerwell when detecting and probing the HDMI codec.
>
> For the skl case (HDMI codec is in powerwell, while controller not),
> my thinking is:
>
> 1. power on the power well
> 2. read STATESTS to determine the codec_mask
> 3. if codec is not present, power off the power well
> and remove the flag. (seems we need a new flag)
> 4. if codec is present, we will power on the power well
> when dealing with HDMI codec.
>
> What do you think?
Side question - do you know if it's the same for braswell? I e, the HDMI
codec is in the powerwell but the controller is not?
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2015-04-01 7:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 7:10 [PATCH] ALSA: hda_intel: add AZX_DCAPS_I915_POWERWELL for skl libin.yang
2015-03-27 7:56 ` Takashi Iwai
2015-03-27 8:02 ` Yang, Libin
2015-03-27 8:19 ` Takashi Iwai
2015-03-27 8:25 ` Yang, Libin
2015-03-27 8:30 ` Takashi Iwai
2015-03-27 8:33 ` Yang, Libin
2015-03-30 2:47 ` Yang, Libin
2015-04-01 7:31 ` David Henningsson [this message]
2015-04-01 8:00 ` Yang, Libin
2015-04-01 8:12 ` David Henningsson
2015-04-01 21:55 ` Yang, Libin
2015-04-02 6:52 ` David Henningsson
2015-04-02 7:23 ` Yang, Libin
2015-04-04 10:44 ` Takashi Iwai
2015-04-07 5:47 ` Yang, Libin
2015-04-07 6:00 ` Takashi Iwai
2015-04-07 6:12 ` Yang, Libin
2015-04-07 6:24 ` Takashi Iwai
2015-04-07 6:40 ` Yang, Libin
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=551B9EC0.2060308@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.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 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.