All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@altera.com>
To: Vince Bridgers <vbridgers2013@gmail.com>
Cc: devicetree@vger.kernel.org, netdev@vger.kernel.org,
	peppe.cavallaro@st.com, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org, rayagond@vayavyalabs.com
Subject: Re: [PATCH net-next v2 1/2] dts: Add a binding for Synopsys emac max-frame-size
Date: Tue, 14 Jan 2014 09:57:36 -0600	[thread overview]
Message-ID: <1389715056.10673.9.camel@linux-builds1> (raw)
In-Reply-To: <1389710409-14106-2-git-send-email-vbridgers2013@gmail.com>

On Tue, 2014-01-14 at 08:40 -0600, Vince Bridgers wrote:
> 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>
> ---
>  Documentation/devicetree/bindings/net/stmmac.txt |    5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/net/stmmac.txt b/Documentation/devicetree/bindings/net/stmmac.txt
> index eba0e5e..26a0ba9 100644
> --- a/Documentation/devicetree/bindings/net/stmmac.txt
> +++ b/Documentation/devicetree/bindings/net/stmmac.txt
> @@ -30,6 +30,10 @@ Required properties:
>  
>  Optional properties:
>  - mac-address: 6 bytes, mac address
> +- snps,max-frame-size:	Maximum frame size permitted. This parameter is useful 

I don't think max-frame-size should be a snps-only binding.

Dinh
> +			since different implementations of the Synopsys MAC may 
> +			have different FIFO sizes depending on the selections
> +			made in Synopsys Core Consultant.


>  
>  Examples:
>  
> @@ -40,5 +44,6 @@ Examples:
>  		interrupts = <24 23>;
>  		interrupt-names = "macirq", "eth_wake_irq";
>  		mac-address = [000000000000]; /* Filled in by U-Boot */
> +		snps,max-frame-size = <3800>;
>  		phy-mode = "gmii";
>  	};

WARNING: multiple messages have this Message-ID (diff)
From: Dinh Nguyen <dinguyen@altera.com>
To: Vince Bridgers <vbridgers2013@gmail.com>
Cc: <devicetree@vger.kernel.org>, <netdev@vger.kernel.org>,
	<peppe.cavallaro@st.com>, <robh+dt@kernel.org>,
	<pawel.moll@arm.com>, <mark.rutland@arm.com>,
	<ijc+devicetree@hellion.org.uk>, <galak@codeaurora.org>,
	<rayagond@vayavyalabs.com>
Subject: Re: [PATCH net-next v2 1/2] dts: Add a binding for Synopsys emac max-frame-size
Date: Tue, 14 Jan 2014 09:57:36 -0600	[thread overview]
Message-ID: <1389715056.10673.9.camel@linux-builds1> (raw)
In-Reply-To: <1389710409-14106-2-git-send-email-vbridgers2013@gmail.com>

On Tue, 2014-01-14 at 08:40 -0600, Vince Bridgers wrote:
> 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>
> ---
>  Documentation/devicetree/bindings/net/stmmac.txt |    5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/net/stmmac.txt b/Documentation/devicetree/bindings/net/stmmac.txt
> index eba0e5e..26a0ba9 100644
> --- a/Documentation/devicetree/bindings/net/stmmac.txt
> +++ b/Documentation/devicetree/bindings/net/stmmac.txt
> @@ -30,6 +30,10 @@ Required properties:
>  
>  Optional properties:
>  - mac-address: 6 bytes, mac address
> +- snps,max-frame-size:	Maximum frame size permitted. This parameter is useful 

I don't think max-frame-size should be a snps-only binding.

Dinh
> +			since different implementations of the Synopsys MAC may 
> +			have different FIFO sizes depending on the selections
> +			made in Synopsys Core Consultant.


>  
>  Examples:
>  
> @@ -40,5 +44,6 @@ Examples:
>  		interrupts = <24 23>;
>  		interrupt-names = "macirq", "eth_wake_irq";
>  		mac-address = [000000000000]; /* Filled in by U-Boot */
> +		snps,max-frame-size = <3800>;
>  		phy-mode = "gmii";
>  	};

  reply	other threads:[~2014-01-14 15:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 14:40 [PATCH net-next v2 0/2] stmmac: fix kernel crashes for jumbo frames Vince Bridgers
2014-01-14 14:40 ` [PATCH net-next v2 1/2] dts: Add a binding for Synopsys emac max-frame-size Vince Bridgers
2014-01-14 15:57   ` Dinh Nguyen [this message]
2014-01-14 15:57     ` Dinh Nguyen
2014-01-14 16:07     ` Florian Fainelli
2014-01-14 16:30       ` Vince Bridgers
2014-01-14 14:40 ` [PATCH net-next v2 2/2] stmmac: Fix kernel crashes for jumbo frames Vince Bridgers
2014-01-14 15:52 ` [PATCH net-next v2 0/2] stmmac: fix " Dinh Nguyen
2014-01-14 15:52   ` Dinh Nguyen

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=1389715056.10673.9.camel@linux-builds1 \
    --to=dinguyen@altera.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=peppe.cavallaro@st.com \
    --cc=rayagond@vayavyalabs.com \
    --cc=robh+dt@kernel.org \
    --cc=vbridgers2013@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.