Commits on Source (33)
-
Lyude Paul authored
--- V3: * Document why modesetting objects require Send + Sync
-
Lyude Paul authored
* Make `ModeObject` an unsafe trait I was prompted to make this change in response to one of Daniel's comments, as it occurred to me that we need something that ensures that implementers are only returning valid `drm_mode_object` pointers so we have something to put down for the various related safety comments in RcModeObject. Also, update the safety comments there.
-
Lyude Paul authored
V3: * Add safety comments for ModeObject implementation
-
Lyude Paul authored
V3: * Add safety comment for implementation of ModeObject
-
Lyude Paul authored
V3: * Add safety comment for implementation of ModeObject
-
Lyude Paul authored
V3: * Add safety comment to implementation of ModeObject
-
Lyude Paul authored
V3: * Add safety comment to implementation of ModeObject
-
Lyude Paul authored
V3: * Add safety comment to implementation of ModeObject
-
Lyude Paul authored
V3: * Add safety comments for ModeObject implementation
-
Lyude Paul authored
V3: * Add safety comment to ModeObject implementation
-
Lyude Paul authored
-
Lyude Paul authored
-
Lyude Paul authored
-
Lyude Paul authored
-
Lyude Paul authored
-
Lyude Paul authored
-
Lyude Paul authored
-
Lyude Paul authored
-
Lyude Paul authored
* Make AsRawConnector an unsafe trait, we need a guarantee that as_raw() always returns a valid pointer.
-
Lyude Paul authored
* Add safety comments to AsRawConnector implementation
-
Lyude Paul authored
* Make AsRawEncoder unsafe so that we have a guarantee that `as_raw()` always returns a valid pointer.
-
Lyude Paul authored
* Add safety comments for AsRawEncoder
-
Lyude Paul authored
* Make AsRawCrtc unsafe, as we need a guarantee that `as_raw()` will always return a pointer to a valid `drm_crtc`.
-
Lyude Paul authored
* Add safety comments to AsRawCrtc implementation
-
Lyude Paul authored
* Make AsRawPlane unsafe, since we need a guarantee that `as_raw()` always returns a valid pointer to an initialized drm_plane.
-
Lyude Paul authored
* Add safety comments to implementation of AsRawPlane
-
Lyude Paul authored
* Fix typo on KmsImpl documentation
-
Lyude Paul authored
* Add safety comments for ModeObject implementation
-
Lyude Paul authored
V3: * Get rid of Kms, long live KmsDriver After Daniel pointed out that we should just make KmsDriver a supertrait of Driver, it immediately occurred to me that there's no actual need for Kms to be a separate trait at all. So, drop Kms entirely and move its requirements over to KmsDriver.
-
Lyude Paul authored
-
Lyude Paul authored
-
Lyude Paul authored
-
Lyude Paul authored
Showing
- drivers/gpu/drm/rvkms/rvkms.rs 12 additions, 7 deletionsdrivers/gpu/drm/rvkms/rvkms.rs
- rust/kernel/drm/drv.rs 1 addition, 1 deletionrust/kernel/drm/drv.rs
- rust/kernel/drm/kms.rs 30 additions, 28 deletionsrust/kernel/drm/kms.rs
- rust/kernel/drm/kms/atomic.rs 2 additions, 3 deletionsrust/kernel/drm/kms/atomic.rs
- rust/kernel/drm/kms/connector.rs 23 additions, 6 deletionsrust/kernel/drm/kms/connector.rs
- rust/kernel/drm/kms/crtc.rs 22 additions, 5 deletionsrust/kernel/drm/kms/crtc.rs
- rust/kernel/drm/kms/encoder.rs 23 additions, 5 deletionsrust/kernel/drm/kms/encoder.rs
- rust/kernel/drm/kms/framebuffer.rs 5 additions, 1 deletionrust/kernel/drm/kms/framebuffer.rs
- rust/kernel/drm/kms/plane.rs 23 additions, 5 deletionsrust/kernel/drm/kms/plane.rs