From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bo Shen Subject: Re: [RFC PATCH 08/13] sound: sam9x5_wm8731: machine driver for at91sam9x5 wm8731 boards Date: Mon, 8 Jul 2013 10:01:25 +0800 Message-ID: <51DA1D75.2010503@atmel.com> References: <1372667978-4718-1-git-send-email-richard.genoud@gmail.com> <1372667978-4718-9-git-send-email-richard.genoud@gmail.com> <51D2472B.2010407@atmel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Richard Genoud Cc: devicetree-discuss@lists.ozlabs.org, Nicolas Ferre , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, =?UTF-8?B?VXdlIEtsZWluZS1Lw7ZuaWc=?= List-Id: devicetree@vger.kernel.org Hi Richard, On 7/5/2013 23:15, Richard Genoud wrote: >>> + card->dev = &pdev->dev; >>> >>+ card->owner = THIS_MODULE; >>> >>+ card->dai_link = dai; >>> >>+ card->num_links = 1; >>> >>+ dai->name = "WM8731"; >>> >>+ dai->stream_name = "WM8731 PCM"; >>> >>+ dai->codec_dai_name = "wm8731-hifi"; >>> >>+ dai->init = at91sam9x5ek_wm8731_init; >>> >>+ card->dapm_widgets = at91sam9x5ek_dapm_widgets; >>> >>+ card->num_dapm_widgets = ARRAY_SIZE(at91sam9x5ek_dapm_widgets); >> > >> > >> >Will keep these as snd_soc_card and snd_soc_dai_link structure separately? > I don't really understand what you mean here. > do you mean that something like that will more explicit ? : > + card->dai_link[0].name = "WM8731"; > + card->dai_link[0].stream_name = "WM8731 PCM"; > + card->dai_link[0].codec_dai_name = "wm8731-hifi"; > + card->dai_link[0].init = at91sam9x5ek_wm8731_init; > I mean using structure to define snd_soc_card and snd_soc_dai_link, look like: struct snd_soc_dai_link dai_link_name = { .name = xxx, .stream_name = xxx, ... }; struct snd_soc_card card_name = { .name = xxxx .ower = THIS_MODULE, .dai_link = &dai_link_name, ... }; In this way, I think it will be more clear than put them in code. Best Regards, Bo Shen