From: Daniel Vetter <daniel@ffwll.ch>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: dri-devel@lists.freedesktop.org, daniel.vetter@ffwll.ch,
michel@daenzer.net, imirkin@alum.mit.edu,
Gustavo Padovan <gustavo@padovan.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@linux.ie>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 6/6] drm: move quirk_addfb_prefer_xbgr_30bpp handling to drm_driver_legacy_fb_format too
Date: Sat, 22 Sep 2018 10:58:19 +0200 [thread overview]
Message-ID: <20180922085819.GM11082@phenom.ffwll.local> (raw)
In-Reply-To: <20180921134704.12826-7-kraxel@redhat.com>
On Fri, Sep 21, 2018 at 03:47:04PM +0200, Gerd Hoffmann wrote:
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
> drivers/gpu/drm/drm_fourcc.c | 5 +++++
> drivers/gpu/drm/drm_framebuffer.c | 4 ----
> 2 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_fourcc.c b/drivers/gpu/drm/drm_fourcc.c
> index 7c6d3922ed..90a1c846fc 100644
> --- a/drivers/gpu/drm/drm_fourcc.c
> +++ b/drivers/gpu/drm/drm_fourcc.c
> @@ -121,6 +121,11 @@ uint32_t drm_driver_legacy_fb_format(struct drm_device *dev,
> if (fmt == DRM_FORMAT_XRGB1555)
> fmt = DRM_FORMAT_HOST_XRGB1555;
> }
> +
> + if (dev->mode_config.quirk_addfb_prefer_xbgr_30bpp &&
> + fmt == DRM_FORMAT_XRGB2101010)
> + fmt = DRM_FORMAT_XBGR2101010;
> +
> return fmt;
> }
> EXPORT_SYMBOL(drm_driver_legacy_fb_format);
> diff --git a/drivers/gpu/drm/drm_framebuffer.c b/drivers/gpu/drm/drm_framebuffer.c
> index 1e2126101c..3bf729d0aa 100644
> --- a/drivers/gpu/drm/drm_framebuffer.c
> +++ b/drivers/gpu/drm/drm_framebuffer.c
> @@ -129,10 +129,6 @@ int drm_mode_addfb(struct drm_device *dev, struct drm_mode_fb_cmd *or,
> r.pitches[0] = or->pitch;
> r.handles[0] = or->handle;
>
> - if (dev->mode_config.quirk_addfb_prefer_xbgr_30bpp &&
> - r.pixel_format == DRM_FORMAT_XRGB2101010)
> - r.pixel_format = DRM_FORMAT_XBGR2101010;
> -
> ret = drm_mode_addfb2(dev, &r, file_priv);
> if (ret)
> return ret;
> --
> 2.9.3
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2018-09-22 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180921134704.12826-1-kraxel@redhat.com>
2018-09-21 13:46 ` [PATCH v4 1/6] drm: move native byte order quirk to new drm_driver_legacy_fb_format function Gerd Hoffmann
2018-09-21 13:47 ` [PATCH v4 2/6] drm: use drm_driver_legacy_fb_format in drm_gem_fbdev_fb_create Gerd Hoffmann
2018-09-22 8:58 ` Daniel Vetter
2018-09-21 13:47 ` [PATCH v4 3/6] drm/bochs: fix DRM_FORMAT_* handling for big endian machines Gerd Hoffmann
2018-09-21 13:47 ` [PATCH v4 4/6] drm/bochs: support changing byteorder at mode set time Gerd Hoffmann
2018-09-21 13:47 ` [PATCH v4 5/6] drm/virtio: fix DRM_FORMAT_* handling Gerd Hoffmann
2018-09-21 13:47 ` [PATCH v4 6/6] drm: move quirk_addfb_prefer_xbgr_30bpp handling to drm_driver_legacy_fb_format too Gerd Hoffmann
2018-09-22 8:58 ` Daniel Vetter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180922085819.GM11082@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=imirkin@alum.mit.edu \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michel@daenzer.net \
--cc=sean@poorly.run \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox