From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [RFC PATCH 0/2] ALSA: hda - DP MST audio for Jack support Date: Tue, 03 Nov 2015 17:49:25 +0100 Message-ID: References: <1446540176-110181-1-git-send-email-libin.yang@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: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 6C96926044E for ; Tue, 3 Nov 2015 17:49:26 +0100 (CET) In-Reply-To: <1446540176-110181-1-git-send-email-libin.yang@linux.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: 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 Tue, 03 Nov 2015 09:42:54 +0100, libin.yang@linux.intel.com wrote: > > From: Libin Yang > > 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. 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. A bit more explanation is needed. 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 >