Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp138324pxb; Thu, 31 Mar 2022 01:25:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy2SIyikB3lrugDK6l1qqAbL+wCk/4duEQI0ErGh72Oo8B9mtwBPor/MJBeNa1bt7x8gek8 X-Received: by 2002:a17:906:2bd7:b0:6ce:698b:7531 with SMTP id n23-20020a1709062bd700b006ce698b7531mr3858582ejg.146.1648715119400; Thu, 31 Mar 2022 01:25:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648715119; cv=none; d=google.com; s=arc-20160816; b=B1XzsWjJNKr6QkJFcvw6sI2AcxVBf069MzmuY5qjzNQnPI8w9hednGfn4GxczmF1Bl rij1veTBqXFfBBi+9uFIAtM4qqocv/IrZNnNVY2c5FkFxHirRZ0b/kN/BgALmdU15glq hoKPmc040iW6WDsvAjE+YzuJuU7nqzXCv01GulQY06xSXR6l04jZcOrbT+pyzmymB8xD 1cS6xTbWnHc3vyx6szaBBOvg7lCu3d6NsFwQ+UO7WoZhkfrGpHN4M7DtL2Vhr4TvJKJ6 DndW97/Be5Ye1gjpNwZ6zf+WIOG8FqAgbtVyM2SFAH8C2b4l75XxIO3a3HZYP3/reR56 9OxA== 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:to:from:cc:in-reply-to:subject:date:dkim-signature; bh=LsQ2rHdZ2Pn2SWmoHtGM/9EAvT94L/VPQneu88cPzwo=; b=kMAK+YTHOf5Bb/FEWlEyBRxs5uKqkmXeEZMNuGDRO1QlRwK/pBH1Jt4gGHyV7ds2bj wnj2PoG3nL/cY9QAUsWZ9Ty37N/PelhU1RxWzxfO6HdUt8KYOOxC3n8nsJfACUUC7+T7 PVeq490wfpkZmjkBvP4OpiqgjFbiD0vDQm2CqIUuba3MRUMk86GIbGezlEEtKyh5ppMh HX5XsQQVWq00+C1pW9P/G6XMhIZS1FaFeiAyC7Qwf/7lOoIwU0kDKXf4usoVbAg0czaS VGCz4o6/SHi8TzTAdd2aB6VlkdRpVO/CdX9QXe9sWnEtJZmmS5eyPi425Zzc+YfxNI+5 9YYw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@dabbelt-com.20210112.gappssmtp.com header.s=20210112 header.b=fhBB4NND; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bj11-20020a170906b04b00b006df76385bdesi21409627ejb.126.2022.03.31.01.24.54; Thu, 31 Mar 2022 01:25:19 -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=@dabbelt-com.20210112.gappssmtp.com header.s=20210112 header.b=fhBB4NND; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230005AbiCaF4h (ORCPT + 99 others); Thu, 31 Mar 2022 01:56:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46334 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229966AbiCaF4f (ORCPT ); Thu, 31 Mar 2022 01:56:35 -0400 Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 72E1D673CD for ; Wed, 30 Mar 2022 22:54:48 -0700 (PDT) Received: by mail-pj1-x1034.google.com with SMTP id jx9so23035520pjb.5 for ; Wed, 30 Mar 2022 22:54:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dabbelt-com.20210112.gappssmtp.com; s=20210112; h=date:subject:in-reply-to:cc:from:to:message-id:mime-version :content-transfer-encoding; bh=LsQ2rHdZ2Pn2SWmoHtGM/9EAvT94L/VPQneu88cPzwo=; b=fhBB4NNDdLmXkeTPANq7lsyDMOfX1/D0yapXetf68Ih585qlMXbjQk4w73YtHMyRA/ y7UIy8BR72on4QPmShIlonIzpPK3aFXq4jOAfItwroot+BWxIIVdbLbjlXJMdvU9vaul KHrXRGClA2Jty1lY1c+R4Lq+cwHfraSVxaBqiIJYVad/MRTYNp1nE3aJ6j2d+eelUNlu lc55fFYROwp6EwpJb0A+jUi9aMxQjAsa1yJGAm4QlrVXgD8nqkqA+znMAtAoAuO29Gky aPF0tGurLWfqxxP7LEiVp3TXDehEdpApwcsKTt38YnfGW2NsR9SJUW/IdAL62n63Ci/X OhCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:subject:in-reply-to:cc:from:to:message-id :mime-version:content-transfer-encoding; bh=LsQ2rHdZ2Pn2SWmoHtGM/9EAvT94L/VPQneu88cPzwo=; b=o5cEwbS1j6rD6jdvNU2qpVTS9Tj8clLcccp6AzIGvYTK7FsP3y6ZfLzRsSUkt325bo ex3CXomseDlSWnhYI6UtHotUYFpOACjTXBtEDBrPH5Gd5Bx/oqdLfrhIGJhuQrmd1gPH 4zbMS58EwonUCJoUY8IvDoS5sHlnA/Ue7IHBBvfnC2JKHIpp9W7sbhHM2koSh1h3FQFl avOGwXu/KZzM0WlojjZXv8X/5gpho2u72kzJuXnDEShY3PmkkbYy/ss6mLwBpDTcaolY tOtC5PyBxAVRu2VI8H96AqzZ1DpAUcRRWV37BL0TX9dyLSqJklSY2UQb8+K1h2oco0LU l81w== X-Gm-Message-State: AOAM533S39lazGnFGw6k6QHXs+28AKQVle3p54N/A9SQe96F1iDMn253 e6wREwiv4JSQ6yBSNT/WonrPZA== X-Received: by 2002:a17:902:8306:b0:14f:a386:6a44 with SMTP id bd6-20020a170902830600b0014fa3866a44mr3661884plb.140.1648706087889; Wed, 30 Mar 2022 22:54:47 -0700 (PDT) Received: from localhost (76-210-143-223.lightspeed.sntcca.sbcglobal.net. [76.210.143.223]) by smtp.gmail.com with ESMTPSA id pc13-20020a17090b3b8d00b001c775679f58sm8661466pjb.37.2022.03.30.22.54.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Mar 2022 22:54:47 -0700 (PDT) Date: Wed, 30 Mar 2022 22:54:47 -0700 (PDT) X-Google-Original-Date: Wed, 30 Mar 2022 22:54:44 PDT (-0700) Subject: Re: [PATCH v8 0/4] Determine the number of DMA channels by 'dma-channels' property In-Reply-To: CC: zong.li@sifive.com, robh+dt@kernel.org, Paul Walmsley , aou@eecs.berkeley.edu, krzysztof.kozlowski@canonical.com, conor.dooley@microchip.com, geert@linux-m68k.org, bin.meng@windriver.com, green.wan@sifive.com, dmaengine@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org From: Palmer Dabbelt To: vkoul@kernel.org Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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 On Wed, 30 Mar 2022 22:21:56 PDT (-0700), vkoul@kernel.org wrote: > On 30-03-22, 20:15, Palmer Dabbelt wrote: >> On Mon, 28 Mar 2022 02:52:21 PDT (-0700), zong.li@sifive.com wrote: >> > The PDMA driver currently assumes there are four channels by default, it >> > might cause the error if there is actually less than four channels. >> > Change that by getting number of channel dynamically from device tree. >> > For backwards-compatible, it uses the default value (i.e. 4) when there >> > is no 'dma-channels' information in dts. >> > >> > This patch set contains the dts and dt-bindings change. >> > >> > Changed in v8: >> > - Rebase on master >> > - Remove modification of microchip-mpfs.dtsi >> > - Rename DMA node name of fu540-c000.dtsi >> > >> > Changed in v7: >> > - Rebase on tag v5.17-rc7 >> > - Modify the subject of patch >> > >> > Changed in v6: >> > - Rebase on tag v5.17-rc6 >> > - Change sf_pdma.chans[] to a flexible array member. >> > >> > Changed in v5: >> > - Rebase on tag v5.17-rc3 >> > - Fix typo in dt-bindings and commit message >> > - Add PDMA versioning scheme for compatible >> > >> > Changed in v4: >> > - Remove cflags of debug use reported-by: kernel test robot >> > >> > Changed in v3: >> > - Fix allocating wrong size >> > - Return error if 'dma-channels' is larger than maximum >> > >> > Changed in v2: >> > - Rebase on tag v5.16 >> > - Use 4 as default value of dma-channels >> > >> > Zong Li (4): >> > dt-bindings: dma-engine: sifive,fu540: Add dma-channels property and >> > modify compatible >> > riscv: dts: Add dma-channels property and modify compatible >> > riscv: dts: rename the node name of dma >> > dmaengine: sf-pdma: Get number of channel by device tree >> > >> > .../bindings/dma/sifive,fu540-c000-pdma.yaml | 19 +++++++++++++-- >> > arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 5 ++-- >> > drivers/dma/sf-pdma/sf-pdma.c | 24 ++++++++++++------- >> > drivers/dma/sf-pdma/sf-pdma.h | 8 ++----- >> > 4 files changed, 38 insertions(+), 18 deletions(-) >> >> Thanks, these are on for-next. > > The drivers/dma/ should go thru dmaengine tree. During merge window I > dont apply the patches OK, I can drop this from my tree if you'd like?