| 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
| ||
|
Message-ID: <47CEF8C4B26E8C44B22B028A650E0EA9317A6B8B@DBDE01.ent.ti.com> Date: Fri, 13 Jan 2012 10:40:50 +0000 From: "Gupta, Ajay Kumar" <ajay.gupta@...com> To: "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: RFC: usb: musb: Adding CPPI4.1 DMA driver under drivers/dma Hi, CPPI4.1 (Communication Port Programming Interface) is a TI specific DMA controller used in multiple TI platform such as AM33x, DA8x, AM35x, TI81x. The DMA engine is mainly used by musb controller on above platform. Earlier version of the driver was submitted by Sergei Shtylyov at [1] but was not merged due to disagreement on the location of driver in kernel. Refer the discussions at [1] for more details. [1] http://marc.info/?l=linux-usb&m=125087318308323 The new implementation of the CPPI4.1 DMA slave driver will be in the drivers/dma folder, complying to dmaengine framework. It would involve changes in existing musb driver also for which current plan is to maintain the compatibility of non-CPPI4.1 DMA in musb driver. The task is planned to be spitted into below subtasks. (1) Post RFC on the API details, changes envisaged in musb driver and other challenges (2) Implement and post RFC for the CPPI4.1 DMA driver and changes needed in musb driver. Let me know if you have any thoughts/comments on this. Regards, Ajay -- 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