2014-01-05 07:17:06 +07:00
|
|
|
/* Framework for configuring and reading PHY devices
|
2005-07-31 06:31:23 +07:00
|
|
|
* Based on code in sungem_phy.c and gianfar_phy.c
|
|
|
|
*
|
|
|
|
* Author: Andy Fleming
|
|
|
|
*
|
|
|
|
* Copyright (c) 2004 Freescale Semiconductor, Inc.
|
2007-09-29 12:42:14 +07:00
|
|
|
* Copyright (c) 2006, 2007 Maciej W. Rozycki
|
2005-07-31 06:31:23 +07:00
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify it
|
|
|
|
* under the terms of the GNU General Public License as published by the
|
|
|
|
* Free Software Foundation; either version 2 of the License, or (at your
|
|
|
|
* option) any later version.
|
|
|
|
*
|
|
|
|
*/
|
2012-06-09 14:49:07 +07:00
|
|
|
|
|
|
|
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
|
|
|
|
|
2005-07-31 06:31:23 +07:00
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/string.h>
|
|
|
|
#include <linux/errno.h>
|
|
|
|
#include <linux/unistd.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/netdevice.h>
|
|
|
|
#include <linux/etherdevice.h>
|
|
|
|
#include <linux/skbuff.h>
|
|
|
|
#include <linux/mm.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/mii.h>
|
|
|
|
#include <linux/ethtool.h>
|
|
|
|
#include <linux/phy.h>
|
2017-01-25 17:39:49 +07:00
|
|
|
#include <linux/phy_led_triggers.h>
|
2006-10-03 22:18:35 +07:00
|
|
|
#include <linux/timer.h>
|
|
|
|
#include <linux/workqueue.h>
|
2012-06-28 04:14:38 +07:00
|
|
|
#include <linux/mdio.h>
|
2014-01-05 07:17:06 +07:00
|
|
|
#include <linux/io.h>
|
|
|
|
#include <linux/uaccess.h>
|
2011-07-27 06:09:06 +07:00
|
|
|
#include <linux/atomic.h>
|
2014-01-05 07:17:06 +07:00
|
|
|
|
2005-07-31 06:31:23 +07:00
|
|
|
#include <asm/irq.h>
|
|
|
|
|
2014-02-12 08:27:35 +07:00
|
|
|
static const char *phy_speed_to_str(int speed)
|
|
|
|
{
|
|
|
|
switch (speed) {
|
|
|
|
case SPEED_10:
|
|
|
|
return "10Mbps";
|
|
|
|
case SPEED_100:
|
|
|
|
return "100Mbps";
|
|
|
|
case SPEED_1000:
|
|
|
|
return "1Gbps";
|
|
|
|
case SPEED_2500:
|
|
|
|
return "2.5Gbps";
|
2017-04-03 04:30:06 +07:00
|
|
|
case SPEED_5000:
|
|
|
|
return "5Gbps";
|
2014-02-12 08:27:35 +07:00
|
|
|
case SPEED_10000:
|
|
|
|
return "10Gbps";
|
2017-06-09 20:45:32 +07:00
|
|
|
case SPEED_14000:
|
|
|
|
return "14Gbps";
|
2017-04-03 04:30:06 +07:00
|
|
|
case SPEED_20000:
|
|
|
|
return "20Gbps";
|
|
|
|
case SPEED_25000:
|
|
|
|
return "25Gbps";
|
|
|
|
case SPEED_40000:
|
|
|
|
return "40Gbps";
|
|
|
|
case SPEED_50000:
|
|
|
|
return "50Gbps";
|
|
|
|
case SPEED_56000:
|
|
|
|
return "56Gbps";
|
|
|
|
case SPEED_100000:
|
|
|
|
return "100Gbps";
|
2014-02-12 08:27:35 +07:00
|
|
|
case SPEED_UNKNOWN:
|
|
|
|
return "Unknown";
|
|
|
|
default:
|
|
|
|
return "Unsupported (update phy.c)";
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-05-17 00:17:56 +07:00
|
|
|
#define PHY_STATE_STR(_state) \
|
|
|
|
case PHY_##_state: \
|
|
|
|
return __stringify(_state); \
|
|
|
|
|
|
|
|
static const char *phy_state_to_str(enum phy_state st)
|
|
|
|
{
|
|
|
|
switch (st) {
|
|
|
|
PHY_STATE_STR(DOWN)
|
|
|
|
PHY_STATE_STR(STARTING)
|
|
|
|
PHY_STATE_STR(READY)
|
|
|
|
PHY_STATE_STR(PENDING)
|
|
|
|
PHY_STATE_STR(UP)
|
|
|
|
PHY_STATE_STR(AN)
|
|
|
|
PHY_STATE_STR(RUNNING)
|
|
|
|
PHY_STATE_STR(NOLINK)
|
|
|
|
PHY_STATE_STR(FORCING)
|
|
|
|
PHY_STATE_STR(CHANGELINK)
|
|
|
|
PHY_STATE_STR(HALTED)
|
|
|
|
PHY_STATE_STR(RESUMING)
|
|
|
|
}
|
|
|
|
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_print_status - Convenience function to print out the current phy status
|
|
|
|
* @phydev: the phy_device struct
|
2005-08-25 06:46:21 +07:00
|
|
|
*/
|
|
|
|
void phy_print_status(struct phy_device *phydev)
|
|
|
|
{
|
2014-01-05 07:17:06 +07:00
|
|
|
if (phydev->link) {
|
2014-02-12 08:27:34 +07:00
|
|
|
netdev_info(phydev->attached_dev,
|
2014-02-12 08:27:35 +07:00
|
|
|
"Link is Up - %s/%s - flow control %s\n",
|
|
|
|
phy_speed_to_str(phydev->speed),
|
2014-02-12 08:27:34 +07:00
|
|
|
DUPLEX_FULL == phydev->duplex ? "Full" : "Half",
|
|
|
|
phydev->pause ? "rx/tx" : "off");
|
2014-01-05 07:17:06 +07:00
|
|
|
} else {
|
2014-02-12 08:27:33 +07:00
|
|
|
netdev_info(phydev->attached_dev, "Link is Down\n");
|
2014-01-05 07:17:06 +07:00
|
|
|
}
|
2005-08-25 06:46:21 +07:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_print_status);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_clear_interrupt - Ack the phy device's interrupt
|
|
|
|
* @phydev: the phy_device struct
|
|
|
|
*
|
|
|
|
* If the @phydev driver has an ack_interrupt function, call it to
|
|
|
|
* ack and clear the phy device's interrupt.
|
|
|
|
*
|
2014-02-12 08:27:38 +07:00
|
|
|
* Returns 0 on success or < 0 on error.
|
2007-03-06 17:41:48 +07:00
|
|
|
*/
|
2010-10-21 15:37:41 +07:00
|
|
|
static int phy_clear_interrupt(struct phy_device *phydev)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
|
|
|
if (phydev->drv->ack_interrupt)
|
2014-01-05 07:21:52 +07:00
|
|
|
return phydev->drv->ack_interrupt(phydev);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2014-01-05 07:21:52 +07:00
|
|
|
return 0;
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_config_interrupt - configure the PHY device for the requested interrupts
|
|
|
|
* @phydev: the phy_device struct
|
|
|
|
* @interrupts: interrupt flags to configure for this @phydev
|
|
|
|
*
|
2014-02-12 08:27:38 +07:00
|
|
|
* Returns 0 on success or < 0 on error.
|
2007-03-06 17:41:48 +07:00
|
|
|
*/
|
2010-10-21 15:37:41 +07:00
|
|
|
static int phy_config_interrupt(struct phy_device *phydev, u32 interrupts)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
|
|
|
phydev->interrupts = interrupts;
|
|
|
|
if (phydev->drv->config_intr)
|
2014-01-05 07:21:52 +07:00
|
|
|
return phydev->drv->config_intr(phydev);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2014-01-05 07:21:52 +07:00
|
|
|
return 0;
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_aneg_done - return auto-negotiation status
|
|
|
|
* @phydev: target phy_device struct
|
2005-07-31 06:31:23 +07:00
|
|
|
*
|
2014-02-12 08:27:37 +07:00
|
|
|
* Description: Return the auto-negotiation status from this @phydev
|
|
|
|
* Returns > 0 on success or < 0 on error. 0 means that auto-negotiation
|
|
|
|
* is still pending.
|
2005-07-31 06:31:23 +07:00
|
|
|
*/
|
2016-11-11 06:10:46 +07:00
|
|
|
int phy_aneg_done(struct phy_device *phydev)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
2017-02-24 05:22:19 +07:00
|
|
|
if (phydev->drv && phydev->drv->aneg_done)
|
2014-02-12 08:27:37 +07:00
|
|
|
return phydev->drv->aneg_done(phydev);
|
|
|
|
|
2014-02-12 08:27:36 +07:00
|
|
|
return genphy_aneg_done(phydev);
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
2016-11-11 06:10:46 +07:00
|
|
|
EXPORT_SYMBOL(phy_aneg_done);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
|
|
|
/* A structure for mapping a particular speed and duplex
|
2014-01-05 07:17:06 +07:00
|
|
|
* combination to a particular SUPPORTED and ADVERTISED value
|
|
|
|
*/
|
2005-07-31 06:31:23 +07:00
|
|
|
struct phy_setting {
|
|
|
|
int speed;
|
|
|
|
int duplex;
|
|
|
|
u32 setting;
|
|
|
|
};
|
|
|
|
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
/* A mapping of all SUPPORTED settings to speed/duplex. This table
|
|
|
|
* must be grouped by speed and sorted in descending match priority
|
|
|
|
* - iow, descending speed. */
|
2006-03-04 09:33:57 +07:00
|
|
|
static const struct phy_setting settings[] = {
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
2014-07-15 02:05:46 +07:00
|
|
|
.speed = SPEED_10000,
|
|
|
|
.duplex = DUPLEX_FULL,
|
|
|
|
.setting = SUPPORTED_10000baseKR_Full,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.speed = SPEED_10000,
|
|
|
|
.duplex = DUPLEX_FULL,
|
|
|
|
.setting = SUPPORTED_10000baseKX4_Full,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.speed = SPEED_10000,
|
2005-07-31 06:31:23 +07:00
|
|
|
.duplex = DUPLEX_FULL,
|
|
|
|
.setting = SUPPORTED_10000baseT_Full,
|
|
|
|
},
|
2014-07-15 02:05:46 +07:00
|
|
|
{
|
|
|
|
.speed = SPEED_2500,
|
|
|
|
.duplex = DUPLEX_FULL,
|
|
|
|
.setting = SUPPORTED_2500baseX_Full,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.speed = SPEED_1000,
|
|
|
|
.duplex = DUPLEX_FULL,
|
|
|
|
.setting = SUPPORTED_1000baseKX_Full,
|
|
|
|
},
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
|
|
|
.speed = SPEED_1000,
|
|
|
|
.duplex = DUPLEX_FULL,
|
|
|
|
.setting = SUPPORTED_1000baseT_Full,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.speed = SPEED_1000,
|
|
|
|
.duplex = DUPLEX_HALF,
|
|
|
|
.setting = SUPPORTED_1000baseT_Half,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.speed = SPEED_100,
|
|
|
|
.duplex = DUPLEX_FULL,
|
|
|
|
.setting = SUPPORTED_100baseT_Full,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.speed = SPEED_100,
|
|
|
|
.duplex = DUPLEX_HALF,
|
|
|
|
.setting = SUPPORTED_100baseT_Half,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.speed = SPEED_10,
|
|
|
|
.duplex = DUPLEX_FULL,
|
|
|
|
.setting = SUPPORTED_10baseT_Full,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.speed = SPEED_10,
|
|
|
|
.duplex = DUPLEX_HALF,
|
|
|
|
.setting = SUPPORTED_10baseT_Half,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
* phy_lookup_setting - lookup a PHY setting
|
2007-03-06 17:41:48 +07:00
|
|
|
* @speed: speed to match
|
|
|
|
* @duplex: duplex to match
|
2017-06-05 09:46:53 +07:00
|
|
|
* @features: allowed link modes
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
* @exact: an exact match is required
|
|
|
|
*
|
|
|
|
* Search the settings array for a setting that matches the speed and
|
|
|
|
* duplex, and which is supported.
|
2005-07-31 06:31:23 +07:00
|
|
|
*
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
* If @exact is unset, either an exact match or %NULL for no match will
|
|
|
|
* be returned.
|
|
|
|
*
|
|
|
|
* If @exact is set, an exact match, the fastest supported setting at
|
|
|
|
* or below the specified speed, the slowest supported setting, or if
|
|
|
|
* they all fail, %NULL will be returned.
|
2005-07-31 06:31:23 +07:00
|
|
|
*/
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
static const struct phy_setting *
|
|
|
|
phy_lookup_setting(int speed, int duplex, u32 features, bool exact)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
const struct phy_setting *p, *match = NULL, *last = NULL;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0, p = settings; i < ARRAY_SIZE(settings); i++, p++) {
|
|
|
|
if (p->setting & features) {
|
|
|
|
last = p;
|
|
|
|
if (p->speed == speed && p->duplex == duplex) {
|
|
|
|
/* Exact match for speed and duplex */
|
|
|
|
match = p;
|
|
|
|
break;
|
|
|
|
} else if (!exact) {
|
|
|
|
if (!match && p->speed <= speed)
|
|
|
|
/* Candidate */
|
|
|
|
match = p;
|
|
|
|
|
|
|
|
if (p->speed < speed)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2005-07-31 06:31:23 +07:00
|
|
|
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
if (!match && !exact)
|
|
|
|
match = last;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
return match;
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
* phy_find_valid - find a PHY setting that matches the requested parameters
|
|
|
|
* @speed: desired speed
|
|
|
|
* @duplex: desired duplex
|
|
|
|
* @supported: mask of supported link modes
|
2005-07-31 06:31:23 +07:00
|
|
|
*
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
* Locate a supported phy setting that is, in priority order:
|
|
|
|
* - an exact match for the specified speed and duplex mode
|
|
|
|
* - a match for the specified speed, or slower speed
|
|
|
|
* - the slowest supported speed
|
|
|
|
* Returns the matched phy_setting entry, or %NULL if no supported phy
|
|
|
|
* settings were found.
|
2005-07-31 06:31:23 +07:00
|
|
|
*/
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
static const struct phy_setting *
|
|
|
|
phy_find_valid(int speed, int duplex, u32 supported)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
return phy_lookup_setting(speed, duplex, supported, false);
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
2016-10-17 22:49:54 +07:00
|
|
|
/**
|
|
|
|
* phy_supported_speeds - return all speeds currently supported by a phy device
|
|
|
|
* @phy: The phy device to return supported speeds of.
|
|
|
|
* @speeds: buffer to store supported speeds in.
|
|
|
|
* @size: size of speeds buffer.
|
|
|
|
*
|
|
|
|
* Description: Returns the number of supported speeds, and fills the speeds
|
|
|
|
* buffer with the supported speeds. If speeds buffer is too small to contain
|
|
|
|
* all currently supported speeds, will return as many speeds as can fit.
|
|
|
|
*/
|
|
|
|
unsigned int phy_supported_speeds(struct phy_device *phy,
|
|
|
|
unsigned int *speeds,
|
|
|
|
unsigned int size)
|
|
|
|
{
|
|
|
|
unsigned int count = 0;
|
|
|
|
unsigned int idx = 0;
|
|
|
|
|
2017-04-13 22:49:20 +07:00
|
|
|
for (idx = 0; idx < ARRAY_SIZE(settings) && count < size; idx++)
|
2016-10-17 22:49:54 +07:00
|
|
|
/* Assumes settings are grouped by speed */
|
2017-04-13 22:49:20 +07:00
|
|
|
if ((settings[idx].setting & phy->supported) &&
|
|
|
|
(count == 0 || speeds[count - 1] != settings[idx].speed))
|
|
|
|
speeds[count++] = settings[idx].speed;
|
2016-10-17 22:49:54 +07:00
|
|
|
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
2015-02-18 00:36:22 +07:00
|
|
|
/**
|
|
|
|
* phy_check_valid - check if there is a valid PHY setting which matches
|
|
|
|
* speed, duplex, and feature mask
|
|
|
|
* @speed: speed to match
|
|
|
|
* @duplex: duplex to match
|
|
|
|
* @features: A mask of the valid settings
|
|
|
|
*
|
|
|
|
* Description: Returns true if there is a valid setting, false otherwise.
|
|
|
|
*/
|
|
|
|
static inline bool phy_check_valid(int speed, int duplex, u32 features)
|
|
|
|
{
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
return !!phy_lookup_setting(speed, duplex, features, true);
|
2015-02-18 00:36:22 +07:00
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_sanitize_settings - make sure the PHY is set to supported speed and duplex
|
|
|
|
* @phydev: the target phy_device struct
|
2005-07-31 06:31:23 +07:00
|
|
|
*
|
2007-03-06 17:41:48 +07:00
|
|
|
* Description: Make sure the PHY is set to supported speeds and
|
2005-07-31 06:31:23 +07:00
|
|
|
* duplexes. Drop down by one in this order: 1000/FULL,
|
2007-03-06 17:41:48 +07:00
|
|
|
* 1000/HALF, 100/FULL, 100/HALF, 10/FULL, 10/HALF.
|
2005-07-31 06:31:23 +07:00
|
|
|
*/
|
2010-10-21 15:37:41 +07:00
|
|
|
static void phy_sanitize_settings(struct phy_device *phydev)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
const struct phy_setting *setting;
|
2005-07-31 06:31:23 +07:00
|
|
|
u32 features = phydev->supported;
|
|
|
|
|
|
|
|
/* Sanitize settings based on PHY capabilities */
|
|
|
|
if ((features & SUPPORTED_Autoneg) == 0)
|
2007-08-07 17:12:41 +07:00
|
|
|
phydev->autoneg = AUTONEG_DISABLE;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
net: phy: improve phylib correctness for non-autoneg settings
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0, and scans upwards looking for an exact speed and duplex match.
When it doesn't find it, it returns MAX_NUM_SETTINGS - 1, which is
10baseT-Half duplex.
phy_find_valid() then scans from the point (and effectively only checks
one entry) before bailing out, returning MAX_NUM_SETTINGS - 1.
phy_sanitize_settings() then sets ->speed to SPEED_10 and ->duplex to
DUPLEX_HALF whether or not 10baseT-Half is supported or not. This goes
against all the comments against these functions, and 10baseT-Half may
not even be supported by the hardware.
Rework these functions, introducing a new method of scanning the table.
There are two modes of lookup that phylib wants: exact, and inexact.
- in exact mode, we return either an exact match or failure
- in inexact mode, we return an exact match if it exists, a match at
the highest speed that is not greater than the requested speed
(ignoring duplex), or failing that, the lowest supported speed, or
failure.
The biggest difference is that we always check whether the entry is
supported before further consideration, so all unsupported entries are
not considered as candidates.
This results in arguably saner behaviour, better matches the comments,
and is probably what users would expect.
This becomes important as ethernet speeds increase, PHYs exist which do
not support the 10Mbit speeds, and half-duplex is likely to become
obsolete - it's already not even an option on 10Gbit and faster links.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-13 22:49:15 +07:00
|
|
|
setting = phy_find_valid(phydev->speed, phydev->duplex, features);
|
|
|
|
if (setting) {
|
|
|
|
phydev->speed = setting->speed;
|
|
|
|
phydev->duplex = setting->duplex;
|
|
|
|
} else {
|
|
|
|
/* We failed to find anything (no supported speeds?) */
|
|
|
|
phydev->speed = SPEED_UNKNOWN;
|
|
|
|
phydev->duplex = DUPLEX_UNKNOWN;
|
|
|
|
}
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_ethtool_sset - generic ethtool sset function, handles all the details
|
|
|
|
* @phydev: target phy_device struct
|
|
|
|
* @cmd: ethtool_cmd
|
2005-07-31 06:31:23 +07:00
|
|
|
*
|
|
|
|
* A few notes about parameter checking:
|
|
|
|
* - We don't set port or transceiver, so we don't care what they
|
|
|
|
* were set to.
|
|
|
|
* - phy_start_aneg() will make sure forced settings are sane, and
|
|
|
|
* choose the next best ones from the ones selected, so we don't
|
2007-03-06 17:41:48 +07:00
|
|
|
* care if ethtool tries to give us bad values.
|
2005-07-31 06:31:23 +07:00
|
|
|
*/
|
|
|
|
int phy_ethtool_sset(struct phy_device *phydev, struct ethtool_cmd *cmd)
|
|
|
|
{
|
2011-04-28 01:32:39 +07:00
|
|
|
u32 speed = ethtool_cmd_speed(cmd);
|
|
|
|
|
2016-01-07 02:11:16 +07:00
|
|
|
if (cmd->phy_address != phydev->mdio.addr)
|
2005-07-31 06:31:23 +07:00
|
|
|
return -EINVAL;
|
|
|
|
|
2014-01-05 07:17:06 +07:00
|
|
|
/* We make sure that we don't pass unsupported values in to the PHY */
|
2005-07-31 06:31:23 +07:00
|
|
|
cmd->advertising &= phydev->supported;
|
|
|
|
|
|
|
|
/* Verify the settings we care about. */
|
|
|
|
if (cmd->autoneg != AUTONEG_ENABLE && cmd->autoneg != AUTONEG_DISABLE)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
if (cmd->autoneg == AUTONEG_ENABLE && cmd->advertising == 0)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2009-12-03 14:58:21 +07:00
|
|
|
if (cmd->autoneg == AUTONEG_DISABLE &&
|
2011-04-28 01:32:39 +07:00
|
|
|
((speed != SPEED_1000 &&
|
|
|
|
speed != SPEED_100 &&
|
|
|
|
speed != SPEED_10) ||
|
2009-12-03 14:58:21 +07:00
|
|
|
(cmd->duplex != DUPLEX_HALF &&
|
|
|
|
cmd->duplex != DUPLEX_FULL)))
|
2005-07-31 06:31:23 +07:00
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
phydev->autoneg = cmd->autoneg;
|
|
|
|
|
2011-04-28 01:32:39 +07:00
|
|
|
phydev->speed = speed;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
|
|
|
phydev->advertising = cmd->advertising;
|
|
|
|
|
|
|
|
if (AUTONEG_ENABLE == cmd->autoneg)
|
|
|
|
phydev->advertising |= ADVERTISED_Autoneg;
|
|
|
|
else
|
|
|
|
phydev->advertising &= ~ADVERTISED_Autoneg;
|
|
|
|
|
|
|
|
phydev->duplex = cmd->duplex;
|
|
|
|
|
2016-11-29 16:46:47 +07:00
|
|
|
phydev->mdix_ctrl = cmd->eth_tp_mdix_ctrl;
|
2015-07-10 08:56:54 +07:00
|
|
|
|
2005-07-31 06:31:23 +07:00
|
|
|
/* Restart the PHY */
|
|
|
|
phy_start_aneg(phydev);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2007-01-21 05:38:26 +07:00
|
|
|
EXPORT_SYMBOL(phy_ethtool_sset);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2016-04-15 05:35:00 +07:00
|
|
|
int phy_ethtool_ksettings_set(struct phy_device *phydev,
|
|
|
|
const struct ethtool_link_ksettings *cmd)
|
|
|
|
{
|
|
|
|
u8 autoneg = cmd->base.autoneg;
|
|
|
|
u8 duplex = cmd->base.duplex;
|
|
|
|
u32 speed = cmd->base.speed;
|
|
|
|
u32 advertising;
|
|
|
|
|
|
|
|
if (cmd->base.phy_address != phydev->mdio.addr)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
ethtool_convert_link_mode_to_legacy_u32(&advertising,
|
|
|
|
cmd->link_modes.advertising);
|
|
|
|
|
|
|
|
/* We make sure that we don't pass unsupported values in to the PHY */
|
|
|
|
advertising &= phydev->supported;
|
|
|
|
|
|
|
|
/* Verify the settings we care about. */
|
|
|
|
if (autoneg != AUTONEG_ENABLE && autoneg != AUTONEG_DISABLE)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
if (autoneg == AUTONEG_ENABLE && advertising == 0)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
if (autoneg == AUTONEG_DISABLE &&
|
|
|
|
((speed != SPEED_1000 &&
|
|
|
|
speed != SPEED_100 &&
|
|
|
|
speed != SPEED_10) ||
|
|
|
|
(duplex != DUPLEX_HALF &&
|
|
|
|
duplex != DUPLEX_FULL)))
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
phydev->autoneg = autoneg;
|
|
|
|
|
|
|
|
phydev->speed = speed;
|
|
|
|
|
|
|
|
phydev->advertising = advertising;
|
|
|
|
|
|
|
|
if (autoneg == AUTONEG_ENABLE)
|
|
|
|
phydev->advertising |= ADVERTISED_Autoneg;
|
|
|
|
else
|
|
|
|
phydev->advertising &= ~ADVERTISED_Autoneg;
|
|
|
|
|
|
|
|
phydev->duplex = duplex;
|
|
|
|
|
2016-11-29 16:46:47 +07:00
|
|
|
phydev->mdix_ctrl = cmd->base.eth_tp_mdix_ctrl;
|
2016-04-15 05:35:00 +07:00
|
|
|
|
|
|
|
/* Restart the PHY */
|
|
|
|
phy_start_aneg(phydev);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_ethtool_ksettings_set);
|
|
|
|
|
2005-07-31 06:31:23 +07:00
|
|
|
int phy_ethtool_gset(struct phy_device *phydev, struct ethtool_cmd *cmd)
|
|
|
|
{
|
|
|
|
cmd->supported = phydev->supported;
|
|
|
|
|
|
|
|
cmd->advertising = phydev->advertising;
|
2013-12-07 04:01:30 +07:00
|
|
|
cmd->lp_advertising = phydev->lp_advertising;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2011-04-28 01:32:40 +07:00
|
|
|
ethtool_cmd_speed_set(cmd, phydev->speed);
|
2005-07-31 06:31:23 +07:00
|
|
|
cmd->duplex = phydev->duplex;
|
2014-02-14 07:08:43 +07:00
|
|
|
if (phydev->interface == PHY_INTERFACE_MODE_MOCA)
|
|
|
|
cmd->port = PORT_BNC;
|
|
|
|
else
|
|
|
|
cmd->port = PORT_MII;
|
2016-01-07 02:11:16 +07:00
|
|
|
cmd->phy_address = phydev->mdio.addr;
|
2013-05-23 08:11:12 +07:00
|
|
|
cmd->transceiver = phy_is_internal(phydev) ?
|
|
|
|
XCVR_INTERNAL : XCVR_EXTERNAL;
|
2005-07-31 06:31:23 +07:00
|
|
|
cmd->autoneg = phydev->autoneg;
|
2016-11-29 16:46:47 +07:00
|
|
|
cmd->eth_tp_mdix_ctrl = phydev->mdix_ctrl;
|
|
|
|
cmd->eth_tp_mdix = phydev->mdix;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2007-01-21 05:38:26 +07:00
|
|
|
EXPORT_SYMBOL(phy_ethtool_gset);
|
2016-04-15 05:35:00 +07:00
|
|
|
|
|
|
|
int phy_ethtool_ksettings_get(struct phy_device *phydev,
|
|
|
|
struct ethtool_link_ksettings *cmd)
|
|
|
|
{
|
|
|
|
ethtool_convert_legacy_u32_to_link_mode(cmd->link_modes.supported,
|
|
|
|
phydev->supported);
|
|
|
|
|
|
|
|
ethtool_convert_legacy_u32_to_link_mode(cmd->link_modes.advertising,
|
|
|
|
phydev->advertising);
|
|
|
|
|
|
|
|
ethtool_convert_legacy_u32_to_link_mode(cmd->link_modes.lp_advertising,
|
|
|
|
phydev->lp_advertising);
|
|
|
|
|
|
|
|
cmd->base.speed = phydev->speed;
|
|
|
|
cmd->base.duplex = phydev->duplex;
|
|
|
|
if (phydev->interface == PHY_INTERFACE_MODE_MOCA)
|
|
|
|
cmd->base.port = PORT_BNC;
|
|
|
|
else
|
|
|
|
cmd->base.port = PORT_MII;
|
|
|
|
|
|
|
|
cmd->base.phy_address = phydev->mdio.addr;
|
|
|
|
cmd->base.autoneg = phydev->autoneg;
|
2016-11-29 16:46:47 +07:00
|
|
|
cmd->base.eth_tp_mdix_ctrl = phydev->mdix_ctrl;
|
|
|
|
cmd->base.eth_tp_mdix = phydev->mdix;
|
2016-04-15 05:35:00 +07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_ethtool_ksettings_get);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_mii_ioctl - generic PHY MII ioctl interface
|
|
|
|
* @phydev: the phy_device struct
|
2010-08-09 20:41:59 +07:00
|
|
|
* @ifr: &struct ifreq for socket ioctl's
|
2007-03-06 17:41:48 +07:00
|
|
|
* @cmd: ioctl cmd to execute
|
|
|
|
*
|
|
|
|
* Note that this function is currently incompatible with the
|
2005-07-31 06:31:23 +07:00
|
|
|
* PHYCONTROL layer. It changes registers without regard to
|
2007-03-06 17:41:48 +07:00
|
|
|
* current state. Use at own risk.
|
2005-07-31 06:31:23 +07:00
|
|
|
*/
|
2014-01-05 07:17:06 +07:00
|
|
|
int phy_mii_ioctl(struct phy_device *phydev, struct ifreq *ifr, int cmd)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
2010-07-17 15:48:55 +07:00
|
|
|
struct mii_ioctl_data *mii_data = if_mii(ifr);
|
2005-07-31 06:31:23 +07:00
|
|
|
u16 val = mii_data->val_in;
|
2014-11-12 03:39:39 +07:00
|
|
|
bool change_autoneg = false;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
|
|
|
switch (cmd) {
|
|
|
|
case SIOCGMIIPHY:
|
2016-01-07 02:11:16 +07:00
|
|
|
mii_data->phy_id = phydev->mdio.addr;
|
2008-09-18 10:06:52 +07:00
|
|
|
/* fall through */
|
|
|
|
|
2005-07-31 06:31:23 +07:00
|
|
|
case SIOCGMIIREG:
|
2016-01-07 02:11:16 +07:00
|
|
|
mii_data->val_out = mdiobus_read(phydev->mdio.bus,
|
|
|
|
mii_data->phy_id,
|
2011-03-10 13:52:13 +07:00
|
|
|
mii_data->reg_num);
|
2014-01-05 07:21:52 +07:00
|
|
|
return 0;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
|
|
|
case SIOCSMIIREG:
|
2016-01-07 02:11:16 +07:00
|
|
|
if (mii_data->phy_id == phydev->mdio.addr) {
|
2013-12-18 12:38:12 +07:00
|
|
|
switch (mii_data->reg_num) {
|
2005-07-31 06:31:23 +07:00
|
|
|
case MII_BMCR:
|
2014-11-12 03:39:39 +07:00
|
|
|
if ((val & (BMCR_RESET | BMCR_ANENABLE)) == 0) {
|
|
|
|
if (phydev->autoneg == AUTONEG_ENABLE)
|
|
|
|
change_autoneg = true;
|
2005-07-31 06:31:23 +07:00
|
|
|
phydev->autoneg = AUTONEG_DISABLE;
|
2014-11-12 03:39:39 +07:00
|
|
|
if (val & BMCR_FULLDPLX)
|
|
|
|
phydev->duplex = DUPLEX_FULL;
|
|
|
|
else
|
|
|
|
phydev->duplex = DUPLEX_HALF;
|
|
|
|
if (val & BMCR_SPEED1000)
|
|
|
|
phydev->speed = SPEED_1000;
|
|
|
|
else if (val & BMCR_SPEED100)
|
|
|
|
phydev->speed = SPEED_100;
|
|
|
|
else phydev->speed = SPEED_10;
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
if (phydev->autoneg == AUTONEG_DISABLE)
|
|
|
|
change_autoneg = true;
|
2005-07-31 06:31:23 +07:00
|
|
|
phydev->autoneg = AUTONEG_ENABLE;
|
2014-11-12 03:39:39 +07:00
|
|
|
}
|
2005-07-31 06:31:23 +07:00
|
|
|
break;
|
|
|
|
case MII_ADVERTISE:
|
2014-11-12 03:39:39 +07:00
|
|
|
phydev->advertising = mii_adv_to_ethtool_adv_t(val);
|
|
|
|
change_autoneg = true;
|
2005-07-31 06:31:23 +07:00
|
|
|
break;
|
|
|
|
default:
|
|
|
|
/* do nothing */
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-01-07 02:11:16 +07:00
|
|
|
mdiobus_write(phydev->mdio.bus, mii_data->phy_id,
|
2011-03-10 13:52:13 +07:00
|
|
|
mii_data->reg_num, val);
|
|
|
|
|
2016-01-07 02:11:16 +07:00
|
|
|
if (mii_data->phy_id == phydev->mdio.addr &&
|
2015-12-03 16:02:35 +07:00
|
|
|
mii_data->reg_num == MII_BMCR &&
|
2013-12-07 04:01:31 +07:00
|
|
|
val & BMCR_RESET)
|
2014-01-05 07:21:52 +07:00
|
|
|
return phy_init_hw(phydev);
|
2014-11-12 03:39:39 +07:00
|
|
|
|
|
|
|
if (change_autoneg)
|
|
|
|
return phy_start_aneg(phydev);
|
|
|
|
|
2014-01-05 07:21:52 +07:00
|
|
|
return 0;
|
2007-11-29 02:56:34 +07:00
|
|
|
|
2010-07-17 15:49:36 +07:00
|
|
|
case SIOCSHWTSTAMP:
|
2017-02-18 07:07:34 +07:00
|
|
|
if (phydev->drv && phydev->drv->hwtstamp)
|
2010-07-17 15:49:36 +07:00
|
|
|
return phydev->drv->hwtstamp(phydev, ifr);
|
|
|
|
/* fall through */
|
|
|
|
|
2007-11-29 02:56:34 +07:00
|
|
|
default:
|
2008-09-18 10:06:52 +07:00
|
|
|
return -EOPNOTSUPP;
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
}
|
2007-09-18 03:21:40 +07:00
|
|
|
EXPORT_SYMBOL(phy_mii_ioctl);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
2017-04-20 18:00:04 +07:00
|
|
|
* phy_start_aneg_priv - start auto-negotiation for this PHY device
|
2007-03-06 17:41:48 +07:00
|
|
|
* @phydev: the phy_device struct
|
2017-04-20 18:00:04 +07:00
|
|
|
* @sync: indicate whether we should wait for the workqueue cancelation
|
2005-08-25 06:46:21 +07:00
|
|
|
*
|
2007-03-06 17:41:48 +07:00
|
|
|
* Description: Sanitizes the settings (if we're not autonegotiating
|
|
|
|
* them), and then calls the driver's config_aneg function.
|
|
|
|
* If the PHYCONTROL Layer is operating, we change the state to
|
|
|
|
* reflect the beginning of Auto-negotiation or forcing.
|
2005-08-25 06:46:21 +07:00
|
|
|
*/
|
2017-04-20 18:00:04 +07:00
|
|
|
static int phy_start_aneg_priv(struct phy_device *phydev, bool sync)
|
2005-08-25 06:46:21 +07:00
|
|
|
{
|
2017-04-20 18:00:04 +07:00
|
|
|
bool trigger = 0;
|
2005-08-25 06:46:21 +07:00
|
|
|
int err;
|
|
|
|
|
2017-02-18 07:07:34 +07:00
|
|
|
if (!phydev->drv)
|
|
|
|
return -EIO;
|
|
|
|
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_lock(&phydev->lock);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
|
|
|
if (AUTONEG_DISABLE == phydev->autoneg)
|
|
|
|
phy_sanitize_settings(phydev);
|
|
|
|
|
2015-01-27 07:58:15 +07:00
|
|
|
/* Invalidate LP advertising flags */
|
|
|
|
phydev->lp_advertising = 0;
|
|
|
|
|
2005-08-25 06:46:21 +07:00
|
|
|
err = phydev->drv->config_aneg(phydev);
|
|
|
|
if (err < 0)
|
|
|
|
goto out_unlock;
|
|
|
|
|
|
|
|
if (phydev->state != PHY_HALTED) {
|
|
|
|
if (AUTONEG_ENABLE == phydev->autoneg) {
|
|
|
|
phydev->state = PHY_AN;
|
|
|
|
phydev->link_timeout = PHY_AN_TIMEOUT;
|
|
|
|
} else {
|
|
|
|
phydev->state = PHY_FORCING;
|
|
|
|
phydev->link_timeout = PHY_FORCE_TIMEOUT;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-04-20 18:00:04 +07:00
|
|
|
/* Re-schedule a PHY state machine to check PHY status because
|
|
|
|
* negotiation may already be done and aneg interrupt may not be
|
|
|
|
* generated.
|
|
|
|
*/
|
|
|
|
if (phy_interrupt_is_valid(phydev) && (phydev->state == PHY_AN)) {
|
|
|
|
err = phy_aneg_done(phydev);
|
|
|
|
if (err > 0) {
|
|
|
|
trigger = true;
|
|
|
|
err = 0;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2005-08-25 06:46:21 +07:00
|
|
|
out_unlock:
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_unlock(&phydev->lock);
|
2017-04-20 18:00:04 +07:00
|
|
|
|
|
|
|
if (trigger)
|
|
|
|
phy_trigger_machine(phydev, sync);
|
|
|
|
|
2005-08-25 06:46:21 +07:00
|
|
|
return err;
|
|
|
|
}
|
2017-04-20 18:00:04 +07:00
|
|
|
|
|
|
|
/**
|
|
|
|
* phy_start_aneg - start auto-negotiation for this PHY device
|
|
|
|
* @phydev: the phy_device struct
|
|
|
|
*
|
|
|
|
* Description: Sanitizes the settings (if we're not autonegotiating
|
|
|
|
* them), and then calls the driver's config_aneg function.
|
|
|
|
* If the PHYCONTROL Layer is operating, we change the state to
|
|
|
|
* reflect the beginning of Auto-negotiation or forcing.
|
|
|
|
*/
|
|
|
|
int phy_start_aneg(struct phy_device *phydev)
|
|
|
|
{
|
|
|
|
return phy_start_aneg_priv(phydev, true);
|
|
|
|
}
|
2005-08-25 06:46:21 +07:00
|
|
|
EXPORT_SYMBOL(phy_start_aneg);
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_start_machine - start PHY state machine tracking
|
|
|
|
* @phydev: the phy_device struct
|
2005-07-31 06:31:23 +07:00
|
|
|
*
|
2007-03-06 17:41:48 +07:00
|
|
|
* Description: The PHY infrastructure can run a state machine
|
2005-07-31 06:31:23 +07:00
|
|
|
* which tracks whether the PHY is starting up, negotiating,
|
|
|
|
* etc. This function starts the timer which tracks the state
|
2014-01-05 07:27:17 +07:00
|
|
|
* of the PHY. If you want to maintain your own state machine,
|
|
|
|
* do not call this function.
|
2007-03-06 17:41:48 +07:00
|
|
|
*/
|
2014-01-05 07:27:17 +07:00
|
|
|
void phy_start_machine(struct phy_device *phydev)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
2013-04-24 18:42:55 +07:00
|
|
|
queue_delayed_work(system_power_efficient_wq, &phydev->state_queue, HZ);
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
net: phy: Trigger state machine on state change and not polling.
The phy_start() is used to indicate the PHY is now ready to do its
work. The state is changed, normally to PHY_UP which means that both
the MAC and the PHY are ready.
If the phy driver is using polling, when the next poll happens, the
state machine notices the PHY is now in PHY_UP, and kicks off
auto-negotiation, if needed.
If however, the PHY is using interrupts, there is no polling. The phy
is stuck in PHY_UP until the next interrupt comes along. And there is
no reason for the PHY to interrupt.
Have phy_start() schedule the state machine to run, which both speeds
up the polling use case, and makes the interrupt use case actually
work.
This problems exists whenever there is a state change which will not
cause an interrupt. Trigger the state machine in these cases,
e.g. phy_error().
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Cc: Kyle Roeschley <kyle.roeschley@ni.com>
Tested-by: Kyle Roeschley <kyle.roeschley@ni.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-10-13 03:14:53 +07:00
|
|
|
/**
|
|
|
|
* phy_trigger_machine - trigger the state machine to run
|
|
|
|
*
|
|
|
|
* @phydev: the phy_device struct
|
2017-01-21 06:31:52 +07:00
|
|
|
* @sync: indicate whether we should wait for the workqueue cancelation
|
net: phy: Trigger state machine on state change and not polling.
The phy_start() is used to indicate the PHY is now ready to do its
work. The state is changed, normally to PHY_UP which means that both
the MAC and the PHY are ready.
If the phy driver is using polling, when the next poll happens, the
state machine notices the PHY is now in PHY_UP, and kicks off
auto-negotiation, if needed.
If however, the PHY is using interrupts, there is no polling. The phy
is stuck in PHY_UP until the next interrupt comes along. And there is
no reason for the PHY to interrupt.
Have phy_start() schedule the state machine to run, which both speeds
up the polling use case, and makes the interrupt use case actually
work.
This problems exists whenever there is a state change which will not
cause an interrupt. Trigger the state machine in these cases,
e.g. phy_error().
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Cc: Kyle Roeschley <kyle.roeschley@ni.com>
Tested-by: Kyle Roeschley <kyle.roeschley@ni.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-10-13 03:14:53 +07:00
|
|
|
*
|
|
|
|
* Description: There has been a change in state which requires that the
|
|
|
|
* state machine runs.
|
|
|
|
*/
|
|
|
|
|
2017-04-20 18:00:04 +07:00
|
|
|
void phy_trigger_machine(struct phy_device *phydev, bool sync)
|
net: phy: Trigger state machine on state change and not polling.
The phy_start() is used to indicate the PHY is now ready to do its
work. The state is changed, normally to PHY_UP which means that both
the MAC and the PHY are ready.
If the phy driver is using polling, when the next poll happens, the
state machine notices the PHY is now in PHY_UP, and kicks off
auto-negotiation, if needed.
If however, the PHY is using interrupts, there is no polling. The phy
is stuck in PHY_UP until the next interrupt comes along. And there is
no reason for the PHY to interrupt.
Have phy_start() schedule the state machine to run, which both speeds
up the polling use case, and makes the interrupt use case actually
work.
This problems exists whenever there is a state change which will not
cause an interrupt. Trigger the state machine in these cases,
e.g. phy_error().
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Cc: Kyle Roeschley <kyle.roeschley@ni.com>
Tested-by: Kyle Roeschley <kyle.roeschley@ni.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-10-13 03:14:53 +07:00
|
|
|
{
|
2017-01-21 06:31:52 +07:00
|
|
|
if (sync)
|
|
|
|
cancel_delayed_work_sync(&phydev->state_queue);
|
|
|
|
else
|
|
|
|
cancel_delayed_work(&phydev->state_queue);
|
net: phy: Trigger state machine on state change and not polling.
The phy_start() is used to indicate the PHY is now ready to do its
work. The state is changed, normally to PHY_UP which means that both
the MAC and the PHY are ready.
If the phy driver is using polling, when the next poll happens, the
state machine notices the PHY is now in PHY_UP, and kicks off
auto-negotiation, if needed.
If however, the PHY is using interrupts, there is no polling. The phy
is stuck in PHY_UP until the next interrupt comes along. And there is
no reason for the PHY to interrupt.
Have phy_start() schedule the state machine to run, which both speeds
up the polling use case, and makes the interrupt use case actually
work.
This problems exists whenever there is a state change which will not
cause an interrupt. Trigger the state machine in these cases,
e.g. phy_error().
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Cc: Kyle Roeschley <kyle.roeschley@ni.com>
Tested-by: Kyle Roeschley <kyle.roeschley@ni.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-10-13 03:14:53 +07:00
|
|
|
queue_delayed_work(system_power_efficient_wq, &phydev->state_queue, 0);
|
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_stop_machine - stop the PHY state machine tracking
|
|
|
|
* @phydev: target phy_device struct
|
2005-07-31 06:31:23 +07:00
|
|
|
*
|
2007-03-06 17:41:48 +07:00
|
|
|
* Description: Stops the state machine timer, sets the state to UP
|
2006-07-26 03:53:53 +07:00
|
|
|
* (unless it wasn't up yet). This function must be called BEFORE
|
2005-07-31 06:31:23 +07:00
|
|
|
* phy_detach.
|
|
|
|
*/
|
|
|
|
void phy_stop_machine(struct phy_device *phydev)
|
|
|
|
{
|
2009-03-14 05:41:19 +07:00
|
|
|
cancel_delayed_work_sync(&phydev->state_queue);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_lock(&phydev->lock);
|
2017-03-23 03:27:01 +07:00
|
|
|
if (phydev->state > PHY_UP && phydev->state != PHY_HALTED)
|
2005-07-31 06:31:23 +07:00
|
|
|
phydev->state = PHY_UP;
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_unlock(&phydev->lock);
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_error - enter HALTED state for this PHY device
|
|
|
|
* @phydev: target phy_device struct
|
2005-07-31 06:31:23 +07:00
|
|
|
*
|
|
|
|
* Moves the PHY to the HALTED state in response to a read
|
|
|
|
* or write error, and tells the controller the link is down.
|
|
|
|
* Must not be called from interrupt context, or while the
|
|
|
|
* phydev->lock is held.
|
|
|
|
*/
|
2008-05-03 01:00:51 +07:00
|
|
|
static void phy_error(struct phy_device *phydev)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_lock(&phydev->lock);
|
2005-07-31 06:31:23 +07:00
|
|
|
phydev->state = PHY_HALTED;
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_unlock(&phydev->lock);
|
net: phy: Trigger state machine on state change and not polling.
The phy_start() is used to indicate the PHY is now ready to do its
work. The state is changed, normally to PHY_UP which means that both
the MAC and the PHY are ready.
If the phy driver is using polling, when the next poll happens, the
state machine notices the PHY is now in PHY_UP, and kicks off
auto-negotiation, if needed.
If however, the PHY is using interrupts, there is no polling. The phy
is stuck in PHY_UP until the next interrupt comes along. And there is
no reason for the PHY to interrupt.
Have phy_start() schedule the state machine to run, which both speeds
up the polling use case, and makes the interrupt use case actually
work.
This problems exists whenever there is a state change which will not
cause an interrupt. Trigger the state machine in these cases,
e.g. phy_error().
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Cc: Kyle Roeschley <kyle.roeschley@ni.com>
Tested-by: Kyle Roeschley <kyle.roeschley@ni.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-10-13 03:14:53 +07:00
|
|
|
|
2017-01-21 06:31:52 +07:00
|
|
|
phy_trigger_machine(phydev, false);
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_interrupt - PHY interrupt handler
|
|
|
|
* @irq: interrupt line
|
|
|
|
* @phy_dat: phy_device pointer
|
2005-08-25 06:46:21 +07:00
|
|
|
*
|
2007-03-06 17:41:48 +07:00
|
|
|
* Description: When a PHY interrupt occurs, the handler disables
|
2016-10-17 00:56:51 +07:00
|
|
|
* interrupts, and uses phy_change to handle the interrupt.
|
2005-08-25 06:46:21 +07:00
|
|
|
*/
|
IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
of passing regs around manually through all ~1800 interrupt handlers in the
Linux kernel.
The regs pointer is used in few places, but it potentially costs both stack
space and code to pass it around. On the FRV arch, removing the regs parameter
from all the genirq function results in a 20% speed up of the IRQ exit path
(ie: from leaving timer_interrupt() to leaving do_IRQ()).
Where appropriate, an arch may override the generic storage facility and do
something different with the variable. On FRV, for instance, the address is
maintained in GR28 at all times inside the kernel as part of general exception
handling.
Having looked over the code, it appears that the parameter may be handed down
through up to twenty or so layers of functions. Consider a USB character
device attached to a USB hub, attached to a USB controller that posts its
interrupts through a cascaded auxiliary interrupt controller. A character
device driver may want to pass regs to the sysrq handler through the input
layer which adds another few layers of parameter passing.
I've build this code with allyesconfig for x86_64 and i386. I've runtested the
main part of the code on FRV and i386, though I can't test most of the drivers.
I've also done partial conversion for powerpc and MIPS - these at least compile
with minimal configurations.
This will affect all archs. Mostly the changes should be relatively easy.
Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
struct pt_regs *old_regs = set_irq_regs(regs);
And put the old one back at the end:
set_irq_regs(old_regs);
Don't pass regs through to generic_handle_irq() or __do_IRQ().
In timer_interrupt(), this sort of change will be necessary:
- update_process_times(user_mode(regs));
- profile_tick(CPU_PROFILING, regs);
+ update_process_times(user_mode(get_irq_regs()));
+ profile_tick(CPU_PROFILING);
I'd like to move update_process_times()'s use of get_irq_regs() into itself,
except that i386, alone of the archs, uses something other than user_mode().
Some notes on the interrupt handling in the drivers:
(*) input_dev() is now gone entirely. The regs pointer is no longer stored in
the input_dev struct.
(*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
something different depending on whether it's been supplied with a regs
pointer or not.
(*) Various IRQ handler function pointers have been moved to type
irq_handler_t.
Signed-Off-By: David Howells <dhowells@redhat.com>
(cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
2006-10-05 20:55:46 +07:00
|
|
|
static irqreturn_t phy_interrupt(int irq, void *phy_dat)
|
2005-08-25 06:46:21 +07:00
|
|
|
{
|
|
|
|
struct phy_device *phydev = phy_dat;
|
|
|
|
|
2006-10-03 22:18:35 +07:00
|
|
|
if (PHY_HALTED == phydev->state)
|
|
|
|
return IRQ_NONE; /* It can't be ours. */
|
|
|
|
|
2005-08-25 06:46:21 +07:00
|
|
|
disable_irq_nosync(irq);
|
2007-09-29 12:42:14 +07:00
|
|
|
atomic_inc(&phydev->irq_disable);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
2016-10-17 00:56:51 +07:00
|
|
|
phy_change(phydev);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
|
|
|
return IRQ_HANDLED;
|
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_enable_interrupts - Enable the interrupts from the PHY side
|
|
|
|
* @phydev: target phy_device struct
|
|
|
|
*/
|
2010-10-21 15:37:41 +07:00
|
|
|
static int phy_enable_interrupts(struct phy_device *phydev)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
2014-01-05 07:23:19 +07:00
|
|
|
int err = phy_clear_interrupt(phydev);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2005-08-25 06:46:21 +07:00
|
|
|
if (err < 0)
|
|
|
|
return err;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2014-01-05 07:23:19 +07:00
|
|
|
return phy_config_interrupt(phydev, PHY_INTERRUPT_ENABLED);
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_disable_interrupts - Disable the PHY interrupts from the PHY side
|
|
|
|
* @phydev: target phy_device struct
|
|
|
|
*/
|
2010-10-21 15:37:41 +07:00
|
|
|
static int phy_disable_interrupts(struct phy_device *phydev)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
/* Disable PHY interrupts */
|
|
|
|
err = phy_config_interrupt(phydev, PHY_INTERRUPT_DISABLED);
|
|
|
|
if (err)
|
|
|
|
goto phy_err;
|
|
|
|
|
|
|
|
/* Clear the interrupt */
|
|
|
|
err = phy_clear_interrupt(phydev);
|
|
|
|
if (err)
|
|
|
|
goto phy_err;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
phy_err:
|
|
|
|
phy_error(phydev);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
2005-08-25 06:46:21 +07:00
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_start_interrupts - request and enable interrupts for a PHY device
|
|
|
|
* @phydev: target phy_device struct
|
2005-08-25 06:46:21 +07:00
|
|
|
*
|
2007-03-06 17:41:48 +07:00
|
|
|
* Description: Request the interrupt for the given PHY.
|
|
|
|
* If this fails, then we set irq to PHY_POLL.
|
2005-08-25 06:46:21 +07:00
|
|
|
* Otherwise, we enable the interrupts in the PHY.
|
|
|
|
* This should only be called with a valid IRQ number.
|
2007-03-06 17:41:48 +07:00
|
|
|
* Returns 0 on success or < 0 on error.
|
2005-08-25 06:46:21 +07:00
|
|
|
*/
|
|
|
|
int phy_start_interrupts(struct phy_device *phydev)
|
|
|
|
{
|
2007-09-29 12:42:14 +07:00
|
|
|
atomic_set(&phydev->irq_disable, 0);
|
2016-10-17 00:56:50 +07:00
|
|
|
if (request_threaded_irq(phydev->irq, NULL, phy_interrupt,
|
|
|
|
IRQF_ONESHOT | IRQF_SHARED,
|
2016-10-17 00:56:52 +07:00
|
|
|
phydev_name(phydev), phydev) < 0) {
|
2012-06-09 14:49:07 +07:00
|
|
|
pr_warn("%s: Can't get IRQ %d (PHY)\n",
|
2016-01-07 02:11:16 +07:00
|
|
|
phydev->mdio.bus->name, phydev->irq);
|
2005-08-25 06:46:21 +07:00
|
|
|
phydev->irq = PHY_POLL;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2014-01-05 07:21:52 +07:00
|
|
|
return phy_enable_interrupts(phydev);
|
2005-08-25 06:46:21 +07:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_start_interrupts);
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_stop_interrupts - disable interrupts from a PHY device
|
|
|
|
* @phydev: target phy_device struct
|
|
|
|
*/
|
2005-08-25 06:46:21 +07:00
|
|
|
int phy_stop_interrupts(struct phy_device *phydev)
|
|
|
|
{
|
2014-01-05 07:23:19 +07:00
|
|
|
int err = phy_disable_interrupts(phydev);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
|
|
|
if (err)
|
|
|
|
phy_error(phydev);
|
|
|
|
|
2007-09-29 12:42:14 +07:00
|
|
|
free_irq(phydev->irq, phydev);
|
|
|
|
|
2014-01-05 07:17:06 +07:00
|
|
|
/* If work indeed has been cancelled, disable_irq() will have
|
2007-09-29 12:42:14 +07:00
|
|
|
* been left unbalanced from phy_interrupt() and enable_irq()
|
|
|
|
* has to be called so that other devices on the line work.
|
|
|
|
*/
|
|
|
|
while (atomic_dec_return(&phydev->irq_disable) >= 0)
|
|
|
|
enable_irq(phydev->irq);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_stop_interrupts);
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
2016-10-17 00:56:51 +07:00
|
|
|
* phy_change - Called by the phy_interrupt to handle PHY changes
|
|
|
|
* @phydev: phy_device struct that interrupted
|
2007-03-06 17:41:48 +07:00
|
|
|
*/
|
2016-10-17 00:56:51 +07:00
|
|
|
void phy_change(struct phy_device *phydev)
|
2005-08-25 06:46:21 +07:00
|
|
|
{
|
2016-01-19 10:33:07 +07:00
|
|
|
if (phy_interrupt_is_valid(phydev)) {
|
|
|
|
if (phydev->drv->did_interrupt &&
|
|
|
|
!phydev->drv->did_interrupt(phydev))
|
|
|
|
goto ignore;
|
2009-04-07 09:01:42 +07:00
|
|
|
|
2016-01-19 10:33:07 +07:00
|
|
|
if (phy_disable_interrupts(phydev))
|
|
|
|
goto phy_err;
|
|
|
|
}
|
2005-08-25 06:46:21 +07:00
|
|
|
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_lock(&phydev->lock);
|
2005-08-25 06:46:21 +07:00
|
|
|
if ((PHY_RUNNING == phydev->state) || (PHY_NOLINK == phydev->state))
|
|
|
|
phydev->state = PHY_CHANGELINK;
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_unlock(&phydev->lock);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
2016-01-19 10:33:07 +07:00
|
|
|
if (phy_interrupt_is_valid(phydev)) {
|
|
|
|
atomic_dec(&phydev->irq_disable);
|
|
|
|
enable_irq(phydev->irq);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
2016-01-19 10:33:07 +07:00
|
|
|
/* Reenable interrupts */
|
|
|
|
if (PHY_HALTED != phydev->state &&
|
|
|
|
phy_config_interrupt(phydev, PHY_INTERRUPT_ENABLED))
|
|
|
|
goto irq_enable_err;
|
|
|
|
}
|
2005-08-25 06:46:21 +07:00
|
|
|
|
2009-03-14 05:41:19 +07:00
|
|
|
/* reschedule state queue work to run as soon as possible */
|
2017-01-21 06:31:52 +07:00
|
|
|
phy_trigger_machine(phydev, true);
|
2005-08-25 06:46:21 +07:00
|
|
|
return;
|
|
|
|
|
2009-04-07 09:01:42 +07:00
|
|
|
ignore:
|
|
|
|
atomic_dec(&phydev->irq_disable);
|
|
|
|
enable_irq(phydev->irq);
|
|
|
|
return;
|
|
|
|
|
2005-08-25 06:46:21 +07:00
|
|
|
irq_enable_err:
|
|
|
|
disable_irq(phydev->irq);
|
2007-09-29 12:42:14 +07:00
|
|
|
atomic_inc(&phydev->irq_disable);
|
2005-08-25 06:46:21 +07:00
|
|
|
phy_err:
|
|
|
|
phy_error(phydev);
|
|
|
|
}
|
|
|
|
|
2016-10-17 00:56:51 +07:00
|
|
|
/**
|
|
|
|
* phy_change_work - Scheduled by the phy_mac_interrupt to handle PHY changes
|
|
|
|
* @work: work_struct that describes the work to be done
|
|
|
|
*/
|
|
|
|
void phy_change_work(struct work_struct *work)
|
|
|
|
{
|
|
|
|
struct phy_device *phydev =
|
|
|
|
container_of(work, struct phy_device, phy_queue);
|
|
|
|
|
|
|
|
phy_change(phydev);
|
|
|
|
}
|
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_stop - Bring down the PHY link, and stop checking the status
|
|
|
|
* @phydev: target phy_device struct
|
|
|
|
*/
|
2005-08-25 06:46:21 +07:00
|
|
|
void phy_stop(struct phy_device *phydev)
|
|
|
|
{
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_lock(&phydev->lock);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
|
|
|
if (PHY_HALTED == phydev->state)
|
|
|
|
goto out_unlock;
|
|
|
|
|
2013-05-20 05:53:42 +07:00
|
|
|
if (phy_interrupt_is_valid(phydev)) {
|
2005-08-25 06:46:21 +07:00
|
|
|
/* Disable PHY Interrupts */
|
|
|
|
phy_config_interrupt(phydev, PHY_INTERRUPT_DISABLED);
|
|
|
|
|
2006-10-03 22:18:35 +07:00
|
|
|
/* Clear any pending interrupts */
|
|
|
|
phy_clear_interrupt(phydev);
|
|
|
|
}
|
2005-08-25 06:46:21 +07:00
|
|
|
|
2007-09-29 12:42:15 +07:00
|
|
|
phydev->state = PHY_HALTED;
|
|
|
|
|
2005-08-25 06:46:21 +07:00
|
|
|
out_unlock:
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_unlock(&phydev->lock);
|
2006-10-03 22:18:35 +07:00
|
|
|
|
2014-01-05 07:17:06 +07:00
|
|
|
/* Cannot call flush_scheduled_work() here as desired because
|
2006-10-03 22:18:35 +07:00
|
|
|
* of rtnl_lock(), but PHY_HALTED shall guarantee phy_change()
|
|
|
|
* will not reenable interrupts.
|
|
|
|
*/
|
2005-08-25 06:46:21 +07:00
|
|
|
}
|
2014-01-05 07:17:06 +07:00
|
|
|
EXPORT_SYMBOL(phy_stop);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
2007-03-06 17:41:48 +07:00
|
|
|
/**
|
|
|
|
* phy_start - start or restart a PHY device
|
|
|
|
* @phydev: target phy_device struct
|
2005-08-25 06:46:21 +07:00
|
|
|
*
|
2007-03-06 17:41:48 +07:00
|
|
|
* Description: Indicates the attached device's readiness to
|
2005-08-25 06:46:21 +07:00
|
|
|
* handle PHY-related work. Used during startup to start the
|
|
|
|
* PHY, and after a call to phy_stop() to resume operation.
|
|
|
|
* Also used to indicate the MDIO bus has cleared an error
|
|
|
|
* condition.
|
|
|
|
*/
|
|
|
|
void phy_start(struct phy_device *phydev)
|
|
|
|
{
|
2015-05-18 10:38:38 +07:00
|
|
|
bool do_resume = false;
|
|
|
|
int err = 0;
|
|
|
|
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_lock(&phydev->lock);
|
2005-08-25 06:46:21 +07:00
|
|
|
|
|
|
|
switch (phydev->state) {
|
2013-12-18 12:38:12 +07:00
|
|
|
case PHY_STARTING:
|
|
|
|
phydev->state = PHY_PENDING;
|
|
|
|
break;
|
|
|
|
case PHY_READY:
|
|
|
|
phydev->state = PHY_UP;
|
|
|
|
break;
|
|
|
|
case PHY_HALTED:
|
2015-05-18 10:38:38 +07:00
|
|
|
/* make sure interrupts are re-enabled for the PHY */
|
2016-05-10 16:42:26 +07:00
|
|
|
if (phydev->irq != PHY_POLL) {
|
|
|
|
err = phy_enable_interrupts(phydev);
|
|
|
|
if (err < 0)
|
|
|
|
break;
|
|
|
|
}
|
2015-05-18 10:38:38 +07:00
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
phydev->state = PHY_RESUMING;
|
2015-05-18 10:38:38 +07:00
|
|
|
do_resume = true;
|
|
|
|
break;
|
2013-12-18 12:38:12 +07:00
|
|
|
default:
|
|
|
|
break;
|
2005-08-25 06:46:21 +07:00
|
|
|
}
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_unlock(&phydev->lock);
|
2015-05-18 10:38:38 +07:00
|
|
|
|
|
|
|
/* if phy was suspended, bring the physical link up again */
|
|
|
|
if (do_resume)
|
|
|
|
phy_resume(phydev);
|
net: phy: Trigger state machine on state change and not polling.
The phy_start() is used to indicate the PHY is now ready to do its
work. The state is changed, normally to PHY_UP which means that both
the MAC and the PHY are ready.
If the phy driver is using polling, when the next poll happens, the
state machine notices the PHY is now in PHY_UP, and kicks off
auto-negotiation, if needed.
If however, the PHY is using interrupts, there is no polling. The phy
is stuck in PHY_UP until the next interrupt comes along. And there is
no reason for the PHY to interrupt.
Have phy_start() schedule the state machine to run, which both speeds
up the polling use case, and makes the interrupt use case actually
work.
This problems exists whenever there is a state change which will not
cause an interrupt. Trigger the state machine in these cases,
e.g. phy_error().
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Cc: Kyle Roeschley <kyle.roeschley@ni.com>
Tested-by: Kyle Roeschley <kyle.roeschley@ni.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-10-13 03:14:53 +07:00
|
|
|
|
2017-01-21 06:31:52 +07:00
|
|
|
phy_trigger_machine(phydev, true);
|
2005-08-25 06:46:21 +07:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_start);
|
2005-08-11 13:07:25 +07:00
|
|
|
|
2016-10-17 22:49:53 +07:00
|
|
|
static void phy_adjust_link(struct phy_device *phydev)
|
|
|
|
{
|
|
|
|
phydev->adjust_link(phydev->attached_dev);
|
2016-10-17 22:49:55 +07:00
|
|
|
phy_led_trigger_change_speed(phydev);
|
2016-10-17 22:49:53 +07:00
|
|
|
}
|
|
|
|
|
2008-01-29 23:05:09 +07:00
|
|
|
/**
|
|
|
|
* phy_state_machine - Handle the state machine
|
|
|
|
* @work: work_struct that describes the work to be done
|
|
|
|
*/
|
2010-01-18 12:37:16 +07:00
|
|
|
void phy_state_machine(struct work_struct *work)
|
2005-07-31 06:31:23 +07:00
|
|
|
{
|
2009-04-03 06:56:54 +07:00
|
|
|
struct delayed_work *dwork = to_delayed_work(work);
|
2008-01-29 23:05:09 +07:00
|
|
|
struct phy_device *phydev =
|
2009-03-14 05:41:19 +07:00
|
|
|
container_of(dwork, struct phy_device, state_queue);
|
2015-05-18 10:38:38 +07:00
|
|
|
bool needs_aneg = false, do_suspend = false;
|
2015-05-17 00:17:56 +07:00
|
|
|
enum phy_state old_state;
|
2005-07-31 06:31:23 +07:00
|
|
|
int err = 0;
|
2015-08-14 11:23:40 +07:00
|
|
|
int old_link;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_lock(&phydev->lock);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2015-05-17 00:17:56 +07:00
|
|
|
old_state = phydev->state;
|
|
|
|
|
2017-02-18 07:07:34 +07:00
|
|
|
if (phydev->drv && phydev->drv->link_change_notify)
|
2014-06-18 16:01:41 +07:00
|
|
|
phydev->drv->link_change_notify(phydev);
|
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
switch (phydev->state) {
|
|
|
|
case PHY_DOWN:
|
|
|
|
case PHY_STARTING:
|
|
|
|
case PHY_READY:
|
|
|
|
case PHY_PENDING:
|
|
|
|
break;
|
|
|
|
case PHY_UP:
|
2014-05-15 12:35:34 +07:00
|
|
|
needs_aneg = true;
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
phydev->link_timeout = PHY_AN_TIMEOUT;
|
|
|
|
|
|
|
|
break;
|
|
|
|
case PHY_AN:
|
|
|
|
err = phy_read_status(phydev);
|
|
|
|
if (err < 0)
|
2005-07-31 06:31:23 +07:00
|
|
|
break;
|
2006-10-17 04:19:17 +07:00
|
|
|
|
2014-01-05 07:17:06 +07:00
|
|
|
/* If the link is down, give up on negotiation for now */
|
2013-12-18 12:38:12 +07:00
|
|
|
if (!phydev->link) {
|
|
|
|
phydev->state = PHY_NOLINK;
|
|
|
|
netif_carrier_off(phydev->attached_dev);
|
2016-10-17 22:49:53 +07:00
|
|
|
phy_adjust_link(phydev);
|
2013-12-18 12:38:12 +07:00
|
|
|
break;
|
|
|
|
}
|
2006-10-17 04:19:17 +07:00
|
|
|
|
2014-01-05 07:17:06 +07:00
|
|
|
/* Check if negotiation is done. Break if there's an error */
|
2013-12-18 12:38:12 +07:00
|
|
|
err = phy_aneg_done(phydev);
|
|
|
|
if (err < 0)
|
|
|
|
break;
|
2006-10-17 04:19:17 +07:00
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
/* If AN is done, we're running */
|
|
|
|
if (err > 0) {
|
|
|
|
phydev->state = PHY_RUNNING;
|
|
|
|
netif_carrier_on(phydev->attached_dev);
|
2016-10-17 22:49:53 +07:00
|
|
|
phy_adjust_link(phydev);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2014-04-09 10:33:45 +07:00
|
|
|
} else if (0 == phydev->link_timeout--)
|
2014-05-15 12:35:34 +07:00
|
|
|
needs_aneg = true;
|
2013-12-18 12:38:12 +07:00
|
|
|
break;
|
|
|
|
case PHY_NOLINK:
|
2015-11-17 05:36:46 +07:00
|
|
|
if (phy_interrupt_is_valid(phydev))
|
|
|
|
break;
|
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
err = phy_read_status(phydev);
|
|
|
|
if (err)
|
2005-07-31 06:31:23 +07:00
|
|
|
break;
|
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
if (phydev->link) {
|
2014-04-24 09:52:47 +07:00
|
|
|
if (AUTONEG_ENABLE == phydev->autoneg) {
|
|
|
|
err = phy_aneg_done(phydev);
|
|
|
|
if (err < 0)
|
|
|
|
break;
|
|
|
|
|
|
|
|
if (!err) {
|
|
|
|
phydev->state = PHY_AN;
|
|
|
|
phydev->link_timeout = PHY_AN_TIMEOUT;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2013-12-18 12:38:12 +07:00
|
|
|
phydev->state = PHY_RUNNING;
|
|
|
|
netif_carrier_on(phydev->attached_dev);
|
2016-10-17 22:49:53 +07:00
|
|
|
phy_adjust_link(phydev);
|
2013-12-18 12:38:12 +07:00
|
|
|
}
|
|
|
|
break;
|
|
|
|
case PHY_FORCING:
|
|
|
|
err = genphy_update_link(phydev);
|
|
|
|
if (err)
|
2005-07-31 06:31:23 +07:00
|
|
|
break;
|
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
if (phydev->link) {
|
|
|
|
phydev->state = PHY_RUNNING;
|
|
|
|
netif_carrier_on(phydev->attached_dev);
|
|
|
|
} else {
|
|
|
|
if (0 == phydev->link_timeout--)
|
2014-05-15 12:35:34 +07:00
|
|
|
needs_aneg = true;
|
2013-12-18 12:38:12 +07:00
|
|
|
}
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2016-10-17 22:49:53 +07:00
|
|
|
phy_adjust_link(phydev);
|
2013-12-18 12:38:12 +07:00
|
|
|
break;
|
|
|
|
case PHY_RUNNING:
|
2016-01-19 10:33:06 +07:00
|
|
|
/* Only register a CHANGE if we are polling and link changed
|
|
|
|
* since latest checking.
|
2013-12-18 12:38:12 +07:00
|
|
|
*/
|
2016-01-19 10:33:06 +07:00
|
|
|
if (phydev->irq == PHY_POLL) {
|
2015-08-14 11:23:40 +07:00
|
|
|
old_link = phydev->link;
|
|
|
|
err = phy_read_status(phydev);
|
|
|
|
if (err)
|
|
|
|
break;
|
|
|
|
|
|
|
|
if (old_link != phydev->link)
|
|
|
|
phydev->state = PHY_CHANGELINK;
|
|
|
|
}
|
2017-01-06 18:14:48 +07:00
|
|
|
/*
|
|
|
|
* Failsafe: check that nobody set phydev->link=0 between two
|
|
|
|
* poll cycles, otherwise we won't leave RUNNING state as long
|
|
|
|
* as link remains down.
|
|
|
|
*/
|
|
|
|
if (!phydev->link && phydev->state == PHY_RUNNING) {
|
|
|
|
phydev->state = PHY_CHANGELINK;
|
|
|
|
phydev_err(phydev, "no link in PHY_RUNNING\n");
|
|
|
|
}
|
2013-12-18 12:38:12 +07:00
|
|
|
break;
|
|
|
|
case PHY_CHANGELINK:
|
|
|
|
err = phy_read_status(phydev);
|
|
|
|
if (err)
|
2005-07-31 06:31:23 +07:00
|
|
|
break;
|
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
if (phydev->link) {
|
|
|
|
phydev->state = PHY_RUNNING;
|
|
|
|
netif_carrier_on(phydev->attached_dev);
|
|
|
|
} else {
|
|
|
|
phydev->state = PHY_NOLINK;
|
|
|
|
netif_carrier_off(phydev->attached_dev);
|
|
|
|
}
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2016-10-17 22:49:53 +07:00
|
|
|
phy_adjust_link(phydev);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
if (phy_interrupt_is_valid(phydev))
|
|
|
|
err = phy_config_interrupt(phydev,
|
2014-01-05 07:17:06 +07:00
|
|
|
PHY_INTERRUPT_ENABLED);
|
2013-12-18 12:38:12 +07:00
|
|
|
break;
|
|
|
|
case PHY_HALTED:
|
|
|
|
if (phydev->link) {
|
|
|
|
phydev->link = 0;
|
|
|
|
netif_carrier_off(phydev->attached_dev);
|
2016-10-17 22:49:53 +07:00
|
|
|
phy_adjust_link(phydev);
|
2014-05-15 12:35:34 +07:00
|
|
|
do_suspend = true;
|
2013-12-18 12:38:12 +07:00
|
|
|
}
|
|
|
|
break;
|
|
|
|
case PHY_RESUMING:
|
|
|
|
if (AUTONEG_ENABLE == phydev->autoneg) {
|
|
|
|
err = phy_aneg_done(phydev);
|
|
|
|
if (err < 0)
|
2005-07-31 06:31:23 +07:00
|
|
|
break;
|
|
|
|
|
2013-12-18 12:38:12 +07:00
|
|
|
/* err > 0 if AN is done.
|
2014-01-05 07:17:06 +07:00
|
|
|
* Otherwise, it's 0, and we're still waiting for AN
|
|
|
|
*/
|
2013-12-18 12:38:12 +07:00
|
|
|
if (err > 0) {
|
2009-07-01 20:00:34 +07:00
|
|
|
err = phy_read_status(phydev);
|
|
|
|
if (err)
|
|
|
|
break;
|
|
|
|
|
|
|
|
if (phydev->link) {
|
|
|
|
phydev->state = PHY_RUNNING;
|
|
|
|
netif_carrier_on(phydev->attached_dev);
|
2014-01-05 07:17:06 +07:00
|
|
|
} else {
|
2009-07-01 20:00:34 +07:00
|
|
|
phydev->state = PHY_NOLINK;
|
2014-01-05 07:17:06 +07:00
|
|
|
}
|
2016-10-17 22:49:53 +07:00
|
|
|
phy_adjust_link(phydev);
|
2013-12-18 12:38:12 +07:00
|
|
|
} else {
|
|
|
|
phydev->state = PHY_AN;
|
|
|
|
phydev->link_timeout = PHY_AN_TIMEOUT;
|
2009-07-01 20:00:34 +07:00
|
|
|
}
|
2013-12-18 12:38:12 +07:00
|
|
|
} else {
|
|
|
|
err = phy_read_status(phydev);
|
|
|
|
if (err)
|
|
|
|
break;
|
|
|
|
|
|
|
|
if (phydev->link) {
|
|
|
|
phydev->state = PHY_RUNNING;
|
|
|
|
netif_carrier_on(phydev->attached_dev);
|
2014-01-05 07:17:06 +07:00
|
|
|
} else {
|
2013-12-18 12:38:12 +07:00
|
|
|
phydev->state = PHY_NOLINK;
|
2014-01-05 07:17:06 +07:00
|
|
|
}
|
2016-10-17 22:49:53 +07:00
|
|
|
phy_adjust_link(phydev);
|
2013-12-18 12:38:12 +07:00
|
|
|
}
|
|
|
|
break;
|
2005-07-31 06:31:23 +07:00
|
|
|
}
|
|
|
|
|
2008-01-29 23:05:09 +07:00
|
|
|
mutex_unlock(&phydev->lock);
|
2005-07-31 06:31:23 +07:00
|
|
|
|
|
|
|
if (needs_aneg)
|
2017-04-20 18:00:04 +07:00
|
|
|
err = phy_start_aneg_priv(phydev, false);
|
2014-05-15 12:35:34 +07:00
|
|
|
else if (do_suspend)
|
2013-12-13 16:20:29 +07:00
|
|
|
phy_suspend(phydev);
|
|
|
|
|
2005-07-31 06:31:23 +07:00
|
|
|
if (err < 0)
|
|
|
|
phy_error(phydev);
|
|
|
|
|
2016-01-07 02:11:09 +07:00
|
|
|
phydev_dbg(phydev, "PHY state change %s -> %s\n",
|
|
|
|
phy_state_to_str(old_state),
|
|
|
|
phy_state_to_str(phydev->state));
|
2015-05-17 00:17:56 +07:00
|
|
|
|
2016-01-19 10:33:06 +07:00
|
|
|
/* Only re-schedule a PHY state machine change if we are polling the
|
|
|
|
* PHY, if PHY_IGNORE_INTERRUPT is set, then we will be moving
|
|
|
|
* between states from phy_mac_interrupt()
|
|
|
|
*/
|
|
|
|
if (phydev->irq == PHY_POLL)
|
|
|
|
queue_delayed_work(system_power_efficient_wq, &phydev->state_queue,
|
|
|
|
PHY_STATE_TIME * HZ);
|
2008-01-29 23:05:09 +07:00
|
|
|
}
|
2012-06-28 04:14:38 +07:00
|
|
|
|
2016-10-17 00:56:51 +07:00
|
|
|
/**
|
|
|
|
* phy_mac_interrupt - MAC says the link has changed
|
|
|
|
* @phydev: phy_device struct with changed link
|
|
|
|
* @new_link: Link is Up/Down.
|
|
|
|
*
|
|
|
|
* Description: The MAC layer is able indicate there has been a change
|
|
|
|
* in the PHY link status. Set the new link status, and trigger the
|
|
|
|
* state machine, work a work queue.
|
|
|
|
*/
|
2013-05-20 05:53:43 +07:00
|
|
|
void phy_mac_interrupt(struct phy_device *phydev, int new_link)
|
|
|
|
{
|
|
|
|
phydev->link = new_link;
|
2016-01-19 10:33:07 +07:00
|
|
|
|
|
|
|
/* Trigger a state machine change */
|
|
|
|
queue_work(system_power_efficient_wq, &phydev->phy_queue);
|
2013-05-20 05:53:43 +07:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_mac_interrupt);
|
|
|
|
|
2012-06-28 04:14:38 +07:00
|
|
|
/**
|
|
|
|
* phy_init_eee - init and check the EEE feature
|
|
|
|
* @phydev: target phy_device struct
|
|
|
|
* @clk_stop_enable: PHY may stop the clock during LPI
|
|
|
|
*
|
|
|
|
* Description: it checks if the Energy-Efficient Ethernet (EEE)
|
|
|
|
* is supported by looking at the MMD registers 3.20 and 7.60/61
|
|
|
|
* and it programs the MMD register 3.0 setting the "Clock stop enable"
|
|
|
|
* bit if required.
|
|
|
|
*/
|
|
|
|
int phy_init_eee(struct phy_device *phydev, bool clk_stop_enable)
|
|
|
|
{
|
2017-02-18 07:07:34 +07:00
|
|
|
if (!phydev->drv)
|
|
|
|
return -EIO;
|
|
|
|
|
2012-06-28 04:14:38 +07:00
|
|
|
/* According to 802.3az,the EEE is supported only in full duplex-mode.
|
|
|
|
*/
|
2017-03-31 16:37:18 +07:00
|
|
|
if (phydev->duplex == DUPLEX_FULL) {
|
2012-06-28 04:14:38 +07:00
|
|
|
int eee_lp, eee_cap, eee_adv;
|
|
|
|
u32 lp, cap, adv;
|
2014-03-05 07:35:44 +07:00
|
|
|
int status;
|
2012-06-28 04:14:38 +07:00
|
|
|
|
|
|
|
/* Read phy status to properly get the right settings */
|
|
|
|
status = phy_read_status(phydev);
|
|
|
|
if (status)
|
|
|
|
return status;
|
|
|
|
|
|
|
|
/* First check if the EEE ability is supported */
|
2017-03-21 23:36:53 +07:00
|
|
|
eee_cap = phy_read_mmd(phydev, MDIO_MMD_PCS, MDIO_PCS_EEE_ABLE);
|
2014-08-26 14:26:52 +07:00
|
|
|
if (eee_cap <= 0)
|
|
|
|
goto eee_exit_err;
|
2012-06-28 04:14:38 +07:00
|
|
|
|
2012-08-20 11:55:29 +07:00
|
|
|
cap = mmd_eee_cap_to_ethtool_sup_t(eee_cap);
|
2012-06-28 04:14:38 +07:00
|
|
|
if (!cap)
|
2014-08-26 14:26:52 +07:00
|
|
|
goto eee_exit_err;
|
2012-06-28 04:14:38 +07:00
|
|
|
|
|
|
|
/* Check which link settings negotiated and verify it in
|
|
|
|
* the EEE advertising registers.
|
|
|
|
*/
|
2017-03-21 23:36:53 +07:00
|
|
|
eee_lp = phy_read_mmd(phydev, MDIO_MMD_AN, MDIO_AN_EEE_LPABLE);
|
2014-08-26 14:26:52 +07:00
|
|
|
if (eee_lp <= 0)
|
|
|
|
goto eee_exit_err;
|
2012-06-28 04:14:38 +07:00
|
|
|
|
2017-03-21 23:36:53 +07:00
|
|
|
eee_adv = phy_read_mmd(phydev, MDIO_MMD_AN, MDIO_AN_EEE_ADV);
|
2014-08-26 14:26:52 +07:00
|
|
|
if (eee_adv <= 0)
|
|
|
|
goto eee_exit_err;
|
2012-06-28 04:14:38 +07:00
|
|
|
|
2012-08-20 11:55:29 +07:00
|
|
|
adv = mmd_eee_adv_to_ethtool_adv_t(eee_adv);
|
|
|
|
lp = mmd_eee_adv_to_ethtool_adv_t(eee_lp);
|
2015-02-18 00:36:22 +07:00
|
|
|
if (!phy_check_valid(phydev->speed, phydev->duplex, lp & adv))
|
2014-08-26 14:26:52 +07:00
|
|
|
goto eee_exit_err;
|
2012-06-28 04:14:38 +07:00
|
|
|
|
|
|
|
if (clk_stop_enable) {
|
|
|
|
/* Configure the PHY to stop receiving xMII
|
|
|
|
* clock while it is signaling LPI.
|
|
|
|
*/
|
2017-03-21 23:36:53 +07:00
|
|
|
int val = phy_read_mmd(phydev, MDIO_MMD_PCS, MDIO_CTRL1);
|
2012-06-28 04:14:38 +07:00
|
|
|
if (val < 0)
|
|
|
|
return val;
|
|
|
|
|
|
|
|
val |= MDIO_PCS_CTRL1_CLKSTOP_EN;
|
2017-03-21 23:36:53 +07:00
|
|
|
phy_write_mmd(phydev, MDIO_MMD_PCS, MDIO_CTRL1, val);
|
2012-06-28 04:14:38 +07:00
|
|
|
}
|
|
|
|
|
2014-01-05 07:21:52 +07:00
|
|
|
return 0; /* EEE supported */
|
2012-06-28 04:14:38 +07:00
|
|
|
}
|
2014-08-26 14:26:52 +07:00
|
|
|
eee_exit_err:
|
2014-01-05 07:21:52 +07:00
|
|
|
return -EPROTONOSUPPORT;
|
2012-06-28 04:14:38 +07:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_init_eee);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* phy_get_eee_err - report the EEE wake error count
|
|
|
|
* @phydev: target phy_device struct
|
|
|
|
*
|
|
|
|
* Description: it is to report the number of time where the PHY
|
|
|
|
* failed to complete its normal wake sequence.
|
|
|
|
*/
|
|
|
|
int phy_get_eee_err(struct phy_device *phydev)
|
|
|
|
{
|
2017-02-18 07:07:34 +07:00
|
|
|
if (!phydev->drv)
|
|
|
|
return -EIO;
|
|
|
|
|
2017-03-21 23:36:53 +07:00
|
|
|
return phy_read_mmd(phydev, MDIO_MMD_PCS, MDIO_PCS_EEE_WK_ERR);
|
2012-06-28 04:14:38 +07:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_get_eee_err);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* phy_ethtool_get_eee - get EEE supported and status
|
|
|
|
* @phydev: target phy_device struct
|
|
|
|
* @data: ethtool_eee data
|
|
|
|
*
|
|
|
|
* Description: it reportes the Supported/Advertisement/LP Advertisement
|
|
|
|
* capabilities.
|
|
|
|
*/
|
|
|
|
int phy_ethtool_get_eee(struct phy_device *phydev, struct ethtool_eee *data)
|
|
|
|
{
|
|
|
|
int val;
|
|
|
|
|
2017-02-18 07:07:34 +07:00
|
|
|
if (!phydev->drv)
|
|
|
|
return -EIO;
|
|
|
|
|
2012-06-28 04:14:38 +07:00
|
|
|
/* Get Supported EEE */
|
2017-03-21 23:36:53 +07:00
|
|
|
val = phy_read_mmd(phydev, MDIO_MMD_PCS, MDIO_PCS_EEE_ABLE);
|
2012-06-28 04:14:38 +07:00
|
|
|
if (val < 0)
|
|
|
|
return val;
|
2012-08-20 11:55:29 +07:00
|
|
|
data->supported = mmd_eee_cap_to_ethtool_sup_t(val);
|
2012-06-28 04:14:38 +07:00
|
|
|
|
|
|
|
/* Get advertisement EEE */
|
2017-03-21 23:36:53 +07:00
|
|
|
val = phy_read_mmd(phydev, MDIO_MMD_AN, MDIO_AN_EEE_ADV);
|
2012-06-28 04:14:38 +07:00
|
|
|
if (val < 0)
|
|
|
|
return val;
|
2012-08-20 11:55:29 +07:00
|
|
|
data->advertised = mmd_eee_adv_to_ethtool_adv_t(val);
|
2012-06-28 04:14:38 +07:00
|
|
|
|
|
|
|
/* Get LP advertisement EEE */
|
2017-03-21 23:36:53 +07:00
|
|
|
val = phy_read_mmd(phydev, MDIO_MMD_AN, MDIO_AN_EEE_LPABLE);
|
2012-06-28 04:14:38 +07:00
|
|
|
if (val < 0)
|
|
|
|
return val;
|
2012-08-20 11:55:29 +07:00
|
|
|
data->lp_advertised = mmd_eee_adv_to_ethtool_adv_t(val);
|
2012-06-28 04:14:38 +07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_ethtool_get_eee);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* phy_ethtool_set_eee - set EEE supported and status
|
|
|
|
* @phydev: target phy_device struct
|
|
|
|
* @data: ethtool_eee data
|
|
|
|
*
|
|
|
|
* Description: it is to program the Advertisement EEE register.
|
|
|
|
*/
|
|
|
|
int phy_ethtool_set_eee(struct phy_device *phydev, struct ethtool_eee *data)
|
|
|
|
{
|
2017-03-31 16:37:12 +07:00
|
|
|
int cap, old_adv, adv, ret;
|
2012-06-28 04:14:38 +07:00
|
|
|
|
2017-02-18 07:07:34 +07:00
|
|
|
if (!phydev->drv)
|
|
|
|
return -EIO;
|
|
|
|
|
2017-03-31 16:37:07 +07:00
|
|
|
/* Get Supported EEE */
|
|
|
|
cap = phy_read_mmd(phydev, MDIO_MMD_PCS, MDIO_PCS_EEE_ABLE);
|
|
|
|
if (cap < 0)
|
|
|
|
return cap;
|
2016-11-28 16:46:46 +07:00
|
|
|
|
2017-03-31 16:37:12 +07:00
|
|
|
old_adv = phy_read_mmd(phydev, MDIO_MMD_AN, MDIO_AN_EEE_ADV);
|
|
|
|
if (old_adv < 0)
|
|
|
|
return old_adv;
|
|
|
|
|
2017-03-31 16:37:07 +07:00
|
|
|
adv = ethtool_adv_to_mmd_eee_adv_t(data->advertised) & cap;
|
2012-06-28 04:14:38 +07:00
|
|
|
|
2017-03-31 16:37:07 +07:00
|
|
|
/* Mask prohibited EEE modes */
|
|
|
|
adv &= ~phydev->eee_broken_modes;
|
|
|
|
|
2017-03-31 16:37:12 +07:00
|
|
|
if (old_adv != adv) {
|
|
|
|
ret = phy_write_mmd(phydev, MDIO_MMD_AN, MDIO_AN_EEE_ADV, adv);
|
|
|
|
if (ret < 0)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
/* Restart autonegotiation so the new modes get sent to the
|
|
|
|
* link partner.
|
|
|
|
*/
|
|
|
|
ret = genphy_restart_aneg(phydev);
|
|
|
|
if (ret < 0)
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
2012-06-28 04:14:38 +07:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_ethtool_set_eee);
|
2013-03-11 20:56:44 +07:00
|
|
|
|
|
|
|
int phy_ethtool_set_wol(struct phy_device *phydev, struct ethtool_wolinfo *wol)
|
|
|
|
{
|
2017-02-18 07:07:34 +07:00
|
|
|
if (phydev->drv && phydev->drv->set_wol)
|
2013-03-11 20:56:44 +07:00
|
|
|
return phydev->drv->set_wol(phydev, wol);
|
|
|
|
|
|
|
|
return -EOPNOTSUPP;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_ethtool_set_wol);
|
|
|
|
|
|
|
|
void phy_ethtool_get_wol(struct phy_device *phydev, struct ethtool_wolinfo *wol)
|
|
|
|
{
|
2017-02-18 07:07:34 +07:00
|
|
|
if (phydev->drv && phydev->drv->get_wol)
|
2013-03-11 20:56:44 +07:00
|
|
|
phydev->drv->get_wol(phydev, wol);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_ethtool_get_wol);
|
2016-05-10 05:19:41 +07:00
|
|
|
|
|
|
|
int phy_ethtool_get_link_ksettings(struct net_device *ndev,
|
|
|
|
struct ethtool_link_ksettings *cmd)
|
|
|
|
{
|
|
|
|
struct phy_device *phydev = ndev->phydev;
|
|
|
|
|
|
|
|
if (!phydev)
|
|
|
|
return -ENODEV;
|
|
|
|
|
|
|
|
return phy_ethtool_ksettings_get(phydev, cmd);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_ethtool_get_link_ksettings);
|
|
|
|
|
|
|
|
int phy_ethtool_set_link_ksettings(struct net_device *ndev,
|
|
|
|
const struct ethtool_link_ksettings *cmd)
|
|
|
|
{
|
|
|
|
struct phy_device *phydev = ndev->phydev;
|
|
|
|
|
|
|
|
if (!phydev)
|
|
|
|
return -ENODEV;
|
|
|
|
|
|
|
|
return phy_ethtool_ksettings_set(phydev, cmd);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_ethtool_set_link_ksettings);
|
2016-11-16 01:06:30 +07:00
|
|
|
|
|
|
|
int phy_ethtool_nway_reset(struct net_device *ndev)
|
|
|
|
{
|
|
|
|
struct phy_device *phydev = ndev->phydev;
|
|
|
|
|
|
|
|
if (!phydev)
|
|
|
|
return -ENODEV;
|
|
|
|
|
2017-02-18 07:07:34 +07:00
|
|
|
if (!phydev->drv)
|
|
|
|
return -EIO;
|
|
|
|
|
2016-11-16 01:06:30 +07:00
|
|
|
return genphy_restart_aneg(phydev);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(phy_ethtool_nway_reset);
|