From: <Arun.Ramadoss@microchip.com>
To: <olteanv@gmail.com>, <UNGLinuxDriver@microchip.com>,
<vivien.didelot@gmail.com>, <andrew@lunn.ch>,
<f.fainelli@gmail.com>, <kuba@kernel.org>, <wei.fang@nxp.com>,
<edumazet@google.com>, <pabeni@redhat.com>,
<o.rempel@pengutronix.de>, <Woojung.Huh@microchip.com>,
<davem@davemloft.net>, <hkallweit1@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<kernel@pengutronix.de>
Subject: Re: [PATCH net-next v7 1/9] net: dsa: microchip: enable EEE support
Date: Thu, 9 Feb 2023 13:55:17 +0000 [thread overview]
Message-ID: <fc16d1439ea9be10045ab31ecb7f4b6ca45d7fa4.camel@microchip.com> (raw)
In-Reply-To: <20230209095113.364524-2-o.rempel@pengutronix.de>
On Thu, 2023-02-09 at 10:51 +0100, Oleksij Rempel wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> Some of KSZ9477 family switches provides EEE support. To enable it,
> we
> just need to register set_mac_eee/set_mac_eee handlers and validate
> supported chip version and port.
>
> Currently supported chip variants are: KSZ8563, KSZ9477, KSZ9563,
> KSZ9567, KSZ9893, KSZ9896, KSZ9897. KSZ8563 supports EEE only with
> 100BaseTX/Full. Other chips support 100BaseTX/Full and
> 1000BaseTX/Full.
> Low Power Idle configuration is not supported and currently not
> documented in the datasheets.
>
> EEE PHY specific tunings are not documented in the switch datasheets,
> but can
> overlap with KSZ9131 specification.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Acked-by: Arun Ramadoss <arun.ramadoss@microchip.com>
next prev parent reply other threads:[~2023-02-09 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 9:51 [PATCH net-next v7 0/9] net: add EEE support for KSZ9477 and AR8035 with i.MX6 Oleksij Rempel
2023-02-09 9:51 ` [PATCH net-next v7 1/9] net: dsa: microchip: enable EEE support Oleksij Rempel
2023-02-09 13:55 ` Arun.Ramadoss [this message]
2023-02-09 9:51 ` [PATCH net-next v7 2/9] net: phy: add genphy_c45_read_eee_abilities() function Oleksij Rempel
2023-02-09 9:51 ` [PATCH net-next v7 3/9] net: phy: micrel: add ksz9477_get_features() Oleksij Rempel
2023-02-09 9:51 ` [PATCH net-next v7 4/9] net: phy: export phy_check_valid() function Oleksij Rempel
2023-02-10 15:47 ` Alexander H Duyck
2023-02-09 9:51 ` [PATCH net-next v7 5/9] net: phy: add genphy_c45_ethtool_get/set_eee() support Oleksij Rempel
2023-02-10 15:43 ` Alexander H Duyck
2023-02-09 9:51 ` [PATCH net-next v7 6/9] net: phy: c22: migrate to genphy_c45_write_eee_adv() Oleksij Rempel
2023-02-09 9:51 ` [PATCH net-next v7 7/9] net: phy: c45: " Oleksij Rempel
2023-02-09 9:51 ` [PATCH net-next v7 8/9] net: phy: migrate phy_init_eee() to genphy_c45_eee_is_active() Oleksij Rempel
2023-02-09 9:51 ` [PATCH net-next v7 9/9] net: phy: start using genphy_c45_ethtool_get/set_eee() Oleksij Rempel
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=fc16d1439ea9be10045ab31ecb7f4b6ca45d7fa4.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=wei.fang@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).