Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933057AbdHVOjY (ORCPT ); Tue, 22 Aug 2017 10:39:24 -0400 Received: from regular1.263xmail.com ([211.150.99.138]:51982 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932608AbdHVOjX (ORCPT ); Tue, 22 Aug 2017 10:39:23 -0400 X-263anti-spam: KSV:0;BIG:0; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ADDR-CHECKED4: 1 X-ABS-CHECKED: 1 X-SKE-CHECKED: 1 X-ANTISPAM-LEVEL: 2 X-RL-SENDER: jeffy.chen@rock-chips.com X-FST-TO: tiwai@suse.de X-SENDER-IP: 103.29.142.67 X-LOGIN-NAME: jeffy.chen@rock-chips.com X-UNIQUE-TAG: <71bbd1eb28d27a652c7c62973220e238> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Message-ID: <599C420A.80601@rock-chips.com> Date: Tue, 22 Aug 2017 22:39:06 +0800 From: jeffy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20130126 Thunderbird/19.0 MIME-Version: 1.0 To: Takashi Iwai , Mark Brown CC: Donglin Peng , alsa-devel@alsa-project.org, briannorris@chromium.org, dgreid@chromium.org, dianders@chromium.org, mka@chromium.org, Liam Girdwood , mengdong.lin@linux.intel.com, lars@metafoo.de, Jaroslav Kysela , =?UTF-8?B?SGVpa28gU3TDvGJuZXI=?= , linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 2/9] ASoC: soc-core: Allow searching dai driver name in snd_soc_find_dai References: <20170822075729.8438-1-jeffy.chen@rock-chips.com> <20170822075729.8438-3-jeffy.chen@rock-chips.com> <20170822140255.t2wfwkjr67v3eoxu@sirena.org.uk> <20170822142111.zlosryhkyi75htod@sirena.org.uk> In-Reply-To: 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 Content-Length: 773 Lines: 28 Hi guys, On 08/22/2017 10:26 PM, Takashi Iwai wrote: > On Tue, 22 Aug 2017 16:21:11 +0200, > Mark Brown wrote: >> >> On Tue, Aug 22, 2017 at 10:15:32PM +0800, Donglin Peng wrote: >>> On Tue, Aug 22, 2017 at 10:02 PM, Mark Brown wrote: >> >>>> We should be already verifying that drivers have a name, we assume one >>>> elsewhere. >> >>> But I can't find any codes that set or check dai_driver->name in >>> function snd_soc_register_codec or snd_soc_register_component. >> >> We should fix that then. > > Hmm, as far as I read the code, the NULL dai driver name is valid for > a single component. The dai name is determined by fmt_single_name(). > > > Takashi > > sorry, i though that is checked too... new patch is coming, thanks for noticing :) >