From: Artem Lytkin <iprintercanon@gmail.com>
To: netdev@vger.kernel.org, rust-for-linux@vger.kernel.org
Cc: fujita.tomonori@gmail.com, andrew@lunn.ch, hkallweit1@gmail.com,
tmgross@umich.edu, ojeda@kernel.org, dakr@kernel.org
Subject: [PATCH net-next v2 2/5] rust: phy: add paged register access and bit manipulation helpers
Date: Tue, 24 Mar 2026 18:52:46 +0300 [thread overview]
Message-ID: <20260324155249.15098-3-iprintercanon@gmail.com> (raw)
In-Reply-To: <20260324155249.15098-1-iprintercanon@gmail.com>
Add Device methods for register manipulation beyond simple read/write:
- write_paged(): Writes a register on a specific page, completing
the paged access surface (read_paged already existed upstream).
Wraps phy_write_paged().
- modify() / modify_paged(): Atomic read-modify-write operations
that clear bits in mask and set bits in set. Wraps phy_modify()
and phy_modify_paged(). These return Result (not the old register
value) since the C functions return 0 on success.
- set_bits() / clear_bits(): Convenience wrappers around modify()
for the common case of setting or clearing specific bits.
These helpers are heavily used by real-world PHY drivers for
configuring vendor-specific registers without races.
Signed-off-by: Artem Lytkin <iprintercanon@gmail.com>
---
rust/kernel/net/phy.rs | 45 ++++++++++++++++++++++++++++++++++++++++--
1 file changed, 43 insertions(+), 2 deletions(-)
diff --git a/rust/kernel/net/phy.rs b/rust/kernel/net/phy.rs
index 646b2a78a2710..142f7101723c8 100644
--- a/rust/kernel/net/phy.rs
+++ b/rust/kernel/net/phy.rs
@@ -202,8 +202,7 @@ pub fn duplex(&self) -> DuplexMode {
/// Gets the PHY interface mode as a raw `phy_interface_t` value.
///
- /// Common values include `bindings::phy_interface_t_PHY_INTERFACE_MODE_RGMII`,
- /// `bindings::phy_interface_t_PHY_INTERFACE_MODE_SGMII`, etc.
+ /// Values are `bindings::phy_interface_t_PHY_INTERFACE_MODE_*` constants.
/// A typed Rust enum is planned for future work.
pub fn interface(&self) -> u32 {
let phydev = self.0.get();
@@ -241,6 +240,48 @@ pub fn read_paged(&mut self, page: u16, regnum: u16) -> Result<u16> {
to_result(ret).map(|()| ret as u16)
}
+ /// Writes a paged register.
+ pub fn write_paged(&mut self, page: u16, regnum: u16, val: u16) -> Result {
+ let phydev = self.0.get();
+ // SAFETY: `phydev` is pointing to a valid object by the type invariant of `Self`.
+ // So it's just an FFI call.
+ let ret = unsafe { bindings::phy_write_paged(phydev, page.into(), regnum.into(), val) };
+
+ to_result(ret)
+ }
+
+ /// Performs a read-modify-write on a PHY register.
+ ///
+ /// Clears the bits set in `mask` and sets the bits in `set`.
+ pub fn modify(&mut self, regnum: u16, mask: u16, set: u16) -> Result {
+ let phydev = self.0.get();
+ // SAFETY: `phydev` is pointing to a valid object by the type invariant of `Self`.
+ // So it's just an FFI call.
+ to_result(unsafe { bindings::phy_modify(phydev, regnum.into(), mask, set) })
+ }
+
+ /// Performs a read-modify-write on a paged PHY register.
+ ///
+ /// Selects the page, performs the modify, and restores the original page.
+ pub fn modify_paged(&mut self, page: u16, regnum: u16, mask: u16, set: u16) -> Result {
+ let phydev = self.0.get();
+ // SAFETY: `phydev` is pointing to a valid object by the type invariant of `Self`.
+ // So it's just an FFI call.
+ to_result(unsafe {
+ bindings::phy_modify_paged(phydev, page.into(), regnum.into(), mask, set)
+ })
+ }
+
+ /// Sets bits in a PHY register.
+ pub fn set_bits(&mut self, regnum: u16, val: u16) -> Result {
+ self.modify(regnum, 0, val)
+ }
+
+ /// Clears bits in a PHY register.
+ pub fn clear_bits(&mut self, regnum: u16, val: u16) -> Result {
+ self.modify(regnum, val, 0)
+ }
+
/// Resolves the advertisements into PHY settings.
pub fn resolve_aneg_linkmode(&mut self) {
let phydev = self.0.get();
--
2.43.0
next prev parent reply other threads:[~2026-03-24 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 15:52 [PATCH net-next v2 0/5] rust: phy: extend abstractions for real-world PHY drivers Artem Lytkin
2026-03-24 15:52 ` [PATCH net-next v2 1/5] rust: phy: add read-only device field accessors Artem Lytkin
2026-03-24 15:52 ` Artem Lytkin [this message]
2026-03-24 15:52 ` [PATCH net-next v2 3/5] rust: phy: add config_init, read_page, and write_page callbacks Artem Lytkin
2026-03-24 15:52 ` [PATCH net-next v2 4/5] rust: phy: add interrupt support Artem Lytkin
2026-03-24 15:52 ` [PATCH net-next v2 5/5] net: phy: realtek: add Rust RTL8211F PHY driver Artem Lytkin
2026-03-24 15:57 ` 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=20260324155249.15098-3-iprintercanon@gmail.com \
--to=iprintercanon@gmail.com \
--cc=andrew@lunn.ch \
--cc=dakr@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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