From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Joao Pinto" <Joao.Pinto@synopsys.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [RFC net-next] net: phy: Add basic support for Synopsys XPCS using a PHY driver
Date: Mon, 13 Jan 2020 15:05:46 +0000 [thread overview]
Message-ID: <BN8PR12MB32660970D0294CCEE7B16B53D3350@BN8PR12MB3266.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CA+h21hpsauapCGEHqVqHpEU2K-VsAh3vKBRJ_N8iq2i35SedOw@mail.gmail.com>
From: Vladimir Oltean <olteanv@gmail.com>
Date: Jan/13/2020, 14:55:51 (UTC+00:00)
> Clauses 72 and 73 describe some PMD link training procedure too, as
> part of auto-negotiation for 10GBase-KR. Does the XGPCS do any of
> that? Is this series sufficient for link training to work when in the
> 10GBase-KR copper backplane link mode?
Yes, its supported by the IP but not in the patch. It's working fine
without the link training procedure. Actually, Clause 72 Link training is
optional in the IP, and in the configuration I have now it's not enabled
so even if I implemented it I would need a new HW to test it.
---
Thanks,
Jose Miguel Abreu
next prev parent reply other threads:[~2020-01-13 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 13:11 [RFC net-next] net: phy: Add basic support for Synopsys XPCS using a PHY driver Jose Abreu
2020-01-13 13:38 ` Andrew Lunn
2020-01-13 13:54 ` Jose Abreu
2020-01-13 14:18 ` Russell King - ARM Linux admin
2020-01-13 14:27 ` Jose Abreu
2020-01-13 14:55 ` Vladimir Oltean
2020-01-13 15:05 ` Jose Abreu [this message]
2020-01-13 14:50 ` Vladimir Oltean
2020-01-13 15:09 ` Russell King - ARM Linux admin
2020-01-20 10:31 ` Jose Abreu
2020-01-20 10:50 ` Russell King - ARM Linux admin
2020-01-20 11:07 ` Jose Abreu
2020-01-20 11:39 ` Russell King - ARM Linux admin
[not found] ` <e942b414-08bd-0305-9128-26666a7a5d5a@linux.intel.com>
2020-02-04 9:41 ` Chng, Jack Ping
2020-03-09 9:22 ` Jose Abreu
2020-01-13 13:42 ` [RFC " Andy Shevchenko
2020-01-13 14:07 ` Jose Abreu
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=BN8PR12MB32660970D0294CCEE7B16B53D3350@BN8PR12MB3266.namprd12.prod.outlook.com \
--to=jose.abreu@synopsys.com \
--cc=Joao.Pinto@synopsys.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@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 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).