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: Wed, 29 Mar 2017 10:07:51 +0200 From: "M'boumba Cedric Madianga" <cedric.madianga@...il.com> To: Rob Herring <robh@...nel.org> Cc: Vinod Koul <vinod.koul@...el.com>, Mark Rutland <mark.rutland@....com>, Maxime Coquelin <mcoquelin.stm32@...il.com>, Alexandre Torgue <alexandre.torgue@...com>, Dan Williams <dan.j.williams@...el.com>, dmaengine@...r.kernel.org, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 1/2] dt-bindings: Document the STM32 MDMA bindings Hi Rob, > stm32 is not a specific SoC. Compatible strings should be specific to > an SoC (with fallback strings to whatever they are compatible with) so > you can handle SoC specific differences or errata. Ok I see. I will add a more specific SoC description in my compatible. Thanks. > I still don't understand. Is the difference in DMA addresses vs. CPU > addresses? If so, you should dma-ranges to translate these. Not really. In fact, the MDMA controller provides a master AXI interface for memories like DDR/SRAM and peripheral registers access (system access port). It also provides a master AHB interface only for Cortex-M7 TCM memory access (TCM access port). So the goal of this st,ahb-addr-masks property is to list all TCM addresses avalaible in the SoC, in order to correctly configure the MDMA as an AHB master in that particular case. For all other cases (other memories or peripheral registers access), the MDMA will act as AXI master. Hope it helps to understand. BR, Cedric
Powered by blists - more mailing lists