From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Michael Walle <michael@walle.cc>
Cc: Divya.Koppera@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
hkallweit1@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next] net: phy: micrel: Adding SQI support for lan8814 phy
Date: Fri, 26 Aug 2022 12:43:33 +0200 [thread overview]
Message-ID: <20220826104333.GF2116@pengutronix.de> (raw)
In-Reply-To: <20220826095429.GE2116@pengutronix.de>
On Fri, Aug 26, 2022 at 11:54:29AM +0200, Oleksij Rempel wrote:
> Hi,
>
> On Fri, Aug 26, 2022 at 11:26:12AM +0200, Michael Walle wrote:
> > [+ Oleksij Rempel]
> >
> > Hi,
> >
> > Am 2022-08-26 11:11, schrieb Divya.Koppera@microchip.com:
> > > > > Supports SQI(Signal Quality Index) for lan8814 phy, where it has SQI
> > > > > index of 0-7 values and this indicator can be used for cable integrity
> > > > > diagnostic and investigating other noise sources.
> > > > >
> > > > > Signed-off-by: Divya Koppera <Divya.Koppera@microchip.com>
> >
> > ..
> >
> > > > > +#define LAN8814_DCQ_CTRL_CHANNEL_MASK GENMASK(1,
> > > > 0)
> > > > > +#define LAN8814_DCQ_SQI 0xe4
> > > > > +#define LAN8814_DCQ_SQI_MAX 7
> > > > > +#define LAN8814_DCQ_SQI_VAL_MASK GENMASK(3, 1)
> > > > > +
> > > > > static int lanphy_read_page_reg(struct phy_device *phydev, int page,
> > > > > u32 addr) {
> > > > > int data;
> > > > > @@ -2927,6 +2934,32 @@ static int lan8814_probe(struct phy_device
> > > > *phydev)
> > > > > return 0;
> > > > > }
> > > > >
> > > > > +static int lan8814_get_sqi(struct phy_device *phydev) {
> > > > > + int rc, val;
> > > > > +
> > > > > + val = lanphy_read_page_reg(phydev, 1, LAN8814_DCQ_CTRL);
> > > > > + if (val < 0)
> > > > > + return val;
> > > > > +
> > > > > + val &= ~LAN8814_DCQ_CTRL_CHANNEL_MASK;
> > > >
> > > > I do have a datasheet for this PHY, but it doesn't mention 0xe6 on
> > > > EP1.
> > >
> > > This register values are present in GPHY hard macro as below
> > >
> > > 4.2.225 DCQ Control Register
> > > Index (In Decimal): EP 1.230 Size: 16 bits
> > >
> > > Can you give me the name of the datasheet which you are following, so
> > > that I'll check and let you know the reason.
> >
> > I have the AN4286/DS00004286A ("LAN8804/LAN8814 GPHY Register
> > Definitions"). Maybe there is a newer version of it.
> >
> > >
> > > > So I can only guess that this "channel mask" is for the 4 rx/tx
> > > > pairs on GbE?
> > >
> > > Yes channel mask is for wire pair.
> > >
> > > > And you only seem to evaluate one of them. Is that the correct thing
> > > > to do
> > > > here?
> > > >
> > >
> > > I found in below link is that, get_SQI returns sqi value for 100 base-t1
> > > phy's
> > > https://lore.kernel.org/netdev/20200519075200.24631-2-o.rempel@pengutronix.de/T/
> >
> > That one is for the 100base-t1 which has only one pair.
> >
> > > In lan8814 phy only channel 0 is used for 100base-tx. So returning SQI
> > > value for channel 0.
> >
> > What if the other pairs are bad? Maybe Oleksij has an opinion here.
> >
> > Also 100baseTX (and 10baseT) has two pairs, one for transmitting and one
> > for receiving. I guess you meassure the SQI on the receiving side. So is
> > channel 0 correct here?
> >
> > Again this is the first time I hear about SQI but it puzzles me that
> > it only evaluate one pair in this case. So as a user who reads this
> > SQI might be misleaded.
>
> Wow! I was so possessed with one-pair networks, that forgot to image
> that there is 1000Base-T with more then one pairs :D
>
> Yes, your are right. We wont to have readings from all RX channels and
> be able to export them to the user space. In fact, if i see it
> correctly, the LAN8814_DCQ_CTRL_CHANNEL_MASK value should be synced with
> the MDI-X state. Otherwise we will be reading TX channels.
Just an idea not really related to this patch. It will be coll to be
able to generate diagnostic graphs like this:
Interface | pairs | data | power | SQI | cable | selft
| direction | | | test | test
eth0 ok
0 | RX | NC | 7/7 | ok |
1 | TX | NC | NA | ok |
2 | NC | + 10W | NA | ok |
3 | NC | - | NA | ok |
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-08-26 10:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 8:05 [PATCH net-next] net: phy: micrel: Adding SQI support for lan8814 phy Divya Koppera
2022-08-25 13:19 ` Andrew Lunn
2022-08-26 3:46 ` Divya.Koppera
2022-08-25 21:53 ` Andrew Lunn
2022-08-26 3:50 ` Divya.Koppera
2022-08-26 19:42 ` Andrew Lunn
2022-08-29 5:23 ` Divya.Koppera
2022-08-26 8:42 ` Michael Walle
2022-08-26 9:11 ` Divya.Koppera
2022-08-26 9:26 ` Michael Walle
2022-08-26 9:54 ` Oleksij Rempel
2022-08-26 10:43 ` Oleksij Rempel [this message]
2022-08-26 19:51 ` Andrew Lunn
2022-08-29 5:50 ` Divya.Koppera
2022-08-29 12:30 ` 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=20220826104333.GF2116@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=Divya.Koppera@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).