From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763155AbdEZEYb (ORCPT ); Fri, 26 May 2017 00:24:31 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:56804 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751924AbdEZEY3 (ORCPT ); Fri, 26 May 2017 00:24:29 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 10FE7611B2 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=architt@codeaurora.org Subject: Re: [PATCH 5/5] drm: dw-hdmi-i2s: add .get_dai_id callback for ALSA SoC To: Kuninori Morimoto , Mark Brown References: <87efvnosnb.wl%kuninori.morimoto.gx@renesas.com> <877f1fosji.wl%kuninori.morimoto.gx@renesas.com> <20170524173849.h7jkmkrwk47pn6kd@sirena.org.uk> <877f1525qq.wl%kuninori.morimoto.gx@renesas.com> <55fd9644-2a71-866c-af51-260abb38c50a@codeaurora.org> Cc: Jose Abreu , Linux-ALSA , Laurent Pinchart , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org, Russell King , Simon From: Archit Taneja Message-ID: Date: Fri, 26 May 2017 09:54:22 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <55fd9644-2a71-866c-af51-260abb38c50a@codeaurora.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/26/2017 09:46 AM, Archit Taneja wrote: > Hi, > > On 05/25/2017 05:04 AM, Kuninori Morimoto wrote: >> >> Hi Mark >> Cc: DRM maintainer >> >>>> ALSA SoC needs to know connected DAI ID for probing. >>>> It is not a big problem if device/driver was only for sound, >>>> but getting DAI ID will be difficult if device includes both >>>> Video/Sound, like HDMI. >>> >>> As far as I understand what's going on with the graph code this seems to >>> make sense to me. How do we want to go about handling the patch? >> >> This is comment to me ? or DRM maintainer ? >> >> If to me, any case (pickup by Mark, or by DRM maintainer) is OK for me > > I'll pick it up for drm-misc-next. Ah, I just saw the dependence on the previous patches. Mark, Please feel free to pull this to the asoc tree. You can add my Ack: Acked-by: Archit Taneja Thanks, Archit > > Thanks, > Archit > >> >> Best regards >> --- >> Kuninori Morimoto >> > -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project