diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2016-09-06 15:45:38 +0100 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2016-09-06 17:51:01 +0100 |
| commit | b18c1bb48eb5911bf99fbc5bf6509d4ae06feb9d (patch) | |
| tree | 9879390f0cb3a47a8135dfcece57f312b4522b9d /drivers/gpu/drm/i915/intel_hdmi.c | |
| parent | e320d40022128845dfff900422ea9fd69f576c98 (diff) | |
| download | talos-obmc-linux-b18c1bb48eb5911bf99fbc5bf6509d4ae06feb9d.tar.gz talos-obmc-linux-b18c1bb48eb5911bf99fbc5bf6509d4ae06feb9d.zip | |
drm/i915: Remove 64b mmio write vfuncs
We don't have safe 64-bit mmio writes as they are really split into
2x32-bit writes. This tearing is dangerous as the hardware *will*
operate on the intermediate value, requiring great care when assigning.
(See, for example, i965_write_fence_reg.) As such we don't currently use
them and strongly advise not to us them. Go one step further and remove
the 64-bit write vfuncs.
v2: Add some more details to the comment about why WRITE64 is absent,
and why you need to think twice before using READ64.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20160906144538.4204-1-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/intel_hdmi.c')
0 files changed, 0 insertions, 0 deletions
