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
| ||
|
Date: Thu, 8 Oct 2015 18:01:23 +0200 From: "M'boumba Cedric Madianga" <cedric.madianga@...il.com> To: Arnd Bergmann <arnd@...db.de> Cc: linux-arm-kernel@...ts.infradead.org, mcoquelin.stm32@...il.com, robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com, ijc+devicetree@...lion.org.uk, galak@...eaurora.org, linux@....linux.org.uk, vinod.koul@...el.com, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, dmaengine@...r.kernel.org Subject: Re: [PATCH 1/4] dt-bindings: Document the STM32 DMA bindings Hi Arnd, 2015-10-08 17:43 GMT+02:00 Arnd Bergmann <arnd@...db.de>: > On Thursday 08 October 2015 17:20:09 M'boumba Cedric Madianga wrote: >> +Each dmas request consists of 5 cells: >> +1. A phandle pointing to the STM32 DMA controller >> +2. The channel id >> +3. The request line number >> +4. A 32bit mask specifying the DMA channel configuration >> > > It's fairly unusual to encode the channel id here, rather than > letting the driver pick one. Is that actually required here? Yes it is required as in STM32 platform the channel/request DMA mapping is done by hardware lines. So, if one client wants to use DMA, he has to choose the correct channel/request values according to the DMA mapping of his STM32 platform. > > Arnd BR, Cedric -- 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