From: Daniel Almeida <daniel.almeida@collabora.com>
Date: Tue, 29 Jul 2025 17:31:41 +0000 (-0300)
Subject: rust: regulator: implement Send and Sync for Regulator<T>
X-Git-Tag: v6.18-rc1~166^2~18^2
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9a200cbdb54349909a42b45379e792e4b39dd223;p=thirdparty%2Flinux.git

rust: regulator: implement Send and Sync for Regulator<T>

Sending a &Regulator<T> to another thread is safe, as the regulator core
will properly handle the locking for us. Additionally, there are no
restrictions that prevents sending a Regulator<T> to another thread.

Given these two facts, implement Send and Sync.

Signed-off-by: Daniel Almeida <daniel.almeida@collabora.com>
Link: https://patch.msgid.link/20250729-regulator-send-sync-v1-2-8bcbd546b940@collabora.com
Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---

diff --git a/rust/kernel/regulator.rs b/rust/kernel/regulator.rs
index d56aa229e838c..704147e18bfc9 100644
--- a/rust/kernel/regulator.rs
+++ b/rust/kernel/regulator.rs
@@ -398,6 +398,14 @@ impl<T: RegulatorState> Drop for Regulator<T> {
     }
 }
 
+// SAFETY: It is safe to send a `Regulator<T>` across threads. In particular, a
+// Regulator<T> can be dropped from any thread.
+unsafe impl<T: RegulatorState> Send for Regulator<T> {}
+
+// SAFETY: It is safe to send a &Regulator<T> across threads because the C side
+// handles its own locking.
+unsafe impl<T: RegulatorState> Sync for Regulator<T> {}
+
 /// A voltage.
 ///
 /// This type represents a voltage value in microvolts.