Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Libin Yang <libin.yang@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: libin.yang@intel.com, alsa-devel@alsa-project.org,
	mengdong.lin@linux.intel.com
Subject: Re: [RFC PATCH 0/2] ALSA: hda - DP MST audio for Jack support
Date: Wed, 4 Nov 2015 14:23:14 +0800	[thread overview]
Message-ID: <5639A452.20106@linux.intel.com> (raw)
In-Reply-To: <s5hsi4nni3u.wl-tiwai@suse.de>


On 11/04/2015 12:49 AM, Takashi Iwai wrote:
> On Tue, 03 Nov 2015 09:42:54 +0100,
> libin.yang@linux.intel.com wrote:
>>
>> From: Libin Yang <libin.yang@linux.intel.com>
>>
>> This is the patch set for Jack support for DP MST audio
>>
>> Libin Yang (2):
>>    ALSA: hda - jack support DP MST audio
>>    ALSA: hda - hdmi audio add dynamically jack binding to pin
>
> I'm somehow confused by this patch series.
> Is the unsolicited event handling itself changed for MST?  I mean, you
> cannot know which MST dev# is given beforehand, while you seem trying
> to assign such a number to the jack object.

Oh, sorry I forgot to mention that we only operate on device entry 0 
so far in the code. It's misleading.

These patches don't operate on MST audio. The full MST audio driver 
support will be implemented in the later patches. The patches help to 
prepare supporting MST audio.

The purpose of the patches is try to dynamically attach the Jack.

>
> We create all jacks statically at probe time.  And in MST case, each
> jack is still supposed to be corresponding to each PCM stream, not to
> each pin.  So I don't see how this fits with the big picture.

In the generic_hdmi_build_jack(), it will create the snd_jack based on 
the pcm. This is for the userspace. So userspace can see the Jack 
number is the same as PCM. The first Jack for the first PCM, and so 
on. And it is not attached to any pin at first.

In generic_hdmi_build_controls(), it will also create hda_jack_tbl 
based on the pin. The hda_jack_tbl will record the pin information.

When hotplug, in the hdmi_present_sense(), it will call 
xxx_jack_bind() to bind the snd_jack to hda_jack_tbl

>
> A bit more explanation is needed.

I will. Thanks.

Best Regards,
Libin

>
>
> thanks
>
> Takashi
>
>>
>>   sound/pci/hda/hda_jack.c   | 186 ++++++++++++++++++++++++++++++++++++++++-----
>>   sound/pci/hda/hda_jack.h   |  32 +++++++-
>>   sound/pci/hda/patch_hdmi.c | 116 ++++++++++++++++++++++------
>>   3 files changed, 288 insertions(+), 46 deletions(-)
>>
>> --
>> 1.9.1
>>

  reply	other threads:[~2015-11-04  6:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03  8:42 [RFC PATCH 0/2] ALSA: hda - DP MST audio for Jack support libin.yang
2015-11-03  8:42 ` [RFC PATCH 1/2] ALSA: hda - jack support DP MST audio libin.yang
2015-11-03  8:42 ` [RFC PATCH 2/2] ALSA: hda - hdmi audio add dynamically jack binding to pin libin.yang
2015-11-03 16:49 ` [RFC PATCH 0/2] ALSA: hda - DP MST audio for Jack support Takashi Iwai
2015-11-04  6:23   ` Libin Yang [this message]
2015-11-09  7:58     ` Takashi Iwai
2015-11-09 15:00       ` Yang, Libin
2015-11-09 15:15         ` Takashi Iwai
2015-12-22  8:47           ` Libin Yang
2015-12-22  9:00             ` Takashi Iwai
2015-12-22 11:45               ` Yang, Libin
2015-12-22 12:08                 ` Takashi Iwai
2015-12-22 13:33                   ` 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=5639A452.20106@linux.intel.com \
    --to=libin.yang@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=libin.yang@intel.com \
    --cc=mengdong.lin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox