From: David Miller <davem@davemloft.net>
To: dmurphy@ti.com
Cc: andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
bunk@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
grygorii.strashko@ti.com
Subject: Re: [PATCH net-next v3 0/2] Fix Tx/Rx FIFO depth for DP83867
Date: Mon, 09 Dec 2019 20:19:26 -0800 (PST) [thread overview]
Message-ID: <20191209.201926.728362288698200079.davem@davemloft.net> (raw)
In-Reply-To: <20191209201025.5757-1-dmurphy@ti.com>
From: Dan Murphy <dmurphy@ti.com>
Date: Mon, 9 Dec 2019 14:10:23 -0600
> The DP83867 supports both the RGMII and SGMII modes. The Tx and Rx FIFO depths
> are configurable in these modes but may not applicable for both modes.
>
> When the device is configured for RGMII mode the Tx FIFO depth is applicable
> and for SGMII mode both Tx and Rx FIFO depth settings are applicable. When
> the driver was originally written only the RGMII device was available and there
> were no standard fifo-depth DT properties.
>
> The patchset converts the special ti,fifo-depth property to the standard
> tx-fifo-depth property while still allowing the ti,fifo-depth property to be
> set as to maintain backward compatibility.
>
> In addition to this change the rx-fifo-depth property support was added and only
> written when the device is configured for SGMII mode.
Series applied, thanks.
prev parent reply other threads:[~2019-12-10 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 20:10 [PATCH net-next v3 0/2] Fix Tx/Rx FIFO depth for DP83867 Dan Murphy
2019-12-09 20:10 ` [PATCH net-next v3 1/2] dt-bindings: dp83867: Convert fifo-depth to common fifo-depth and make optional Dan Murphy
2019-12-09 20:10 ` [PATCH net-next v3 2/2] net: phy: dp83867: Add rx-fifo-depth and tx-fifo-depth Dan Murphy
2019-12-10 4:19 ` David Miller [this message]
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=20191209.201926.728362288698200079.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=bunk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=f.fainelli@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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).