devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Michal Simek <michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Cc: Appana Durga Kedareswara Rao
	<appana.durga.rao-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Srikanth Vemula <svemula-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Srikanth Thokala
	<sthokal-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	"dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
	<robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Anirudha Sarangi
	<anirudh-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	"grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
	<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine driver support
Date: Mon, 2 Mar 2015 22:08:52 +0530	[thread overview]
Message-ID: <20150302163852.GA2613@intel.com> (raw)
In-Reply-To: <ad1002303e814d53866349674d22fc11-neA4ZlFjCT0GPAd83OwqBWYJ4DzVTqeXkX/xN29GLwg@public.gmane.org>

On Fri, Feb 20, 2015 at 11:42:31AM +0100, Michal Simek wrote:
> Hi Vinod,
> 
> On 02/20/2015 07:29 AM, Vinod Koul wrote:
> > On Sat, Feb 14, 2015 at 02:21:52PM +0000, Appana Durga Kedareswara Rao wrote:
> >> Hi Vinod,
> >>
> >>
> >>> -----Original Message-----
> >>> From: Vinod Koul [mailto:vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org]
> >>> Sent: Thursday, February 12, 2015 3:05 PM
> >>> To: Appana Durga Kedareswara Rao
> >>> Cc: Arnd Bergmann; linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org;
> >>> devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; Srikanth Vemula; linux-
> >>> kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; Srikanth Thokala; dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org;
> >>> robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org; Michal Simek; Anirudha Sarangi;
> >>> grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org; dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
> >>> 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
> >>>
> >>
> > Please limit you mailer to set wrap at 80 chars, otherwise it becomes
> > unreadable
> > 
> >> 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?
> > Let me ask you a question, what is the relation of xilinx_dma with amba?
> > 
> > If none then only include/linux/ seems to be the right choice. If not then
> > amba maybe okay but you need to provide justfication why it should be in amba?
> 
> I see your point. I think there is real reason to have this header in amba.
> The reason for that was that xilinx_dma.h was added there.
and what would be that?
> 
> Anyway there is include/linux/dma/ folder. Is it ok to move xilinx_dma.h there
> too? The same with this dma one.
Yes that is fine too... As i said this or include/linux should be default
location..

-- 
~Vinod

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-03-02 16:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 12:00 [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine driver support Srikanth Thokala
2014-10-15 12:45 ` Mark Rutland
2014-10-15 13:32   ` Vinod Koul
     [not found]     ` <20141015133248.GQ1638-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
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
     [not found]                 ` <ed439c7a25d0465d9dbf4c06987d42a1-neA4ZlFjCT2qEU4nYqjAjmYJ4DzVTqeXkX/xN29GLwg@public.gmane.org>
2015-02-20  6:29                   ` Vinod Koul
2015-02-20 10:42                     ` Michal Simek
     [not found]                       ` <ad1002303e814d53866349674d22fc11-neA4ZlFjCT0GPAd83OwqBWYJ4DzVTqeXkX/xN29GLwg@public.gmane.org>
2015-03-02 16:38                         ` Vinod Koul [this message]
     [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=20150302163852.GA2613@intel.com \
    --to=vinod.koul-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=anirudh-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=appana.durga.rao-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=sthokal-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=svemula-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).