From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
netdev@vger.kernel.org, Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH V2] net: phy: tja11xx: Add TJA11xx PHY driver
Date: Sat, 15 Dec 2018 18:40:35 +0100 [thread overview]
Message-ID: <20181215174035.GD5922@lunn.ch> (raw)
In-Reply-To: <53643e4a-675a-f5bc-21d6-d0f9b3341f80@gmail.com>
On Sat, Dec 15, 2018 at 09:31:54AM -0800, Florian Fainelli wrote:
> Le 12/15/18 à 9:01 AM, Andrew Lunn a écrit :
> >> +static struct tja11xx_phy_stats tja11xx_hw_stats[] = {
> >> + { "phy_symbol_error_count", 20, 0, 0xffff },
> >> + { "phy_overtemp_error", 21, 1, BIT(1) },
> >> + { "phy_undervolt_error", 21, 3, BIT(3) },
> >> + { "phy_polarity_detect", 25, 6, BIT(6) },
> >> + { "phy_open_detect", 25, 7, BIT(7) },
> >> + { "phy_short_detect", 25, 8, BIT(8) },
> >
> > Hi Marek
> >
> > You have a number of one bit counters here, which is pretty unusual.
> > The names also don't really suggest they are counters.
> >
> > Florian, Heiner, do we want to allow this?
>
> Would it make sense to register HWMON attributes for "overtemp",
> "polarity", "undervolt"?
Hi Florian
I just had a quick look at the datasheet. There does not appear to be
an actual temperature value, nor a voltage value. Can you have a hwmon
device with just alarms?
> The open/short detect sounds like something we should add once we
> finally get to the cable diagnostics support within the netlink
> version of ethtool.
Yes, that sounds better,
Andrew
next prev parent reply other threads:[~2018-12-15 17:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 16:11 [PATCH V2] net: phy: tja11xx: Add TJA11xx PHY driver Marek Vasut
2018-12-15 17:01 ` Andrew Lunn
2018-12-15 17:31 ` Florian Fainelli
2018-12-15 17:40 ` Andrew Lunn [this message]
2018-12-15 17:38 ` Heiner Kallweit
2018-12-21 23:22 ` Marek Vasut
2018-12-22 17:24 ` Heiner Kallweit
2018-12-23 9:12 ` Marek Vasut
2018-12-15 18:01 ` Heiner Kallweit
2018-12-15 18:06 ` Heiner Kallweit
2018-12-15 18:29 ` Marek Vasut
2018-12-15 19:59 ` Andrew Lunn
2018-12-15 20:01 ` Heiner Kallweit
2018-12-21 23:31 ` Marek Vasut
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=20181215174035.GD5922@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=marex@denx.de \
--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).