| Message ID | 1389903026-12064-2-git-send-email-vbridgers2013@gmail.com |
|---|---|
| State | Superseded, archived |
| Headers | show |
diff --git a/Documentation/devicetree/bindings/net/stmmac.txt b/Documentation/devicetree/bindings/net/stmmac.txt index eba0e5e..95ddb16 100644 --- a/Documentation/devicetree/bindings/net/stmmac.txt +++ b/Documentation/devicetree/bindings/net/stmmac.txt @@ -29,7 +29,9 @@ Required properties: ignored if force_thresh_dma_mode is set. Optional properties: -- mac-address: 6 bytes, mac address +- mac-address: 6 bytes, mac address +- max-frame-size: Maximum Transfer Unit (IEEE defined MTU), rather + than the maximum frame size. Examples: @@ -40,5 +42,6 @@ Examples: interrupts = <24 23>; interrupt-names = "macirq", "eth_wake_irq"; mac-address = [000000000000]; /* Filled in by U-Boot */ + max-frame-size = <3800>; phy-mode = "gmii"; };
This change adds a parameter for the Synopsys 10/100/1000 stmmac Ethernet driver to configure the maximum frame size supported by the EMAC driver. Synopsys allows the FIFO sizes to be configured when the cores are built for a particular device, but do not provide a way for the driver to read information from the device about the maximum MTU size supported as limited by the device's FIFO size. Signed-off-by: Vince Bridgers <vbridgers2013@gmail.com> --- V5: simplify comment on use of max-frame-size V4: add comments to explain use of max-frame-size with respect to inconsistent definition and use in the ePAPR v1.1 spec V3: change snps,max-frame-size to max-frame-size V2: change snps,max-mtu to snps,max-frame-size --- Documentation/devicetree/bindings/net/stmmac.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)