linux-kernel - RE: [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine driver support

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:	Fri, 24 Oct 2014 12:08:26 +0000
From:	Appana Durga Kedareswara Rao <appana.durga.rao@...inx.com>
To:	Arnd Bergmann <arnd@...db.de>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
CC:	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"vinod.koul@...el.com" <vinod.koul@...el.com>,
	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 Arnd,

-----Original Message-----
From: Arnd Bergmann [mailto:arnd@...db.de]
Sent: Tuesday, October 21, 2014 2:45 PM
To: linux-arm-kernel@...ts.infradead.org
Cc: Appana Durga Kedareswara Rao; devicetree@...r.kernel.org; vinod.koul@...el.com; 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 Tuesday 21 October 2014 09:06:13 Appana Durga Kedareswara Rao wrote:
> The above mentioned API's  and structures will be used by the dma test
> client driver's to set hardware configuration information. The dma
> client drivers are not mainlined  yet and it is Internally used by
> our git-tree  to test the DMA functionality in loopback .

I would suggest you add the test driver into the main dmaengine driver file directly then, so you don't need to export the symbols. If there are important reasons to keep that as separate files, just move the header to the drivers/dma/ directory and add the test driver there.

        Arnd

Sorry I forgot to mention the below things in the mail .The Config API's and structures not only used by the dmaengine driver's but also used by the  various IP's  (Ex: Ethernet driver and SRIO driver these drivers are under development).For example the Ethernet driver is resides under drivers/net/ethernet but it needs to set some specific configuration parameters of the dma that's why created a separate header file for the h/w configurable parameters.

Regards,
Kedar.

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/