<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [BDW][Audio][HD-A Display] DP/HDMI audio playback abnormal"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91410#c28">Comment # 28</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [BDW][Audio][HD-A Display] DP/HDMI audio playback abnormal"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91410">bug 91410</a>
from <span class="vcard"><a class="email" href="mailto:jim.bride@linux.intel.com" title="Jim Bride <jim.bride@linux.intel.com>"> <span class="fn">Jim Bride</span></a>
</span></b>
<pre>(In reply to Vasily Khoruzhick from <a href="show_bug.cgi?id=91410#c27">comment #27</a>)
<span class="quote">> (In reply to Jani Nikula from <a href="show_bug.cgi?id=91410#c26">comment #26</a>)
>
> > + return dev_priv->cdclk_freq;
> > }
> >
> > static int i915_audio_component_sync_audio_rate(struct device *dev,
>
> Is it initialized early enough to allow audio driver querying a clock?</span >
I think the more interesting question is whether or not the HDA driver is
trying to get the CDCLK information too early, which I think it is for the case
of rendering sound to an audio output device that is built into an external
monitor. Currently the HDA driver is getting CDCLK during it's initial
initialization (azx_first_init()) and only updates it when processing a resume
event (azx_resume() and azx_runtime_resume().) These three cases make sense to
me, but I think there's something missing. Since CDCLK can be changed in the
process of initializing a particular port, I wonder if, as Ville suggests, we
wouldn't be better off setting the CDCLK-related state (EM4 & EM5) as a part of
pin_eld_notify() as well.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>