netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Andrew Lunn <andrew@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Wei Fang <wei.fang@nxp.com>,
	Heiner Kallweit <hkallweit1@gmail.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, Shenwei Wang <shenwei.wang@nxp.com>,
	Clark Wang <xiaoning.wang@nxp.com>,
	NXP Linux Team <linux-imx@nxp.com>
Subject: [PATCH net-next v1 0/7] make SmartEEE support controllable
Date: Tue, 14 Feb 2023 10:03:07 +0100	[thread overview]
Message-ID: <20230214090314.2026067-1-o.rempel@pengutronix.de> (raw)

Some PHYs (for example AR8035) provide so called SmartEEE support. Which
allows to use EEE with MACs withotu EEE ability.

Since this functionality is usually enabled by default, it may have
negative impact in some use cases (for example PTP). Or even preventing use of
all link modes without PHY driver assistance (for example full range of
half-duplex modes).

To address at leas some of this issues we need to pass EEE ethtool access to
PHY drivers. Which is done in this patch set.

Oleksij Rempel (7):
  net: phy: add driver specific get/set_eee support
  net: phy: at803x: implement ethtool access to SmartEEE functionality
  net: phy: at803x: ar8035: fix EEE support for half duplex links
  net: phy: add PHY specifica flag to signal SmartEEE support
  net: phy: at803x: add PHY_SMART_EEE flag to AR8035
  net: phy: add phy_has_smarteee() helper
  net: fec: add support for PHYs with SmartEEE support

 drivers/net/ethernet/freescale/fec_main.c |  22 +++-
 drivers/net/phy/at803x.c                  | 142 +++++++++++++++++++++-
 drivers/net/phy/phy.c                     |   6 +
 include/linux/phy.h                       |  15 +++
 4 files changed, 175 insertions(+), 10 deletions(-)

-- 
2.30.2


             reply	other threads:[~2023-02-14  9:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  9:03 Oleksij Rempel [this message]
2023-02-14  9:03 ` [PATCH net-next v1 1/7] net: phy: add driver specific get/set_eee support Oleksij Rempel
2023-02-14  9:03 ` [PATCH net-next v1 2/7] net: phy: at803x: implement ethtool access to SmartEEE functionality Oleksij Rempel
2023-02-14  9:03 ` [PATCH net-next v1 3/7] net: phy: at803x: ar8035: fix EEE support for half duplex links Oleksij Rempel
2023-02-14  9:03 ` [PATCH net-next v1 4/7] net: phy: add PHY specifica flag to signal SmartEEE support Oleksij Rempel
2023-02-14  9:03 ` [PATCH net-next v1 5/7] net: phy: at803x: add PHY_SMART_EEE flag to AR8035 Oleksij Rempel
2023-02-14  9:03 ` [PATCH net-next v1 6/7] net: phy: add phy_has_smarteee() helper Oleksij Rempel
2023-02-14  9:03 ` [PATCH net-next v1 7/7] net: fec: add support for PHYs with SmartEEE support Oleksij Rempel
2023-02-14 13:26   ` Andrew Lunn
2023-02-15 14:14     ` Larysa Zaremba
2023-02-16  9:11     ` Oleksij Rempel
2023-02-16 12:49       ` Andrew Lunn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230214090314.2026067-1-o.rempel@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shenwei.wang@nxp.com \
    --cc=wei.fang@nxp.com \
    --cc=xiaoning.wang@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).