From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: "Marek Behún" <kabel@kernel.org>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Jakub Kicinski <kuba@kernel.org>,
davem@davemloft.net, pali@kernel.org
Subject: Re: [PATCH net-next v5 1/5] net: sfp: add SFP_PASSWORD address
Date: Thu, 14 Jan 2021 14:59:53 +0000 [thread overview]
Message-ID: <20210114145953.GS1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20210114044331.5073-2-kabel@kernel.org>
On Thu, Jan 14, 2021 at 05:43:27AM +0100, Marek Behún wrote:
> Add SFP_PASSWORD = 0x7b to the diagnostics enumerator. This address is
> described in SFF-8436 and SFF-8636.
However, as I mentioned previously, these are not relevant for SFPs,
but are for QSFPs, and QSFPs have a totally different layout.
The data structure for this enum is described by SFF-8472, and it lists
Vendor Specific Locations [Address A2h, Bytes 120-126]
This is what the SFP_VSL definition covers.
SFF-8436 defines the layout for "QSFP+ 10 Gbs 4X PLUGGABLE TRANSCEIVER":
Table 17 - Lower Memory Map (A0h)
Address Description Type Passive Copper, Optical
Active Copper, Module Active Optical
0 Identifier (1 Read-Only R R
Byte)
1-2 Status (2 Bytes) Read-Only See Table 18
3-21 Interrupt Flags Read-Only See Tables 19-21
(19 Bytes)
...
123-126 Password Entry Read/Write O O
Area (optional) 4
Bytes
127 Page Select Byte Read/Write R R
So, SFF-8436 is not relevant - not only is it for a different address
but the whole format is different.
SFF-8636 is "Specification for Management Interface for Cabled
Environments" and defines:
2-Wire Serial Address 1010000x
Lower Page 00h
0 Identifier
1- 2 Status
3- 21 Interrupt Flags
...
123-126 Password Entry Area (Optional)
127 Page Select Byte
So again, SFF-8636 is not relevant for the same reasons as SFF-8436.
We're left with SFF-8472, which mentions no password entry area, but
leaves the area from 120-127 open as "vendor specific", so I don't
think it is appropriate to start adding vendor specific definitions as
if they were generic to sfp.h
I would instead suggest defining this inside mdio-i2c.c as
#define ROLLERBALL_PASSWORD (SFP_VSL + 3)
rather than trying to make this appear generic.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-01-14 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 4:43 [PATCH net-next v5 0/5] Support for RollBall 10G copper SFP modules Marek Behún
2021-01-14 4:43 ` [PATCH net-next v5 1/5] net: sfp: add SFP_PASSWORD address Marek Behún
2021-01-14 14:59 ` Russell King - ARM Linux admin [this message]
2021-01-14 4:43 ` [PATCH net-next v5 2/5] net: phy: mdio-i2c: support I2C MDIO protocol for RollBall SFP modules Marek Behún
2021-01-14 4:43 ` [PATCH net-next v5 3/5] net: phylink: allow attaching phy for SFP modules on 802.3z mode Marek Behún
2021-01-14 4:43 ` [PATCH net-next v5 4/5] net: sfp: create/destroy I2C mdiobus before PHY probe/after PHY release Marek Behún
2021-01-14 16:07 ` Russell King - ARM Linux admin
2021-01-18 9:38 ` Pali Rohár
2021-01-18 11:42 ` Marek Behún
2021-01-14 4:43 ` [PATCH net-next v5 5/5] net: sfp: add support for multigig RollBall transceivers Marek Behún
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=20210114145953.GS1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kabel@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pali@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 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.