From: Fabien DESSENNE <fabien.dessenne@st.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Vincent ABRIOU <vincent.abriou@st.com>,
"kernel@stlinux.com" <kernel@stlinux.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm: Set depth and bpp for XRGB4444 family formats
Date: Wed, 10 Aug 2016 13:04:54 +0200 [thread overview]
Message-ID: <d2fa2998-fd83-eef6-ab23-e629c58471f7@st.com> (raw)
In-Reply-To: <20160810103520.GD6232@phenom.ffwll.local>
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().
> Who's going to use this?
For the time being, I can see 9 drivers that make more or less use of
this format (amd, atmel-hlcdc, exynos, fsl-dcu, imx, omapdrm, radeon,
rcar-du, sti).
In top of that I am working on a new driver that actually needs this
format, and that does not work without this patch.
> -Daniel
>
>> ---
>> drivers/gpu/drm/drm_fourcc.c | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/drm_fourcc.c b/drivers/gpu/drm/drm_fourcc.c
>> index 0645c85..aa8c909 100644
>> --- a/drivers/gpu/drm/drm_fourcc.c
>> +++ b/drivers/gpu/drm/drm_fourcc.c
>> @@ -80,6 +80,17 @@ void drm_fb_get_bpp_depth(uint32_t format, unsigned int *depth,
>> *depth = 8;
>> *bpp = 8;
>> break;
>> + case DRM_FORMAT_XRGB4444:
>> + case DRM_FORMAT_XBGR4444:
>> + case DRM_FORMAT_RGBX4444:
>> + case DRM_FORMAT_BGRX4444:
>> + case DRM_FORMAT_ARGB4444:
>> + case DRM_FORMAT_ABGR4444:
>> + case DRM_FORMAT_RGBA4444:
>> + case DRM_FORMAT_BGRA4444:
>> + *depth = 12;
>> + *bpp = 16;
>> + break;
>> case DRM_FORMAT_XRGB1555:
>> case DRM_FORMAT_XBGR1555:
>> case DRM_FORMAT_RGBX5551:
>> --
>> 1.9.1
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
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 11:04 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 [this message]
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ä
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=d2fa2998-fd83-eef6-ab23-e629c58471f7@st.com \
--to=fabien.dessenne@st.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@stlinux.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.