<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:宋体;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:宋体;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@宋体";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Raymond,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Raymond Yau [mailto:superquad.vortex2@gmail.com]
<br>
<b>Sent:</b> Monday, August 10, 2015 12:23 PM<br>
<b>To:</b> Yang, Libin<br>
<b>Cc:</b> alsa-devel@alsa-project.org; Takashi Iwai; Lin, Mengdong; intel-gfx@lists.freedesktop.org<br>
<b>Subject:</b> RE: [alsa-devel] [PATCH 3/4] ALSA: hda - display audio call ncts callback<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><br>
2015-8-10 <span lang="ZH-CN" style="font-family:宋体">上午</span>11:15<span lang="ZH-CN" style="font-family:宋体">於</span> "Yang, Libin" <<a href="mailto:libin.yang@intel.com">libin.yang@intel.com</a>><span lang="ZH-CN" style="font-family:宋体">寫道:</span><br>
><br>
> Hi Raymond,<br>
><br>
> ><br>
> > > > }<br>
> > > ><br>
> > > > + if (is_haswell_plus(codec)) {<br>
> > > > + if (acomp && acomp->ops && acomp->ops->set_ncts)<br>
> > > > + acomp->ops->set_ncts(acomp->dev, per_pin-<br>
> > > >pin_nid - 4,<br>
> > ><br>
> > > Please describe more how "pin_nid - 4" is supposed to work. Also...<br>
> ><br>
> > OK, I see.<br>
> ><br>
> > ><br>
> > > > + 0, runtime->rate);<br>
> > ><br>
> > > ... this implies that no MST support included?<br>
> ><br>
> > We will support MST later. Currently I just add the<br>
> > interface to support MST, but not implementing it.<br>
> Refer to DCN HDA040-A<br>
> Multi-stream over Single Display Port<br>
> Can the driver use subdevices for those display port support multi streaming ?<br>
><br>
> [Libin] What do you mean subdevice here,<br>
> using a struct device to represent a dev_entry or an int type?<o:p></o:p></p>
<p><a href="http://git.kernel.org/cgit/linux/kernel/git/tiwai/hda-emu.git/tree/codecs/stac9227-intel-d946gzis-mobo?id=HEAD">http://git.kernel.org/cgit/linux/kernel/git/tiwai/hda-emu.git/tree/codecs/stac9227-intel-d946gzis-mobo?id=HEAD</a>
<o:p></o:p></p>
<p>When HDA codecs have three Audio Input widgets, the driver create three subdevices for those desktop which have three or more input sources in the past<span style="color:#1F497D"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This is what we are thinking currently. Different companies
<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">have different implementation. On currently Intel platforms,
<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">it may show several pin widgets and each pin widget has<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">several device entry. But it actually only support 3 streams.<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mengdong is thinking to use dynamic PCM to implement it,<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">and so we don’t need each subdevice for each device entry.<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m not sure we will use what solution. It seems it is a<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">good open question to discuss.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Libin<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p>ARECORD<o:p></o:p></p>
<p>**** List of CAPTURE Hardware Devices ****<br>
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]<br>
Subdevices: 3/3<br>
Subdevice #0: subdevice #0<br>
Subdevice #1: subdevice #1<br>
Subdevice #2: subdevice #2<o:p></o:p></p>
<p>With the auto generic parser , the driver create one subdevice for Analog two subdevices for Alt Analog
<o:p></o:p></p>
<p>**** List of CAPTURE Hardware Devices ****<br>
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]<br>
Subdevices: 1/1<br>
Subdevice #0: subdevice #0<br>
card 0: Intel [HDA Intel], device 2: STAC92xx Alt Analog [STAC92xx Alt Analog]<br>
Subdevices: 2/2<br>
Subdevice #0: subdevice #0<br>
Subdevice #1: subdevice #1<o:p></o:p></p>
<p>><br>
> The specification allow up to 64 device entries<br>
> This mean the number of subdevices is equal to the device list length<br>
> More than one audio output /converters can be connected to the multi stream displayport pin widget but different device entry while only one audio output can be dynamically allocated to other HDMI pin widget<br>
><br>
> [Libin] Yes, Pin widget can have multiple device entry and connecting different converters. The audio output will be based on device entry.<o:p></o:p></p>
</div>
</div>
</body>
</html>