DRM driver and runtime suspend-resume handling?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
While working with CRTC color related properties (gamma and CTM for
instance) and making them persistent over suspend-resume cycle it
occurred to me if I am just wasting resources by storing the property
values in the driver and restoring them in dev_pm_ops runtime_resume()..

Wouldn't it work if I would just:

1. Add a flag in the driver to indicate that the context may have been
lost since the previous atomic commit and set in runtime_resume().

2. And write the color properties to HW if the context lost flag is set
even if the drm_crtc_state color_mgmt_changed is false.

The color property values are there despite the color_mgmt_changed ==
false, aren't they?

Best regards,
Jyri

-- 
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel



[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux