From: Rob Herring <robh@kernel.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] dt-bindings: net: airoha: Add EN7581 memory-region property
Date: Wed, 14 May 2025 15:08:16 -0500 [thread overview]
Message-ID: <20250514200816.GA2934563-robh@kernel.org> (raw)
In-Reply-To: <20250509-airopha-desc-sram-v2-1-9dc3d8076dfb@kernel.org>
On Fri, May 09, 2025 at 04:51:33PM +0200, Lorenzo Bianconi wrote:
> Introduce the memory-region and memory-region-names properties for the
> ethernet node available on EN7581 SoC. In order to improve performances,
> EN7581 SoC supports allocating buffers for hw forwarding queues in SRAM
> instead of DRAM if available on the system.
But 'reserved-memory' is generally for system memory which is DRAM
though we unfortunately don't enforce that. For small onchip SRAM, you
should be using the mmio-sram binding and the 'sram' property.
>
> Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> ---
> .../devicetree/bindings/net/airoha,en7581-eth.yaml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/airoha,en7581-eth.yaml b/Documentation/devicetree/bindings/net/airoha,en7581-eth.yaml
> index 0fdd1126541774acacc783d98e4c089b2d2b85e2..6d22131ac2f9e28390b9e785ce33e8d983eafd0f 100644
> --- a/Documentation/devicetree/bindings/net/airoha,en7581-eth.yaml
> +++ b/Documentation/devicetree/bindings/net/airoha,en7581-eth.yaml
> @@ -57,6 +57,16 @@ properties:
> - const: hsi-mac
> - const: xfp-mac
>
> + memory-region:
> + items:
> + - description: QDMA0 buffer memory
> + - description: QDMA1 buffer memory
> +
> + memory-region-names:
> + items:
> + - const: qdma0-buf
> + - const: qdma1-buf
> +
> "#address-cells":
> const: 1
>
> @@ -140,6 +150,9 @@ examples:
> <GIC_SPI 49 IRQ_TYPE_LEVEL_HIGH>,
> <GIC_SPI 64 IRQ_TYPE_LEVEL_HIGH>;
>
> + memory-region = <&qdma0_buf>, <&qdma1_buf>;
> + memory-region-names = "qdma0-buf", "qdma1-buf";
> +
> airoha,npu = <&npu>;
>
> #address-cells = <1>;
>
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-05-14 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 14:51 [PATCH net-next v2 0/2] Add the capability to allocate hw buffers in SRAM for EN7581 SoC Lorenzo Bianconi
2025-05-09 14:51 ` [PATCH net-next v2 1/2] dt-bindings: net: airoha: Add EN7581 memory-region property Lorenzo Bianconi
2025-05-14 20:08 ` Rob Herring [this message]
2025-05-16 6:28 ` Lorenzo Bianconi
2025-05-21 7:07 ` Lorenzo Bianconi
2025-05-09 14:51 ` [PATCH net-next v2 2/2] net: airoha: Add the capability to allocate hw buffers in SRAM Lorenzo Bianconi
2025-05-12 13:33 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250514200816.GA2934563-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).