From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Vincent ABRIOU <vincent.abriou@st.com>,
"kernel@stlinux.com" <kernel@stlinux.com>,
Fabien DESSENNE <fabien.dessenne@st.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH] drm: Set depth and bpp for XRGB4444 family formats
Date: Wed, 10 Aug 2016 20:11:11 +0300 [thread overview]
Message-ID: <20160810171111.GV4329@intel.com> (raw)
In-Reply-To: <CAKMK7uE9Ee4dnxZ0G5fMNnVYzUBCWWpLmOOQDeDgiSQrYSw4Dw@mail.gmail.com>
On Wed, Aug 10, 2016 at 06:57:02PM +0200, Daniel Vetter wrote:
> On Wed, Aug 10, 2016 at 5:26 PM, Fabien DESSENNE <fabien.dessenne@st.com> wrote:
> > On 08/10/2016 04:12 PM, Daniel Vetter wrote:
> >> On Wed, Aug 10, 2016 at 01:04:54PM +0200, Fabien DESSENNE wrote:
> >>> On 08/10/2016 12:35 PM, Daniel Vetter wrote:
> >>>> On Wed, Aug 10, 2016 at 11:21:56AM +0200, Fabien Dessenne wrote:
> >>>>> These pixel formats are supported by format_check() from drm_crtc.c, so
> >>>>> provide there depth and bpp.
> >>>>>
> >>>>> Signed-off-by: Fabien Dessenne <fabien.dessenne@st.com>
> >>>> Why?
> >>> At least for consistency between format_check() and drm_fb_get_bpp_depth().
> >> fb_get_bpp_depth is kinda legacy, the recommended way is to have a switch
> >> statement in your driver that directly decodes DRM_FORMAT_* into driver
> >> register values. The inconsistency is intentional since just looking at
> >> bpp and depth removes a lot of information.
> > I can understand that fb_get_bpp_depth() shall not be called by (new)
> > drivers.
> > But it is also called by the core part through drm_format_plane_cpp()
> > which is not a legacy interface and is used across many drivers (I think
> > that this is a recent change initiated by Ville).
>
> I've dug around and the only places I've found changes is from 2012. I
> think rgb444 formats just plain never worked. But in case I've missed
> something and this is a regression then indeed we need to fix it.
Looks like I just plain forgot about these formats when I added
drm_format_plane_cpp().
> For
> the real solution it's better to sync up with Laurent and his plans to
> rework the fourcc handling we have in drm.
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-10 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 9:21 [PATCH] drm: Set depth and bpp for XRGB4444 family formats Fabien Dessenne
2016-08-10 10:35 ` Daniel Vetter
2016-08-10 11:04 ` Fabien DESSENNE
2016-08-10 14:12 ` Daniel Vetter
2016-08-10 15:26 ` Fabien DESSENNE
2016-08-10 16:57 ` Daniel Vetter
2016-08-10 17:11 ` Ville Syrjälä [this message]
2016-08-19 9:01 ` Fabien DESSENNE
2016-09-09 9:09 ` Laurent Pinchart
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=20160810171111.GV4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabien.dessenne@st.com \
--cc=kernel@stlinux.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=vincent.abriou@st.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.