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, 21 Sep 2017 17:29:17 +0200 From: Pierre-Yves MORDRET <pierre-yves.mordret@...com> To: Vinod Koul <vinod.koul@...el.com>, Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, Maxime Coquelin <mcoquelin.stm32@...il.com>, Alexandre Torgue <alexandre.torgue@...com>, Russell King <linux@...linux.org.uk>, Dan Williams <dan.j.williams@...el.com>, "M'boumba Cedric Madianga" <cedric.madianga@...il.com>, Fabrice GASNIER <fabrice.gasnier@...com>, Herbert Xu <herbert@...dor.apana.org.au>, Fabien DESSENNE <fabien.dessenne@...com>, Amelie Delaunay <amelie.delaunay@...com>, Pierre-Yves MORDRET <pierre-yves.mordret@...com>, <dmaengine@...r.kernel.org>, <devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org> Subject: [PATCH v5 0/4] Add STM32 DMAMUX support This patchset adds support for the STM32 DMA multiplexer. It allows to map any peripheral DMA request to any channel of the product DMAs. This IP has been introduced with STM32H7 SoC. --- Version history: v5: * Set selected channel ID within a lock to avoid race condition. Release if any error occurs v4: * Add multi-master ability for STM32 DMAMUX * Get rid of st,dmamux property and custom API between STM32 DMAMUX and DMA. Bindings has changed. DMAMUX will read DMA masters from Device Tree from now on. Merely one DMAMUX node is needed now. * Only STM32 DMA are allowed to be connected onto DMAMUX * channelID is computed locally within the driver and crafted in dma_psec to be passed toward DMA master. DMAMUX router sorts out which DMA master will serve the request automatically. * This version forbids the use of DMA in standalone and DMAMUX at the same time : all clients need to be connected either on DMA or DMAMUX ; no mix up v3: * change compatible to st,stm32h7-dmamux to be mode Soc specific * add verbosity in dma-cells --- Pierre-Yves MORDRET (4): dt-bindings: Document the STM32 DMAMUX bindings dmaengine: Add STM32 DMAMUX driver dt-bindings: stm32-dma: add a property to handle STM32 DMAMUX ARM: configs: stm32: Add DMAMUX support in STM32 defconfig .../devicetree/bindings/dma/stm32-dma.txt | 4 +- .../devicetree/bindings/dma/stm32-dmamux.txt | 84 ++++++ arch/arm/configs/stm32_defconfig | 1 + drivers/dma/Kconfig | 9 + drivers/dma/Makefile | 1 + drivers/dma/stm32-dmamux.c | 327 +++++++++++++++++++++ 6 files changed, 425 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/dma/stm32-dmamux.txt create mode 100644 drivers/dma/stm32-dmamux.c -- 2.7.4
Powered by blists - more mailing lists