From: Takashi Iwai <tiwai@suse.de>
To: Libin Yang <libin.yang@linux.intel.com>
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: Mon, 09 Nov 2015 08:58:52 +0100 [thread overview]
Message-ID: <s5hmvunk3ib.wl-tiwai@suse.de> (raw)
In-Reply-To: <5639A452.20106@linux.intel.com>
On Wed, 04 Nov 2015 07:23:14 +0100,
Libin Yang wrote:
>
>
> 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.
Well, only judging from the quick glance, I don't buy this strategy,
sorry. Currently for HDMI/DP, the jack is for PCM, not for pin.
Namely, user-space watches the jack notification to judge whether the
corresponding PCM is available or not. You're trying to change this
scheme completely.
So, please convince us why this change is needed and which merit /
demerit it'll bring. Let's start from that point.
thanks,
Takashi
next prev parent reply other threads:[~2015-11-09 7:58 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
2015-11-09 7:58 ` Takashi Iwai [this message]
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=s5hmvunk3ib.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=libin.yang@intel.com \
--cc=libin.yang@linux.intel.com \
--cc=mengdong.lin@linux.intel.com \
/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