From: David Miller <davem@davemloft.net>
To: andrew@lunn.ch
Cc: netdev@vger.kernel.org, vivien.didelot@savoirfairelinux.com
Subject: Re: [PATCH v2 0/2] net: dsa: Move temperature sensor code into PHY.
Date: Fri, 20 Jan 2017 14:43:25 -0500 (EST) [thread overview]
Message-ID: <20170120.144325.630722726670636677.davem@davemloft.net> (raw)
In-Reply-To: <1484872670-32585-1-git-send-email-andrew@lunn.ch>
From: Andrew Lunn <andrew@lunn.ch>
Date: Fri, 20 Jan 2017 01:37:48 +0100
> Marvell Ethernet switches contain a temperature sensor. There appears
> to be one sensor, which is shared by each of the internal PHYs. Each
> PHY has independent registers to read this sensor, and to set a limit
> for when an alarm should be raised.
>
> Some Marvell discrete PHY also have the same sensor and registers.
> Moving the HWMON code from DSA into the PHY makes the sensor available
> in discrete PHYs, and removes the layering violation, the switch
> driver poking around in PHY registers.
>
> While moving the code into the PHY driver, it has been re-written to
> use the new HWMON APIs.
>
> v2:
>
> Better Cover note explaining one sensor, but multiple independent
> registers
>
> Simply error checking.
I know there was minor request for a respin, but I'm not going to hold
this up any more just for that.
Series applied, thanks Andrew.
prev parent reply other threads:[~2017-01-20 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 0:37 [PATCH v2 0/2] net: dsa: Move temperature sensor code into PHY Andrew Lunn
2017-01-20 0:37 ` [PATCH v2 1/2] phy: marvell: Add support for temperature sensor Andrew Lunn
2017-01-20 0:37 ` [PATCH v2 2/2] net: dsa: Remove hwmon support Andrew Lunn
2017-01-20 0:43 ` [PATCH v2 0/2] net: dsa: Move temperature sensor code into PHY Andrew Lunn
2017-01-20 3:26 ` Vivien Didelot
2017-01-20 19:43 ` David Miller [this message]
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=20170120.144325.630722726670636677.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).