From patchwork Tue Dec 4 07:24:27 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Chunyan Zhang X-Patchwork-Id: 10711179 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 811231057 for ; Tue, 4 Dec 2018 07:24:42 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 69D3C2B072 for ; Tue, 4 Dec 2018 07:24:42 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 5DDD02B14B; Tue, 4 Dec 2018 07:24:42 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.0 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 477FB2B072 for ; Tue, 4 Dec 2018 07:24:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725988AbeLDHYk (ORCPT ); Tue, 4 Dec 2018 02:24:40 -0500 Received: from mail-pl1-f195.google.com ([209.85.214.195]:41951 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725976AbeLDHYk (ORCPT ); Tue, 4 Dec 2018 02:24:40 -0500 Received: by mail-pl1-f195.google.com with SMTP id u6so7835064plm.8 for ; Mon, 03 Dec 2018 23:24:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=5dwK9Gc1ilATX5PZtGQWTIvlOupWvPV8pyzXonNFRrQ=; b=Ep2qBWhHgvCqDyTB80T3hNTLTnvOkVG7PBahc5Qk72N+Df2qAfE2XbE+XKXXSVKyw6 H7HSn/V/trwoWDd4Nmi+6j0ea5B+pSAdyDWWFK3EDVPsmkwWg3FF2VoBKj5A2J3R/pG+ Q+Zj6CSC95OyvWWLamedhEgFy4lWJ/zBBgQxg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=5dwK9Gc1ilATX5PZtGQWTIvlOupWvPV8pyzXonNFRrQ=; b=rwdS/aFlaGU3lJhEe4CcJLQu0pNxuPIpqt1GUhbFVBdTBRn2zAG5GXdJZZPWdBKJX/ XteI7hMoNpEDmRYTF8QjA7pY/SgrNA3A/vVk9X8DzYNOq2mYVdS1VKeVq4+kEfqlBEg+ 3M2HUSh4MQsQNBQ4+fuT7LWF632vH2Vqj04e23lIdVt3r0OGvh7Yw8PleaQxClErrud/ s9FvlCaqlMXTRs5eka5/A2Cg1gTRJ1tmDO6FdMIheilu/dCB9KACrTuBuAQ6Y0USTHfJ U9aF7laZthSDXnoSpdZnXjVOv4Pejp3WtBiQLzsBGh0l7Skvpa87FJUJonpAjtRh633g CDCA== X-Gm-Message-State: AA+aEWaaDwy0RKP7dtf7ojTrLifu5IbN0l1PhfaCun3zJAwY0xf29e1c LbIsLiO3F5kFQYvbPhb3jGUMUg== X-Google-Smtp-Source: AFSGD/WfXi/ih4hBizPf1FR88wNhObowVHTSdRVYWusq4OVRjcYW9TOWg1rHMAlKWFZ5XbDrnvH1Ew== X-Received: by 2002:a17:902:bf0c:: with SMTP id bi12mr18526341plb.0.1543908279641; Mon, 03 Dec 2018 23:24:39 -0800 (PST) Received: from ubt.spreadtrum.com ([117.18.48.82]) by smtp.gmail.com with ESMTPSA id g136sm22705943pfb.154.2018.12.03.23.24.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 03 Dec 2018 23:24:38 -0800 (PST) From: Chunyan Zhang To: Ulf Hansson , Adrian Hunter , Faiz Abbas Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, Arnd Bergmann , Mark Brown , Kishon Vijay Abraham I , Sekhar Nori , Chunyan Zhang Subject: [PATCH V3 0/3] Add support for using external dma in SDHCI Date: Tue, 4 Dec 2018 15:24:27 +0800 Message-Id: <1543908270-13953-1-git-send-email-zhang.chunyan@linaro.org> X-Mailer: git-send-email 2.7.4 Sender: linux-mmc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-mmc@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Currently the generic SDHCI code in the Linux kernel supports the SD standard DMA integrated into the host controller but does not have any support for external DMA controllers implemented using dmaengine meaning that custom code is needed for any systems that use a generic DMA controller with SDHCI which in practice means any SDHCI controller that doesn't have an integrated DMA controller so we should have this as a generic feature. There are already a number of controller specific drivers that have dmaengine code, and some could use sdhci.c actually, but needed to implement mmc_ops->request() in their specific driver for sending command with external dma using dmaengine framework, with this patchset, them will take advantage of the generic support. TI's omap controller is the case as an example. Any comments are very appreciated. Thanks, Chunyan Changes from v2 (https://lkml.org/lkml/2018/11/12/1936): * Remove CONFIG_EXTERNAL_DMA prompt and help graph; * Add checking for cmd->data; * Select MMC_SDHCI_EXTERNAL_DMA for MMC_SDHCI_OMAP; * Add checking if there's 'dmas' in device tree before decide using external dma. Changes from v1 (https://lkml.org/lkml/2018/11/5/110): (The code on patch 1/3 only was revised) * Address comments from Arnd: - Release channel when failed to request it unconditionally; - Skip warning message if get EPROBE_DEFER; * Address Andrian's comments: - Replace extdma with external_dma; - Add release dma resources in sdhci_cleanup_host() and sdhci_remove_host(); - Release dma resources once dmaengine_submit() failed. - Put rx/tx_chan in struct sdhci_host, and removed unused structure. * Fall back to the DMA/PIO which standard SDHCI supports, if sdhci_external_dma_setup() or sdhci_external_dma_init failed; Chunyan Zhang (3): mmc: sdhci: add support for using external DMA devices mmc: sdhci-omap: Add using external dma dt-bindings: sdhci-omap: Add example for using external dma .../devicetree/bindings/mmc/sdhci-omap.txt | 7 + drivers/mmc/host/Kconfig | 4 + drivers/mmc/host/sdhci-omap.c | 10 ++ drivers/mmc/host/sdhci.c | 185 ++++++++++++++++++++- drivers/mmc/host/sdhci.h | 8 + 5 files changed, 213 insertions(+), 1 deletion(-)