lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 14 Feb 2015 14:21:52 +0000
From:	Appana Durga Kedareswara Rao <appana.durga.rao@...inx.com>
To:	Vinod Koul <vinod.koul@...el.com>
CC:	Arnd Bergmann <arnd@...db.de>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Srikanth Vemula <svemula@...inx.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Srikanth Thokala" <sthokal@...inx.com>,
	"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
	"robh+dt@...nel.org" <robh+dt@...nel.org>,
	Michal Simek <michals@...inx.com>,
	Anirudha Sarangi <anirudh@...inx.com>,
	"grant.likely@...aro.org" <grant.likely@...aro.org>,
	"dan.j.williams@...el.com" <dan.j.williams@...el.com>
Subject: RE: [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine
 driver support

Hi Vinod,


> -----Original Message-----
> From: Vinod Koul [mailto:vinod.koul@...el.com]
> Sent: Thursday, February 12, 2015 3:05 PM
> To: Appana Durga Kedareswara Rao
> Cc: Arnd Bergmann; linux-arm-kernel@...ts.infradead.org;
> devicetree@...r.kernel.org; Srikanth Vemula; linux-
> kernel@...r.kernel.org; Srikanth Thokala; dmaengine@...r.kernel.org;
> robh+dt@...nel.org; Michal Simek; Anirudha Sarangi;
> grant.likely@...aro.org; dan.j.williams@...el.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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ