From: Dejin Zheng <zhengdejin5@gmail.com>
To: andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, allison@lohutok.net,
corbet@lwn.net, alexios.zavras@intel.com, broonie@kernel.org,
tglx@linutronix.de, mchehab+samsung@kernel.org,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Dejin Zheng <zhengdejin5@gmail.com>
Subject: [PATCH net-next v2 6/7] net: phy: introduce phy_read_poll_timeout macro
Date: Fri, 20 Mar 2020 21:34:30 +0800 [thread overview]
Message-ID: <20200320133431.9354-7-zhengdejin5@gmail.com> (raw)
In-Reply-To: <20200320133431.9354-1-zhengdejin5@gmail.com>
it is sometimes necessary to poll a phy register by phy_read()
function until its value satisfies some condition. introduce
phy_read_poll_timeout() macros that do this.
Suggested-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: Dejin Zheng <zhengdejin5@gmail.com>
---
v1 -> v2:
- pass a phydev and a regnum to replace args... parameter in
the phy_read_poll_timeout(), and also handle the
phy_read() function's return error.
include/linux/phy.h | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/include/linux/phy.h b/include/linux/phy.h
index bb351f8b8769..ecee7e436f89 100644
--- a/include/linux/phy.h
+++ b/include/linux/phy.h
@@ -714,6 +714,19 @@ static inline int phy_read(struct phy_device *phydev, u32 regnum)
return mdiobus_read(phydev->mdio.bus, phydev->mdio.addr, regnum);
}
+#define phy_read_poll_timeout(val, cond, sleep_us, timeout_us, phydev, regnum) \
+({ \
+ int ret = 0; \
+ ret = read_poll_timeout(phy_read, val, cond || val < 0, sleep_us, \
+ timeout_us, phydev, regnum); \
+ if (val < 0) \
+ ret = val; \
+ if (ret) \
+ phydev_err(phydev, "%s failed: %d\n", __func__, ret); \
+ ret; \
+})
+
+
/**
* __phy_read - convenience function for reading a given PHY register
* @phydev: the phy_device struct
--
2.25.0
next prev parent reply other threads:[~2020-03-20 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 13:34 [PATCH net-next v2 0/7] introduce read_poll_timeout Dejin Zheng
2020-03-20 13:34 ` [PATCH net-next v2 1/7] iopoll: introduce read_poll_timeout macro Dejin Zheng
2020-03-20 13:34 ` [PATCH net-next v2 2/7] iopoll: redefined readx_poll_timeout macro to simplify the code Dejin Zheng
2020-03-20 13:34 ` [PATCH net-next v2 3/7] net: phy: introduce phy_read_mmd_poll_timeout macro Dejin Zheng
2020-03-21 16:41 ` Andrew Lunn
2020-03-20 13:34 ` [PATCH net-next v2 4/7] net: phy: bcm84881: use phy_read_mmd_poll_timeout() to simplify the code Dejin Zheng
2020-03-20 13:34 ` [PATCH net-next v2 5/7] net: phy: aquantia: " Dejin Zheng
2020-03-20 13:34 ` Dejin Zheng [this message]
2020-03-20 13:34 ` [PATCH net-next v2 7/7] net: phy: use phy_read_poll_timeout() " Dejin Zheng
2020-03-21 16:50 ` [PATCH net-next v2 0/7] introduce read_poll_timeout Andrew Lunn
2020-03-22 3:03 ` Dejin Zheng
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=20200320133431.9354-7-zhengdejin5@gmail.com \
--to=zhengdejin5@gmail.com \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mchehab+samsung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®