From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, Robert Hancock <hancock@sedsystems.ca>
Cc: netdev@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next v2] net: phy: xilinx: add Xilinx PHY driver
Date: Tue, 4 Jun 2019 19:54:23 +0200 [thread overview]
Message-ID: <2a547fef-880e-fe59-ecff-4e616212a0f7@gmail.com> (raw)
In-Reply-To: <20190604165452.GU19627@lunn.ch>
On 04.06.2019 18:54, Andrew Lunn wrote:
>> So it seems like what is missing is the ability of genphy_config_init to
>> detect the bits in the extended status register for 1000Base-X and add
>> the corresponding mode flags. It appears bit 15 for 1000Base-X full
>> duplex is standardized in 802.3 Clause 22, so I would expect Linux
>> should be able to detect that and add it as a supported mode for the
>> PHY. genphy_config_init is dealing with the "legacy" 32-bit mode masks
>> that have no bit for 1000BaseX though.. how is that intended to work?
>
> Hi Robert
>
> I think you are looking at an old genphy_config_init(). The u32 has
> been replaced. Adding:
>
> #define ESTATUS_1000_XFULL 0x8000 /* Can do 1000BX Full */
> #define ESTATUS_1000_XHALF 0x4000 /* Can do 1000BT Half */
>
At least so far phylib knows 1000Base-X/Full only. Not sure whether optical
half duplex modes are used in reality.
Detecting 1000Base-X capability is one thing, how about 1000Base-X
advertisement and link partner capability detection?
If I remember the Marvell specs correctly, there was some bit to switch the
complete register set to fibre mode.
Robert, how is this done for the Xilinx PHY?
> and
>
> if (val & ESTATUS_1000_XFULL)
> linkmode_set_bit(ETHTOOL_LINK_MODE_1000baseX_Full_BIT,
> features);
>
> should not be a problem.
>
> Andrew
>
>
next prev parent reply other threads:[~2019-06-04 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 23:12 [PATCH net-next v2] net: phy: xilinx: add Xilinx PHY driver Robert Hancock
2019-06-03 23:27 ` Jesse Brandeburg
2019-06-04 2:39 ` Florian Fainelli
2019-06-04 5:37 ` Heiner Kallweit
2019-06-04 16:39 ` Robert Hancock
2019-06-04 16:54 ` Andrew Lunn
2019-06-04 17:37 ` Robert Hancock
2019-06-04 17:54 ` Heiner Kallweit [this message]
2019-06-04 18:12 ` 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=2a547fef-880e-fe59-ecff-4e616212a0f7@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hancock@sedsystems.ca \
--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).