From: Jyri Sarha Subject: Re: [PATCH RFC 3/8] ASoC: davinci-mcasp: Get DMA related properties from DT Date: Thu, 12 Sep 2013 15:10:12 +0300 Message-ID: <49bf24974af0ff34d2be7db97e04f2a9@kapsi.fi> References: <35b6dc24d8a803b97c683d4d2c51db7e3518f7ff.1378738436.git.jsarha@ti.com> <20130909152559.GM29403@sirena.org.uk> <20130912110800.GI29403@sirena.org.uk> <62c9342f91e99fa5d421a7ad29fbf354@kapsi.fi> <20130912115626.GO29403@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail.kapsi.fi (mail.kapsi.fi [217.30.184.167]) by alsa0.perex.cz (Postfix) with ESMTP id 100822654B1 for ; Thu, 12 Sep 2013 14:10:15 +0200 (CEST) In-Reply-To: <20130912115626.GO29403@sirena.org.uk> 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: Mark Brown Cc: Darren Etheridge , alsa-devel@alsa-project.org, Joel Fernandes , Jyri Sarha , "Hebbar, Gururaja" , liam.r.girdwood@linux.intel.com List-Id: alsa-devel@alsa-project.org On 2013-09-12 14:56, Mark Brown wrote: > On Thu, Sep 12, 2013 at 02:34:13PM +0300, Jyri Sarha wrote: > > The bottom line of my suggestion is only to add the dma register > location > to reg-property, since that info is needed in the mcasp node also in > the > future dmaengine_pcm-implementation. > > What exactly is the dma register location here - what hardware is being > controlled? They is the McASP-bus receive/transmit buffer data port addresses. So those are McASP entity specific properties that need to be passed to DMA-engine.