From: Ong Boon Leong <boon.leong.ong@intel.com>
To: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 2/2] net: phy: dp83867: add generic PHY loopback
Date: Wed, 13 Oct 2021 11:41:28 +0800 [thread overview]
Message-ID: <20211013034128.2094426-3-boon.leong.ong@intel.com> (raw)
In-Reply-To: <20211013034128.2094426-1-boon.leong.ong@intel.com>
From: "Lay, Kuan Loon" <kuan.loon.lay@intel.com>
TI DP83867 supports loopback enabled using BMCR, so we add
genphy_loopback to the phy driver.
Tested-by: Clement <clement@intel.com>
Signed-off-by: Lay, Kuan Loon <kuan.loon.lay@intel.com>
Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com>
---
drivers/net/phy/dp83867.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/phy/dp83867.c b/drivers/net/phy/dp83867.c
index bb4369b75179..af47c62d6e04 100644
--- a/drivers/net/phy/dp83867.c
+++ b/drivers/net/phy/dp83867.c
@@ -878,6 +878,7 @@ static struct phy_driver dp83867_driver[] = {
.suspend = genphy_suspend,
.resume = genphy_resume,
+ .set_loopback = genphy_loopback,
},
};
module_phy_driver(dp83867_driver);
--
2.25.1
next prev parent reply other threads:[~2021-10-13 3:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 3:41 [PATCH net-next 0/2] net: phy: dp83867 non-OF and loopback support Ong Boon Leong
2021-10-13 3:41 ` [PATCH net-next 1/2] net: phy: dp83867: introduce critical chip default init for non-of platform Ong Boon Leong
2021-10-19 18:51 ` Andrew Lunn
2021-10-13 3:41 ` Ong Boon Leong [this message]
2021-10-13 3:48 ` [PATCH net-next 2/2] net: phy: dp83867: add generic PHY loopback Wong Vee Khee
2021-10-13 6:18 ` Ong, Boon Leong
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=20211013034128.2094426-3-boon.leong.ong@intel.com \
--to=boon.leong.ong@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®