From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Mario Kleiner <mario.kleiner.de@gmail.com>
Cc: igt-dev@lists.freedesktop.org, Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] lib/igt_fb: Add support for testing of 16 bpc fixed point formats.
Date: Mon, 3 May 2021 22:43:45 +0300 [thread overview]
Message-ID: <YJBScZmyJylibAjR@intel.com> (raw)
In-Reply-To: <CAEsyxyjE8AzJWm8EsQ7W6kAv4_DN26RFWe7OE3Qc51i4xqT0dA@mail.gmail.com>
On Mon, May 03, 2021 at 09:32:19PM +0200, Mario Kleiner wrote:
> On Mon, May 3, 2021 at 8:48 PM Ville Syrjälä
> <ville.syrjala@linux.intel.com> wrote:
> >
> > On Mon, May 03, 2021 at 08:25:55PM +0200, Mario Kleiner wrote:
> > > This is used to support testing the 16 bpc formats, e.g., via:
> > >
> > > kms_plane --run-subtest pixel-format-pipe-A-planes
> > >
> > > So far this was successfully tested on AMD RavenRidge with DCN-1
> > > display hw.
> > >
> > > The new conversion routines are slightly adapted copies of the
> > > convert_float_to_fp16() and convert_fp16_to_float() functions,
> > > with the conversion math modified for float <-> uint16 instead.
> > >
> > > Signed-off-by: Mario Kleiner <mario.kleiner.de@gmail.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Alex Deucher <alexander.deucher@amd.com>
> > > ---
> > > lib/igt_fb.c | 123 +++++++++++++++++++++++++++++++++++++++++++++++++++
> > > 1 file changed, 123 insertions(+)
> > >
> > > diff --git a/lib/igt_fb.c b/lib/igt_fb.c
> > > index 954e1181..148e6c0f 100644
> > > --- a/lib/igt_fb.c
> > > +++ b/lib/igt_fb.c
> > > @@ -220,6 +220,22 @@ static const struct format_desc_struct {
> > > .cairo_id = CAIRO_FORMAT_RGBA128F, .convert = true,
> > > .num_planes = 1, .plane_bpp = { 64, },
> > > },
> > > + { .name = "XRGB16161616", .depth = -1, .drm_id = DRM_FORMAT_XRGB16161616,
> > > + .cairo_id = CAIRO_FORMAT_RGBA128F, .convert = true,
> > > + .num_planes = 1, .plane_bpp = { 64, },
> > > + },
> > > + { .name = "ARGB16161616", .depth = -1, .drm_id = DRM_FORMAT_ARGB16161616,
> > > + .cairo_id = CAIRO_FORMAT_RGBA128F, .convert = true,
> > > + .num_planes = 1, .plane_bpp = { 64, },
> > > + },
> > > + { .name = "XBGR16161616", .depth = -1, .drm_id = DRM_FORMAT_XBGR16161616,
> > > + .cairo_id = CAIRO_FORMAT_RGBA128F, .convert = true,
> > > + .num_planes = 1, .plane_bpp = { 64, },
> > > + },
> > > + { .name = "ABGR16161616", .depth = -1, .drm_id = DRM_FORMAT_ABGR16161616,
> > > + .cairo_id = CAIRO_FORMAT_RGBA128F, .convert = true,
> > > + .num_planes = 1, .plane_bpp = { 64, },
> > > + },
> > > { .name = "NV12", .depth = -1, .drm_id = DRM_FORMAT_NV12,
> > > .cairo_id = CAIRO_FORMAT_RGB24, .convert = true,
> > > .num_planes = 2, .plane_bpp = { 8, 16, },
> > > @@ -3365,9 +3381,13 @@ static const unsigned char *rgbx_swizzle(uint32_t format)
> > > default:
> > > case DRM_FORMAT_XRGB16161616F:
> > > case DRM_FORMAT_ARGB16161616F:
> > > + case DRM_FORMAT_XRGB16161616:
> > > + case DRM_FORMAT_ARGB16161616:
> > > return swizzle_bgrx;
> > > case DRM_FORMAT_XBGR16161616F:
> > > case DRM_FORMAT_ABGR16161616F:
> > > + case DRM_FORMAT_XBGR16161616:
> > > + case DRM_FORMAT_ABGR16161616:
> > > return swizzle_rgbx;
> > > }
> > > }
> > > @@ -3451,6 +3471,97 @@ static void convert_float_to_fp16(struct fb_convert *cvt)
> > > }
> > > }
> > >
> > > +static void float_to_uint16(const float *f, uint16_t *h, unsigned int num)
> > > +{
> > > + for (int i = 0; i < num; i++)
> > > + h[i] = f[i] * 65535.0f + 0.5f;
> > > +}
> > > +
> > > +static void uint16_to_float(const uint16_t *h, float *f, unsigned int num)
> > > +{
> > > + for (int i = 0; i < num; i++)
> > > + f[i] = ((float) h[i]) / 65535.0f;
> >
> > nit: the cast shouldn't be necessary.
> >
> > Looks good otherwise.
> > Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> Thanks for the quick review. Compiler and test results agree with you :).
>
> However, all other uintsomething_to_float() conversion routines, e.g.,
> for the yuv formats and for fp16_to_float() all use that apparently
> redundant cast, which is why I left it for consistency with the rest
> of the code. And in case those wiser people who wrote those bits may
> know something that i don't see?
>
> Should I change the patch to drop the cast, and resend?
Maybe not be worth the hassl esp. if there are redundant casts all over
anyway. We could do a global pass later to clear them all up, or just
squint and pretend they're not there :P
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2021-05-03 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 18:25 [igt-dev] Add support for testing of 16 bpc fixed point framebuffers Mario Kleiner
2021-05-03 18:25 ` [igt-dev] [PATCH i-g-t 1/2] drm-uapi: Add fourcc's for 16 bpc fixed point framebuffer formats Mario Kleiner
2021-05-03 18:59 ` Ville Syrjälä
2021-05-03 18:25 ` [igt-dev] [PATCH i-g-t 2/2] lib/igt_fb: Add support for testing of 16 bpc fixed point formats Mario Kleiner
2021-05-03 18:47 ` Ville Syrjälä
2021-05-03 19:32 ` Mario Kleiner
2021-05-03 19:43 ` Ville Syrjälä [this message]
2021-05-03 19:47 ` Mario Kleiner
2021-05-03 19:19 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] drm-uapi: Add fourcc's for 16 bpc fixed point framebuffer formats Patchwork
2021-05-04 0:07 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-06-11 4:21 [igt-dev] Add support for testing of 16 bpc fixed point framebuffers. II Mario Kleiner
2021-06-11 4:21 ` [igt-dev] [PATCH i-g-t 2/2] lib/igt_fb: Add support for testing of 16 bpc fixed point formats Mario Kleiner
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=YJBScZmyJylibAjR@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=alexander.deucher@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mario.kleiner.de@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox