Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4559302imw; Tue, 19 Jul 2022 08:49:46 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vvglJf6vGAcnF+jZOyLaGCT7mTtTfq1IuYxFdCfVPo2C8LHkSRmWHDKhXrJ0BSiE6a7rGG X-Received: by 2002:a05:6402:248f:b0:43a:b89c:20e3 with SMTP id q15-20020a056402248f00b0043ab89c20e3mr45042365eda.335.1658245786101; Tue, 19 Jul 2022 08:49:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658245786; cv=none; d=google.com; s=arc-20160816; b=XoN39QjtNKTMs5UtXG9cgE6TZ+sBHdH/gzncPRLRUnNUzQdOysyCrt8sQR0UEfTQo3 YqwwWQDdfDf0uyoOZ755aSsnFwOsDqyTIdH9srjYtzF29h2q1XnrS2eKO9BrI6Lp+C3X cpAGmiT7wtB3zDfLTRKoJ/jrbD+PrUCwT+R5qmsfVTf9MqRlShyclIuFGGjhtZ7P+m1g HqgP/48Jk54ie55wj+0hKQK0uS/LWXKg/XIlwQMfxbB5OH3QO6Fg9CNvASjq7ILBSt5u AMYEBD0SuFQ523tHhsasWbRmDJCDXYTnMSoMclRgtcf1Www/vpwS8h5+n0zt+KpWugHB VJ9A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=1ralePF7NZgiuaaEZtba9R7/B4WF8Zv4f9q+QOtg1so=; b=W6suAX9ShCvpyoO17y81qd+Ve7sc++T+of107e9J7rX+BxTj3IuyuePE4CXshGQBAA hyhT0w9sljG5meclt2AGwWyZrNqPcXM0cn5aTMQQrPrKmwoX3Pw+rsQd5ASbju4ECT8Y LoShnGBOf+SshAJqK70go67OfMvYE/p0/XHdvh2+1hx982QiBgK2fudmT+mKdnNCDfAK IcTU6azIjAdnXqCKqcGaSDZpFMOApXyZe2FrctTXswgEmF7uaf8CJ/KiyKMG8ptNTD8d hTE2ocmxAKLBlkAvMZpRhCbfMjcEF5DVfX4gH4JVTCj7m6qJRwj7mQRToWfKcLis8cvd KzRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@foss.st.com header.s=selector1 header.b=p7alzx8A; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=foss.st.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g8-20020a056402090800b004359f471717si26216649edz.0.2022.07.19.08.49.20; Tue, 19 Jul 2022 08:49:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@foss.st.com header.s=selector1 header.b=p7alzx8A; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=foss.st.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238648AbiGSPsO (ORCPT + 99 others); Tue, 19 Jul 2022 11:48:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50162 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238540AbiGSPsN (ORCPT ); Tue, 19 Jul 2022 11:48:13 -0400 Received: from mx07-00178001.pphosted.com (mx07-00178001.pphosted.com [185.132.182.106]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2B22359243; Tue, 19 Jul 2022 08:48:12 -0700 (PDT) Received: from pps.filterd (m0241204.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 26JFMe81030928; Tue, 19 Jul 2022 17:47:57 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h=from : to : cc : subject : date : message-id : mime-version : content-transfer-encoding : content-type; s=selector1; bh=1ralePF7NZgiuaaEZtba9R7/B4WF8Zv4f9q+QOtg1so=; b=p7alzx8ATWRqHMwq63kuR9a7iTHwgoLPGSyYr/j6JOqf3T7JZp8iWZjk+9QllAyd9BBz FEzw4TEgLdlMiaQHCRhyF/E84Ah9dWUUrBLv7J4btdwhn18XecS3TsfRAtQE7dLEHZ/l 72RVw+SNfrJZT5w8nKZvVY4M5WEQoH/PN33cLE9f1nuExvZUFkFmlcUKsXc/VwYrgFdb eraf0txmD1oyGN04Cf07wh4ruPAli40xs8XJiTTVC1LWegYoBwPST4KWyV6h1/20G0cP 3f/eadgF7+VvnPLT+h0uQo01wJMI4s7dXoYG5oadsMY2ivcNSQfyiJtpry7Sj3cpfEmu Ig== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com (PPS) with ESMTPS id 3hbnhy0prh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Jul 2022 17:47:57 +0200 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 03F95100034; Tue, 19 Jul 2022 17:47:57 +0200 (CEST) Received: from Webmail-eu.st.com (shfdag1node2.st.com [10.75.129.70]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id F2FC222D17C; Tue, 19 Jul 2022 17:47:56 +0200 (CEST) Received: from localhost (10.75.127.48) by SHFDAG1NODE2.st.com (10.75.129.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2308.20; Tue, 19 Jul 2022 17:47:56 +0200 From: Amelie Delaunay To: Jonathan Corbet , Vinod Koul , Maxime Coquelin , Alexandre Torgue CC: , , , , , Marek Vasut , Amelie Delaunay Subject: [PATCH v3 0/6] STM32 DMA-MDMA chaining feature Date: Tue, 19 Jul 2022 17:47:39 +0200 Message-ID: <20220719154745.623204-1-amelie.delaunay@foss.st.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.75.127.48] X-ClientProxiedBy: SFHDAG2NODE3.st.com (10.75.127.6) To SHFDAG1NODE2.st.com (10.75.129.70) X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.883,Hydra:6.0.517,FMLib:17.11.122.1 definitions=2022-07-19_04,2022-07-19_01,2022-06-22_01 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patchset (re)introduces STM32 DMA-MDMA chaining feature. As the DMA is not able to generate convenient burst transfer on the DDR, it penalises the AXI bus when accessing the DDR. While it accesses optimally the SRAM. The DMA-MDMA chaining then consists in having an SRAM buffer between DMA and MDMA, so the DMA deals with peripheral and SRAM, and the MDMA with SRAM and DDR. The feature relies on the fact that DMA channel Transfer Complete signal can trigger a MDMA channel transfer and MDMA can clear the DMA request by writing to DMA Interrupt Clear register. A deeper introduction can be found in patch 1. Previous implementation [1] has been dropped as nacked. Unlike this previous implementation (where all the stuff was embedded in stm32-dma driver), the user (in peripheral drivers using dma) has now to configure the MDMA channel. [1] https://lore.kernel.org/lkml/1538139715-24406-1-git-send-email-pierre-yves.mordret@st.com/ Changes in v3: - introduce two prior patches to help readibility - fix stm32-dma struct stm32_dma_mdma_config documentation Changes in v2: - wrap to 80-column limit for documentation - add an entry for this documentation in index.rst - use simple table instead of csv-table in documentation Amelie Delaunay (6): dmaengine: stm32-dma: introduce 3 helpers to address channel flags dmaengine: stm32-dma: use bitfield helpers docs: arm: stm32: introduce STM32 DMA-MDMA chaining feature dmaengine: stm32-dmamux: set dmamux channel id in dma features bitfield dmaengine: stm32-dma: add support to trigger STM32 MDMA dmaengine: stm32-mdma: add support to be triggered by STM32 DMA Documentation/arm/index.rst | 1 + .../arm/stm32/stm32-dma-mdma-chaining.rst | 415 ++++++++++++++++++ drivers/dma/stm32-dma.c | 136 +++--- drivers/dma/stm32-dmamux.c | 2 +- drivers/dma/stm32-mdma.c | 70 ++- 5 files changed, 569 insertions(+), 55 deletions(-) create mode 100644 Documentation/arm/stm32/stm32-dma-mdma-chaining.rst -- 2.25.1