From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Baruch Siach <baruch@tkos.co.il>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH net v3 2/2] net: phy: marvell10g: hwmon support for 2110
Date: Thu, 23 Apr 2020 14:39:36 +0100 [thread overview]
Message-ID: <20200423133936.GS25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <f97e4690b4ec92598b3514f05e32dc26f37044ac.1587618482.git.baruch@tkos.co.il>
On Thu, Apr 23, 2020 at 08:08:02AM +0300, Baruch Siach wrote:
> Read the temperature sensor register from the correct location for the
> 88E2110 PHY. There is no enable/disable bit, so leave
> mv3310_hwmon_config() for 88X3310 only.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> v3: Split temperature register read routine per variant (Andrew Lunn)
>
> v2: Fix indentation (Andrew Lunn)
> ---
> drivers/net/phy/marvell10g.c | 25 +++++++++++++++++++++++--
> 1 file changed, 23 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/phy/marvell10g.c b/drivers/net/phy/marvell10g.c
> index 69530a84450f..e14b9c2e5efe 100644
> --- a/drivers/net/phy/marvell10g.c
> +++ b/drivers/net/phy/marvell10g.c
> @@ -66,6 +66,8 @@ enum {
> MV_PCS_CSSR1_SPD2_2500 = 0x0004,
> MV_PCS_CSSR1_SPD2_10000 = 0x0000,
>
> + MV_PCS_TEMP = 0x8042,
Please add a comment mentioning that this is for the 88E2110, and
it would probably be a good idea to document the MV_V2_TEMP definition
as 88X3310 specific as well.
> +
> /* These registers appear at 0x800X and 0xa00X - the 0xa00X control
> * registers appear to set themselves to the 0x800X when AN is
> * restarted, but status registers appear readable from either.
> @@ -104,6 +106,24 @@ static umode_t mv3310_hwmon_is_visible(const void *data,
> return 0;
> }
>
> +static int mv3310_hwmon_read_temp_reg(struct phy_device *phydev)
> +{
> + return phy_read_mmd(phydev, MDIO_MMD_VEND2, MV_V2_TEMP);
> +}
> +
> +static int mv2110_hwmon_read_temp_reg(struct phy_device *phydev)
> +{
> + return phy_read_mmd(phydev, MDIO_MMD_PCS, MV_PCS_TEMP);
> +}
> +
> +static int mv10g_hwmon_read_temp_reg(struct phy_device *phydev)
> +{
> + if (phydev->drv->phy_id == MARVELL_PHY_ID_88X3310)
> + return mv3310_hwmon_read_temp_reg(phydev);
> + else /* MARVELL_PHY_ID_88E2110 */
> + return mv2110_hwmon_read_temp_reg(phydev);
> +}
> +
> static int mv3310_hwmon_read(struct device *dev, enum hwmon_sensor_types type,
> u32 attr, int channel, long *value)
> {
> @@ -116,7 +136,7 @@ static int mv3310_hwmon_read(struct device *dev, enum hwmon_sensor_types type,
> }
>
> if (type == hwmon_temp && attr == hwmon_temp_input) {
> - temp = phy_read_mmd(phydev, MDIO_MMD_VEND2, MV_V2_TEMP);
> + temp = mv10g_hwmon_read_temp_reg(phydev);
> if (temp < 0)
> return temp;
>
> @@ -196,7 +216,8 @@ static int mv3310_hwmon_probe(struct phy_device *phydev)
> struct mv3310_priv *priv = dev_get_drvdata(&phydev->mdio.dev);
> int i, j, ret;
>
> - if (phydev->drv->phy_id != MARVELL_PHY_ID_88X3310)
> + if (phydev->drv->phy_id != MARVELL_PHY_ID_88X3310 &&
> + phydev->drv->phy_id != MARVELL_PHY_ID_88E2110)
> return 0;
Doesn't that mean this condition can be removed, as this can only be
reached when one of those conditions is true?
>
> priv->hwmon_name = devm_kstrdup(dev, dev_name(dev), GFP_KERNEL);
> --
> 2.26.1
>
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
next prev parent reply other threads:[~2020-04-23 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 5:08 [PATCH net v3 1/2] net: phy: marvell10g: disable temperature sensor on 2110 Baruch Siach
2020-04-23 5:08 ` [PATCH net v3 2/2] net: phy: marvell10g: hwmon support for 2110 Baruch Siach
2020-04-23 13:09 ` Andrew Lunn
2020-04-23 13:39 ` Russell King - ARM Linux admin [this message]
2020-04-23 13:41 ` Russell King - ARM Linux admin
2020-04-23 13:37 ` [PATCH net v3 1/2] net: phy: marvell10g: disable temperature sensor on 2110 Russell King - ARM Linux admin
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=20200423133936.GS25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=baruch@tkos.co.il \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--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).