Lines Matching full:safety
43 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
58 // SAFETY: The `ptr` is guaranteed by the C code to be valid.
74 // SAFETY: The pointer was created via `dev_pm_opp_init_cpufreq_table`, and is only
183 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
195 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
321 // SAFETY: This is the same token value returned by the C code via `dev_pm_opp_set_config`.
493 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
514 /// SAFETY: Called from C. Inputs must be valid pointers.
523 // SAFETY: 'dev' is guaranteed by the C code to be valid.
527 // SAFETY: 'opp_table' is guaranteed by the C code to be valid.
529 // SAFETY: 'opp' is guaranteed by the C code to be valid.
539 /// SAFETY: Called from C. Inputs must be valid pointers.
548 // SAFETY: 'dev' is guaranteed by the C code to be valid.
552 // SAFETY: 'old_opp' is guaranteed by the C code to be valid.
554 // SAFETY: 'new_opp' is guaranteed by the C code to be valid.
612 /// SAFETY: It is okay to send ownership of [`Table`] across thread boundaries.
615 /// SAFETY: It is okay to access [`Table`] through shared references from other threads because
622 /// # Safety
626 // SAFETY: By the safety requirements, ptr is valid and its refcount will be incremented.
642 // SAFETY: The requirements are satisfied by the existence of the [`Device`] and its safety
662 // SAFETY: The requirements are satisfied by the existence of the [`Device`] and its safety
680 // SAFETY: The requirements are satisfied by the existence of the [`Device`] and its safety
690 // SAFETY: The cpumask is valid and the returned pointer will be owned by the [`Table`]
708 // SAFETY: The cpumask is valid and we took the reference from [`from_of_cpumask`] earlier,
715 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
725 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
733 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
741 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
749 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
757 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
765 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
772 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
790 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
806 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
829 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
837 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
857 // SAFETY: The requirements are satisfied by the existence of [`Device`] and
858 // its safety requirements. The returned pointer will be owned by the new
870 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
876 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
883 // SAFETY: The `ptr` is guaranteed by the C code to be valid.
892 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
896 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
902 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
909 // SAFETY: The `ptr` is guaranteed by the C code to be valid.
921 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
927 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
934 // SAFETY: The `ptr` is guaranteed by the C code to be valid.
941 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
949 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
957 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
971 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
979 // SAFETY: By the type invariants, we know that `self` owns a reference, so it is safe
1036 /// SAFETY: It is okay to send the ownership of [`OPP`] across thread boundaries.
1039 /// SAFETY: It is okay to access [`OPP`] through shared references from other threads because we're
1043 /// SAFETY: The type invariants guarantee that [`OPP`] is always refcounted.
1047 // SAFETY: The existence of a shared reference means that the refcount is nonzero.
1053 // SAFETY: The safety requirements guarantee that the refcount is nonzero.
1064 /// # Safety
1073 // SAFETY: The safety requirements guarantee the validity of the pointer.
1084 /// # Safety
1089 // SAFETY: The caller guarantees that the pointer is not dangling and stays valid for the
1104 // SAFETY: By the type invariants, we know that `self` owns a reference, so it is safe to
1112 // SAFETY: By the type invariants, we know that `self` owns a reference, so it is safe to
1120 // SAFETY: By the type invariants, we know that `self` owns a reference, so it is safe to
1128 // SAFETY: By the type invariants, we know that `self` owns a reference, so it is safe to
1136 // SAFETY: By the type invariants, we know that `self` owns a reference, so it is safe to
1144 // SAFETY: By the type invariants, we know that `self` owns a reference, so it is safe to