diff options
author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2017-12-07 17:32:02 +0300 |
---|---|---|
committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2017-12-08 13:28:15 +0300 |
commit | 7a1530d7f91fe670b8033aadb1db4dae64512abb (patch) | |
tree | 56353400233b3f7c052c383263c57e1b5f80ef8c /drivers/net/wireless/ath/ath9k/ath9k.h | |
parent | b68763741aa29f2541c7ca58bcb0c2bb6cb5f449 (diff) | |
download | linux-7a1530d7f91fe670b8033aadb1db4dae64512abb.tar.xz |
intel/atomic: Stop updating legacy fb parameters
Even fbc isn't using this stuff anymore, so time to remove it.
Cleaning up one small piece of the atomic conversion cruft at the time
...
Quick explanation on why the plane->fb assignment is ok to delete: The
core code takes care of the refcounting and legacy ->fb pointer
updating, but drivers are allowed to update it ahead of time. Most
legacy modeset drivers did that as part of their set_config callback
(since that's how the legacy/crtc helpers worked). In i915 we only
need that to make the fbc code happy.
v2: don't nuke the assignement of intel_crtc->config, I accidentally
set CI ablaze :-) Spotted by Maarten. And better explain why nuking
the ->fb assignement shouldn't set off alarm bells.
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20171207143202.6021-1-daniel.vetter@ffwll.ch
Diffstat (limited to 'drivers/net/wireless/ath/ath9k/ath9k.h')
0 files changed, 0 insertions, 0 deletions