From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 08B65C433E0 for ; Fri, 12 Jun 2020 01:06:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D5E65206D7 for ; Fri, 12 Jun 2020 01:06:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="mNx6536r" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726441AbgFLBGY (ORCPT ); Thu, 11 Jun 2020 21:06:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45250 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726305AbgFLBGV (ORCPT ); Thu, 11 Jun 2020 21:06:21 -0400 Received: from mail-ej1-x643.google.com (mail-ej1-x643.google.com [IPv6:2a00:1450:4864:20::643]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A043C03E96F; Thu, 11 Jun 2020 18:06:21 -0700 (PDT) Received: by mail-ej1-x643.google.com with SMTP id l27so8431675ejc.1; Thu, 11 Jun 2020 18:06:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xWMqM4EWUTN/tZ1PSJ29RPSc7m9eyjQgLenvkceVjOU=; b=mNx6536r715NBnskOPn1bdL5xCLTV9aec/WpZqRnZrhvWlD+kxiMUC9R+o/sQtOPK1 m2ldqoyMAEgUFiwM2DFUto+MuvVzSYlnys5Gwx99yKzZhRVmtm6FI19U8PDeV+0oKHIf 4qtt5+hz0BWxGpHxFEakWLwDW+m/zs76ThXZ1XMjIyEk5CRBaHHDtzj11Eo3Q3AFYzAl Y/SD6ODdt/SSDEo+kliR/bCL7fe9qra4GEEHjAaxEVAiiqWgp+XJyXHBjWRhUkO2MkzE JyLgiLlc82/T3yfRmqXBMnPXlTzqI0OaJ0WbFqHQMkBBw73fJCszzV0zQsePLAMWCgpS XF0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xWMqM4EWUTN/tZ1PSJ29RPSc7m9eyjQgLenvkceVjOU=; b=ciAPXQXkKHUEDfvDWW39RinX3IgINK8kVvqjqPivlU8EX8AMXi6rSShHzxaIEPUPVS 3ibGQeOlV8+vsJqBloAhUnPekKbstzA0WZZS3PaL09mIuJydyspfgeJeM/xGXo2fgblZ 1X0m5jTYzHgbVWZAmiVEw73CIGnEyTOcvQoWFpvB0UDqchL3myHwPQ7zSiMR8ZTEorAm yu3uxYnVU5L3H+SwUuECqSzLjX4abCvut/qQqKCnleo5WT3LBxkV+SAqriUjih0d7877 eYxBceAAqkZq6Zk2eaov0GwS47aGevKHuZCcqkaBQST+euwgvA1vzw5o3kHghrQU+DS5 RtBA== X-Gm-Message-State: AOAM5332ALMv7PAsuF3uL8ou10QL8t+KE4F1E+dTll/LDaaXInbI7V8v EQJqYrnxng5ja40FaL7wkm0B1OdBHg97Hz3SKow= X-Google-Smtp-Source: ABdhPJyZ5DVMliAOduWmg47LdIrQ4yp92mfh3e85UoCZsPM9fdn/2djYt+DceiV9URZ9A6OY+OcY2ks7Bhv9wyUHhhI= X-Received: by 2002:a17:906:5595:: with SMTP id y21mr11305629ejp.61.1591923979560; Thu, 11 Jun 2020 18:06:19 -0700 (PDT) MIME-Version: 1.0 References: <1591665267-37713-1-git-send-email-sugar.zhang@rock-chips.com> In-Reply-To: <1591665267-37713-1-git-send-email-sugar.zhang@rock-chips.com> From: Peter Geis Date: Thu, 11 Jun 2020 21:06:07 -0400 Message-ID: Subject: Re: [PATCH v2 0/13] Patches to improve transfer efficiency for Rockchip SoCs. To: Sugar Zhang Cc: Vinod Koul , Heiko Stuebner , devicetree@vger.kernel.org, Carlos de Paula , dmaengine@vger.kernel.org, Jonas Karlman , Daniel Lezcano , linux-kernel@vger.kernel.org, "open list:ARM/Rockchip SoC..." , Chen-Yu Tsai , Rob Herring , linux-arm-kernel@lists.infradead.org, Miquel Raynal , Enric Balletbo i Serra , Andy Yan , Johan Jonker , Robin Murphy , Dan Williams , "Leonidas P. Papadakos" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Good Evening, I am currently testing this on the rk3399-rockpro64, and it appears to fully fix the gmac problem without using txpbl. PCIe also seems to be more stable at high load. I need to conduct long term testing, but it seems to be doing very well. Unfortunately it doesn't fix the rk3328 gmac controller. Tested-by: Peter Geis On Mon, Jun 8, 2020 at 9:15 PM Sugar Zhang wrote: > > > > Changes in v2: > - fix FATAL ERROR: Unable to parse input tree > > Sugar Zhang (13): > dmaengine: pl330: Remove the burst limit for quirk 'NO-FLUSHP' > dmaengine: pl330: Add quirk 'arm,pl330-periph-burst' > dt-bindings: dma: pl330: Document the quirk 'arm,pl330-periph-burst' > ARM: dts: rk3036: Add 'arm,pl330-periph-burst' for dmac > ARM: dts: rk322x: Add 'arm,pl330-periph-burst' for dmac > ARM: dts: rk3288: Add 'arm,pl330-periph-burst' for dmac > ARM: dts: rk3xxx: Add 'arm,pl330-periph-burst' for dmac > ARM: dts: rv1108: Add 'arm,pl330-periph-burst' for dmac > arm64: dts: px30: Add 'arm,pl330-periph-burst' for dmac > arm64: dts: rk3308: Add 'arm,pl330-periph-burst' for dmac > arm64: dts: rk3328: Add 'arm,pl330-periph-burst' for dmac > arm64: dts: rk3368: Add 'arm,pl330-periph-burst' for dmac > arm64: dts: rk3399: Add 'arm,pl330-periph-burst' for dmac > > .../devicetree/bindings/dma/arm-pl330.txt | 1 + > arch/arm/boot/dts/rk3036.dtsi | 1 + > arch/arm/boot/dts/rk322x.dtsi | 1 + > arch/arm/boot/dts/rk3288.dtsi | 3 ++ > arch/arm/boot/dts/rk3xxx.dtsi | 3 ++ > arch/arm/boot/dts/rv1108.dtsi | 1 + > arch/arm64/boot/dts/rockchip/px30.dtsi | 1 + > arch/arm64/boot/dts/rockchip/rk3308.dtsi | 2 + > arch/arm64/boot/dts/rockchip/rk3328.dtsi | 1 + > arch/arm64/boot/dts/rockchip/rk3368.dtsi | 2 + > arch/arm64/boot/dts/rockchip/rk3399.dtsi | 2 + > drivers/dma/pl330.c | 44 +++++++++++++++------- > 12 files changed, 49 insertions(+), 13 deletions(-) > > -- > 2.7.4 > > > > > _______________________________________________ > Linux-rockchip mailing list > Linux-rockchip@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-rockchip