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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 24A04CFC5EC for ; Thu, 10 Oct 2024 18:24:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=+aWpTGr32bp7DHCKTgu6tO8vIi4AU2Bnss842/YylYc=; b=YQVjiSlwjcdSLqyB0YbijKdWL8 qDWm27shukolr4UomHzxvgpdidfqwtwraDYPJOn5ARoutn9ux+uhI1MACX9Bd25qLCGburuV8JL8e OhJSWkX6nRpPvBiQy6hfQ1R2UxQAtIGeKalT54IlBlDjt841HgC1DGmDwjEH+q3rkAZ2JoWVJDqoL TSFrWX3v0tr6hfugJZpnTJGYM8VQg/Rf0zoowgvrWja5QIV6hbykQictExE5mvDeiGIzXZbiOodCe +AlOA2iFl7V75h5qzJ5uOLTykzpzTX2jz8oS24yLPdMmkdRoVlLgLDOr/CYsXIrmRNdJHvTm9KLGP nDE5jnrA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1syxpg-0000000DpUW-2F1J; Thu, 10 Oct 2024 18:24:16 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1syxiS-0000000Do82-3P0V for linux-arm-kernel@lists.infradead.org; Thu, 10 Oct 2024 18:16:52 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id CA3B25C59C8; Thu, 10 Oct 2024 18:16:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8424CC4CEC5; Thu, 10 Oct 2024 18:16:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1728584207; bh=xPm3PVW2xYEBnBhwN7Jk99JqhG0NN+6Z1eKHd0Tobmg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tr0HYA5P2vYjIUDOUUHyBLgzLQ1gkXFeLRYVluR6DGw91nprWgbXC1DJvQkEBaV84 vcLFsUzxvgenW8U18YWY4HkKah/7osO6XgaGqFv1eLfIBa9TkQNeXiQDGlRM73qtMt +lPyDCn1sUr+2qwpjeE9Gb/MjsPEe/jifyiZCkkkcByl6pZTdFNv12hT+37TC15iTb VWDidTouIS9qWl25HjBYOA5h6gRl7TxWAO8mpoSFl8HgaWoNK0JK3IXu99e2QQiZnl JR4rgf7wR9JeXCFi580jcPyY5MTNVBCfvjBJjrNkY8OcRsUBuT4fHVOziEMXXwNMpJ 8/8XNQZZWYuzA== Date: Thu, 10 Oct 2024 13:16:45 -0500 From: Rob Herring To: Amelie Delaunay Cc: Vinod Koul , Krzysztof Kozlowski , Conor Dooley , Maxime Coquelin , Alexandre Torgue , dmaengine@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 06/11] dt-bindings: dma: stm32-dma3: introduce st,axi-max-burst-len property Message-ID: <20241010181645.GA2121939-robh@kernel.org> References: <20241010-dma3-mp25-updates-v1-0-adf0633981ea@foss.st.com> <20241010-dma3-mp25-updates-v1-6-adf0633981ea@foss.st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20241010-dma3-mp25-updates-v1-6-adf0633981ea@foss.st.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241010_111648_958155_5CC75912 X-CRM114-Status: GOOD ( 19.02 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Oct 10, 2024 at 04:27:56PM +0200, Amelie Delaunay wrote: > DMA3 maximum burst length (in unit of beat) may be restricted depending > on bus interconnect. > > As mentionned in STM32MP2 reference manual [1], "the maximum allowed AXI > burst length is 16. The user must set [S|D]BL_1 lower or equal to 15 > if the Source/Destination allocated port is AXI (if [S|D]AP=0)". This should be implied by the SoC specific compatible. > > Introduce st,axi-max-burst-len. If used, it will clamp the burst length > to that value if AXI port is used, if not, the maximum burst length value > supported by DMA3 is used. > > [1] https://www.st.com/resource/en/reference_manual/rm0457-stm32mp2325xx-advanced-armbased-3264bit-mpus-stmicroelectronics.pdf > > Signed-off-by: Amelie Delaunay > --- > .../devicetree/bindings/dma/stm32/st,stm32-dma3.yaml | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/Documentation/devicetree/bindings/dma/stm32/st,stm32-dma3.yaml b/Documentation/devicetree/bindings/dma/stm32/st,stm32-dma3.yaml > index 38c30271f732e0c8da48199a224a88bb647eeca7..90ad70bb24eb790afe72bf2085478fa4cec60b94 100644 > --- a/Documentation/devicetree/bindings/dma/stm32/st,stm32-dma3.yaml > +++ b/Documentation/devicetree/bindings/dma/stm32/st,stm32-dma3.yaml > @@ -51,6 +51,16 @@ properties: > power-domains: > maxItems: 1 > > + st,axi-max-burst-len: > + description: | > + Restrict AXI burst length in unit of beat by value specified in this property. > + The value specified in this property is clamped to the maximum burst length supported by DMA3. > + If this property is missing, the maximum burst length supported by DMA3 is used. > + $ref: /schemas/types.yaml#/definitions/uint32 > + minimum: 1 > + maximum: 256 > + default: 64 > + > "#dma-cells": > const: 3 > description: | > @@ -137,5 +147,6 @@ examples: > ; > clocks = <&rcc CK_BUS_HPDMA1>; > #dma-cells = <3>; > + st,axi-max-burst-len = <16>; > }; > ... > > -- > 2.25.1 >