From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Parshuram Raju Thombare <pthombar@cadence.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rafal Ciepiela <rafalc@cadence.com>,
Anil Joy Varughese <aniljoy@cadence.com>,
Piotr Sroka <piotrs@cadence.com>
Subject: Re: [PATCH v3 0/5] net: macb: cover letter
Date: Sat, 22 Jun 2019 09:41:37 +0100 [thread overview]
Message-ID: <20190622084137.sdszvzzhs2wbav77@shell.armlinux.org.uk> (raw)
In-Reply-To: <CO2PR07MB2469E07AEBF64DFC8A3E3FAFC1E60@CO2PR07MB2469.namprd07.prod.outlook.com>
On Sat, Jun 22, 2019 at 03:18:42AM +0000, Parshuram Raju Thombare wrote:
> Hi Andrew,
>
> >On Fri, Jun 21, 2019 at 09:33:57AM +0100, Parshuram Thombare wrote:
> >> Hello !
> >>
> >> 2. 0002-net-macb-add-support-for-sgmii-MAC-PHY-interface.patch
> >> This patch add support for SGMII mode.
> >
> >Hi Parshuram
> >
> >What PHYs are using to test this? You mention TI PHY DP83867, but that seems to
> >be a plain old 10/100/1000 RGMII PHY.
> It is DP83867ISRGZ on VCU118 board. This PHY supports SGMII but driver
> dp83867 doesn't seems to support it, that was the reason previous patch
> set has patch trying to configure PHY in SGMII mode from PCI wrapper driver.
There are several versions of the dp83867 phy supporting various
interface modes. It seems the driver has been written for the
DP83867IR and DP83867CR family, presumably TI data sheet SNLS484E.
The DP83867E/IS/CS is covered by a separate data sheet, SNLS504B.
Please note that this PHY does not support 2.5G operation in any
mode.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-06-22 8:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 8:33 [PATCH v3 0/5] net: macb: cover letter Parshuram Thombare
2019-06-21 8:34 ` [PATCH v3 1/5] net: macb: add phylink support Parshuram Thombare
2019-06-21 13:29 ` Russell King - ARM Linux admin
2019-06-21 8:34 ` [PATCH v3 2/5] net: macb: add support for sgmii MAC-PHY interface Parshuram Thombare
2019-06-21 8:52 ` Russell King - ARM Linux admin
2019-06-21 9:03 ` Russell King - ARM Linux admin
2019-06-21 8:34 ` [PATCH v3 3/5] net: macb: add support for c45 PHY Parshuram Thombare
2019-06-21 13:17 ` Andrew Lunn
2019-06-21 8:35 ` [PATCH v3 4/5] net: macb: add support for high speed interface Parshuram Thombare
2019-06-21 8:35 ` [PATCH v3 5/5] net: macb: parameter added to cadence ethernet controller DT binding Parshuram Thombare
2019-06-21 13:16 ` [PATCH v3 0/5] net: macb: cover letter Andrew Lunn
2019-06-22 3:18 ` Parshuram Raju Thombare
2019-06-22 8:41 ` Russell King - ARM Linux admin [this message]
2019-06-22 14:54 ` Andrew Lunn
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=20190622084137.sdszvzzhs2wbav77@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=aniljoy@cadence.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=piotrs@cadence.com \
--cc=pthombar@cadence.com \
--cc=rafalc@cadence.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