devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fred Lefranc <hardware.evs@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Fred Lefranc <hardware.evs@gmail.com>,
	Madalin Bucur <madalin.bucur@nxp.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] net/fsl: fman dt binding: add fsl,max-frm-sz & fsl,rx-extra-headroom properties.
Date: Thu, 17 Feb 2022 17:05:27 +0100	[thread overview]
Message-ID: <20220217160528.2662513-2-hardware.evs@gmail.com> (raw)
In-Reply-To: <20220217160528.2662513-1-hardware.evs@gmail.com>

Describes two additional parameters that could be optionally added
in devicetree.

Signed-off-by: Fred Lefranc <hardware.evs@gmail.com>
---
 .../devicetree/bindings/net/fsl-fman.txt      | 20 +++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/Documentation/devicetree/bindings/net/fsl-fman.txt b/Documentation/devicetree/bindings/net/fsl-fman.txt
index 020337f3c05f..bcd0cf8ca9e9 100644
--- a/Documentation/devicetree/bindings/net/fsl-fman.txt
+++ b/Documentation/devicetree/bindings/net/fsl-fman.txt
@@ -117,6 +117,26 @@ PROPERTIES
 		erratum A050385 which indicates that DMA transactions that are
 		split can result in a FMan lock.
 
+- fsl,max-frm-sz
+		Usage: optional
+		Value type: <u32>
+		Definition: Max frame size, across all interfaces.
+ 		Must be large enough to accommodate the network MTU, but small enough
+ 		to avoid wasting skb memory.
+		1522 by default.
+
+- fsl,rx-extra-headroom
+		Usage: optional
+		Value type: <u32>
+		Definition: Extra headroom for Rx buffers.
+ 		FMan is instructed to allocate, on the Rx path, this amount of
+		space at the beginning of a data buffer, beside the DPA private
+		data area and the IC fields.
+		Does not impact Tx buffer layout.
+		64 by default, it's needed on
+		particular forwarding scenarios that add extra headers to the
+		forwarded frame.
+
 =============================================================================
 FMan MURAM Node
 
-- 
2.25.1


  reply	other threads:[~2022-02-17 16:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 16:05 [PATCH 1/2] net/fsl: fman: Allow fm_max_frame_sz & rx_extra_headroom config from devicetree Fred Lefranc
2022-02-17 16:05 ` Fred Lefranc [this message]
2022-02-18  4:08 ` Jakub Kicinski
2022-02-18  7:23 ` Madalin Bucur
2022-02-18 11:28   ` EVS Hardware Dpt
2022-02-18 11:33     ` Madalin Bucur
2022-02-18 12:28       ` EVS Hardware Dpt
2022-02-25 17:42         ` Rob Herring

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=20220217160528.2662513-2-hardware.evs@gmail.com \
    --to=hardware.evs@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madalin.bucur@nxp.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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).