From: Fabio Estevam <festevam@gmail.com>
To: kuba@kernel.org
Cc: davem@davemloft.net, andrew@lunn.ch, netdev@vger.kernel.org,
Fabio Estevam <festevam@denx.de>
Subject: [PATCH net-next 2/2] net: phy: micrel: Use the kszphy probe/suspend/resume
Date: Fri, 13 May 2022 08:46:13 -0300 [thread overview]
Message-ID: <20220513114613.762810-2-festevam@gmail.com> (raw)
In-Reply-To: <20220513114613.762810-1-festevam@gmail.com>
From: Fabio Estevam <festevam@denx.de>
Now that it is possible to use .probe without having .driver_data, let
KSZ8061 use the kszphy specific hooks for probe,suspend and resume,
which is preferred.
Switch to using the dedicated kszphy probe/suspend/resume functions.
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
drivers/net/phy/micrel.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
index 5e356e23c1b7..22139901f01c 100644
--- a/drivers/net/phy/micrel.c
+++ b/drivers/net/phy/micrel.c
@@ -3019,11 +3019,12 @@ static struct phy_driver ksphy_driver[] = {
.name = "Micrel KSZ8061",
.phy_id_mask = MICREL_PHY_ID_MASK,
/* PHY_BASIC_FEATURES */
+ .probe = kszphy_probe,
.config_init = ksz8061_config_init,
.config_intr = kszphy_config_intr,
.handle_interrupt = kszphy_handle_interrupt,
- .suspend = genphy_suspend,
- .resume = genphy_resume,
+ .suspend = kszphy_suspend,
+ .resume = kszphy_resume,
}, {
.phy_id = PHY_ID_KSZ9021,
.phy_id_mask = 0x000ffffe,
--
2.25.1
next prev parent reply other threads:[~2022-05-13 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 11:46 [PATCH net-next 1/2] net: phy: micrel: Allow probing without .driver_data Fabio Estevam
2022-05-13 11:46 ` Fabio Estevam [this message]
2022-05-13 19:37 ` [PATCH net-next 2/2] net: phy: micrel: Use the kszphy probe/suspend/resume Andrew Lunn
2022-05-13 19:36 ` [PATCH net-next 1/2] net: phy: micrel: Allow probing without .driver_data Andrew Lunn
2022-05-16 20:10 ` patchwork-bot+netdevbpf
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=20220513114613.762810-2-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=festevam@denx.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.