summaryrefslogtreecommitdiffstats
path: root/drivers/nfc
diff options
context:
space:
mode:
authorIlia Mirkin <imirkin@alum.mit.edu>2018-02-03 14:11:23 -0500
committerDaniel Vetter <daniel.vetter@ffwll.ch>2018-02-23 13:51:42 +0100
commitc20bb155c2c5acb775f68be5d84fe679687c3c1e (patch)
treefebffbe7b900db3467d757e05e939d2825918d88 /drivers/nfc
parentdfe8db22372873d205c78a9fd5370b1b088a2b87 (diff)
downloadop-kernel-dev-c20bb155c2c5acb775f68be5d84fe679687c3c1e.zip
op-kernel-dev-c20bb155c2c5acb775f68be5d84fe679687c3c1e.tar.gz
drm/nouveau: prefer XBGR2101010 for addfb ioctl
Nouveau only exposes support for XBGR2101010. Prior to the atomic conversion, drm would pass in the wrong format in the framebuffer, but it was always ignored -- both userspace (xf86-video-nouveau) and the kernel driver agreed on the layout, so the fact that the format was wrong didn't matter. With the atomic conversion, nouveau all of a sudden started caring about the exact format, and so the previously-working code in xf86-video-nouveau no longer functioned since the (internally-assigned) format from the addfb ioctl was wrong. This change adds infrastructure to allow a drm driver to specify that it prefers the XBGR format variant for the addfb ioctl, and makes nouveau's nv50 display driver set it. (Prior gens had no support for 30bpp at all.) Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu> Cc: stable@vger.kernel.org # v4.10+ Acked-by: Ben Skeggs <bskeggs@redhat.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: https://patchwork.freedesktop.org/patch/msgid/20180203191123.31507-1-imirkin@alum.mit.edu
Diffstat (limited to 'drivers/nfc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud