From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takashi Iwai <tiwai@suse.de>
Subject: Re: [RFC PATCH 0/2] ALSA: hda - DP MST audio for Jack
	support
Date: Mon, 09 Nov 2015 08:58:52 +0100
Message-ID: <s5hmvunk3ib.wl-tiwai@suse.de>
References: <1446540176-110181-1-git-send-email-libin.yang@linux.intel.com>
 <s5hsi4nni3u.wl-tiwai@suse.de> <5639A452.20106@linux.intel.com>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mx2.suse.de (mx2.suse.de [195.135.220.15])
 by alsa0.perex.cz (Postfix) with ESMTP id 851DD260464
 for <alsa-devel@alsa-project.org>; Mon,  9 Nov 2015 08:58:53 +0100 (CET)
In-Reply-To: <5639A452.20106@linux.intel.com>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/options/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel/>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Errors-To: alsa-devel-bounces@alsa-project.org
Sender: alsa-devel-bounces@alsa-project.org
To: Libin Yang <libin.yang@linux.intel.com>
Cc: libin.yang@intel.com, alsa-devel@alsa-project.org, mengdong.lin@linux.intel.com
List-Id: alsa-devel@alsa-project.org

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