mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Appana Durga Kedareswara Rao <appana.durga.rao@xilinx.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Srikanth Vemula <svemula@xilinx.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Srikanth Thokala" <sthokal@xilinx.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	Michal Simek <michals@xilinx.com>,
	Anirudha Sarangi <anirudh@xilinx.com>,
	"grant.likely@linaro.org" <grant.likely@linaro.org>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>
Subject: RE: [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine driver support
Date: Sat, 14 Feb 2015 14:21:52 +0000	[thread overview]
Message-ID: <ed439c7a25d0465d9dbf4c06987d42a1@BY2FFO11FD018.protection.gbl> (raw)
In-Reply-To: <20150212093445.GM21387@intel.com>

Hi Vinod,


> -----Original Message-----
> From: Vinod Koul [mailto:vinod.koul@intel.com]
> Sent: Thursday, February 12, 2015 3:05 PM
> To: Appana Durga Kedareswara Rao
> Cc: Arnd Bergmann; linux-arm-kernel@lists.infradead.org;
> devicetree@vger.kernel.org; Srikanth Vemula; linux-
> kernel@vger.kernel.org; Srikanth Thokala; dmaengine@vger.kernel.org;
> robh+dt@kernel.org; Michal Simek; Anirudha Sarangi;
> grant.likely@linaro.org; dan.j.williams@intel.com
> Subject: Re: [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine
> driver support
>
> On Thu, Jan 29, 2015 at 11:24:41AM +0000, Appana Durga Kedareswara Rao
> wrote:
> > >  Earlier in the driver we are embedding dma_slave_config into custom
> > > structs But Lars suggested to modify it. please refer to the below
> > > thread for more details.
> > >  http://www.spinics.net/lists/dmaengine/msg00010.html
> > >
> > >  And later we thought of creating a separate private member in
> > > dma_slave_config for sharing additional configuration between slave
> > > device and dma engine Or a new dma_ctrl_cmd like
> > >
> FSLDMA_EXTERNAL_START(http://www.kernelhub.org/?msg=405535&p=2 )
> > >
> > >  Finally Vinod was ok with the existing suggestion so we dropped the
> > > above thought.
> > >
> > >  @Vinod : Could you please comment on this.
> FSLDMA_EXTERNAL_START has been removed, and you cna use the removal
> as a guidance of how to solve your issue
>

The current VDMA driver that got merged in the open source and the  current patch (dma: xilinx dma v4) Srikanth T submitted both contains the
Similar implementation that you pointed as above(I mean similar to the free scale dma driver).

The discussion starts here is why we need the header file(Xilinx_dma.h) in the include/linux/amba/Xilinx_dma.h  folder.

Like for FSL DMA it is got defined (fsl_dma_external_start) as a function prototype in include/linux/fsldma.h
And it is being getting used in the drivers/misc/carma/carma-fpga-program.c

Similarly in the Xilinx VDMA driver(xilinx_vdma_channel_set_config ) defined as a function prototype in the include/linux/amba/xilinx_dma.h
And is being used by Xilinx videos  drivers.
Those video driver need to use the (xilinx_vdma_channel_set_config) which requires this global header file.

Could you please suggest us whether that header file (Xilinx_dma.h) should be there  in include/linux/amba or we should move it to include/linux?
And any functional comments for this v4 patch?


Regards,
Kedar.

> Thanks
>
> --
> ~Vinod



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


  reply	other threads:[~2015-02-14 14:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 12:00 Srikanth Thokala
2014-10-15 12:45 ` Mark Rutland
2014-10-15 13:32   ` Vinod Koul
2014-10-15 15:00     ` Mark Rutland
2014-10-15 14:34   ` Srikanth Thokala
2014-10-20 19:37 ` Arnd Bergmann
2014-10-21  9:06   ` Appana Durga Kedareswara Rao
2014-10-21  9:14     ` Arnd Bergmann
2014-10-24 12:08       ` Appana Durga Kedareswara Rao
2014-10-24 13:58         ` Arnd Bergmann
2015-01-19 14:08           ` Appana Durga Kedareswara Rao
2015-01-29 11:24           ` Appana Durga Kedareswara Rao
2015-02-12  9:34             ` Vinod Koul
2015-02-14 14:21               ` Appana Durga Kedareswara Rao [this message]
2015-02-20  6:29                 ` Vinod Koul
2015-02-20 10:42                   ` Michal Simek
2015-03-02 16:38                     ` Vinod Koul
     [not found]                   ` <54E70F97.30908@xilinx.com>
2015-03-02  9:04                     ` Appana Durga Kedareswara Rao
2015-02-05 13:31           ` Appana Durga Kedareswara Rao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ed439c7a25d0465d9dbf4c06987d42a1@BY2FFO11FD018.protection.gbl \
    --to=appana.durga.rao@xilinx.com \
    --cc=anirudh@xilinx.com \
    --cc=arnd@arndb.de \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michals@xilinx.com \
    --cc=robh+dt@kernel.org \
    --cc=sthokal@xilinx.com \
    --cc=svemula@xilinx.com \
    --cc=vinod.koul@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®