linux-kernel - Porting 3.5 Kernel to a new ARM platform: DMA issues

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>] [day] [month] [year] [list]

Message-ID: <5343AF2A.90809@seletech.com>
Date:	Tue, 08 Apr 2014 10:11:22 +0200
From:	alberto Villa <a.villa@...etech.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Porting 3.5 Kernel to a new ARM platform: DMA issues

Hello,

I'm working to port 3.5 Kernel to a new platform and I'm trying to be
compliant with the new features of newer Kernel versions (I'm familiar
with 2.6). To be more specific I'm trying to adapt the port to the DMA
engine: I've got the DMA driver and the peripheral's driver which use
the DMA engine.
On older Kernel version one could write for example a dma.c under
linux/arch/arm/mach-<arch> to provide dma's specific alloc/release
functions to take care for example of a MUX between peripherals and DMA.
In release 3.5 I found the function dma_filter called during the
dma_request_channel () that seems to provide the functionality I need to
set a MUX for example during the allocation of the DMA channel, but I
can't find any customizable function called during the
dma_release_channel() to change the configuration of the MUX I set
during the dma_request_channel().
Am I missing something or in new releases this kind of operation isn't
supported?

Thank you

-- 
Dr. Villa Alberto
Sw Engineer

SeleTech srl
via Collodi, 8 20052 Monza (MI)
tel: +39 039 5962000
fax: +39 039 9716905
email: a.villa@...etech.com
web: www.seletech.com
     www.seletech.eu 

--
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/