From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751119AbbJOECA (ORCPT ); Thu, 15 Oct 2015 00:02:00 -0400 Received: from mga02.intel.com ([134.134.136.20]:47308 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750714AbbJOEB6 (ORCPT ); Thu, 15 Oct 2015 00:01:58 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,684,1437462000"; d="scan'208";a="827294496" Date: Thu, 15 Oct 2015 09:35:01 +0530 From: Vinod Koul To: Shawn Lin Cc: Heiko Stuebner , Jaroslav Kysela , Takashi Iwai , Mark Brown , Lars-Peter Clausen , Doug Anderson , Olof Johansson , Sonny Rao , Addy Ke , Boojin Kim , dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, alsa-devel@alsa-project.org, linux-spi@vger.kernel.org Subject: Re: [PATCH v6 09/10] snd: dmaengine-pcm: add snd_dmaengine_pcm_get_caps interface Message-ID: <20151015040500.GB27370@localhost> References: <1444872865-2169-1-git-send-email-shawn.lin@rock-chips.com> <1444872998-2548-1-git-send-email-shawn.lin@rock-chips.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1444872998-2548-1-git-send-email-shawn.lin@rock-chips.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 15, 2015 at 09:36:38AM +0800, Shawn Lin wrote: > +int snd_dmaengine_pcm_get_caps(struct device *dev, struct dma_slave_caps *caps) > +{ > + struct snd_soc_platform *platform; > + struct dmaengine_pcm *pcm; > + int ret = -ENODEV; > + > + platform = snd_soc_lookup_platform(dev); > + if (!platform) > + return ret; > + > + pcm = soc_platform_to_pcm(platform); > + > + if (pcm->chan) > + ret = dma_get_slave_caps(pcm->chan[0], caps); > + > + return ret; > +} > +EXPORT_SYMBOL_GPL(snd_dmaengine_pcm_get_caps); I don't see the need of this wrapper if you are not going to use this inside common code.. Why not read this in driver, anyway you setting taht up in next patch -- ~Vinod