Hi Andy,
On Tue, 17 Dec 2024 at 00:41, Andy Yan <andyshrk@xxxxxxx> wrote:
> At 2024-12-16 21:06:07, "Daniel Stone" <daniel@xxxxxxxxxxxxx> wrote:
> >On Sat, 14 Dec 2024 at 08:18, Andy Yan <andyshrk@xxxxxxx> wrote:
> >> This is the only afbc format supported by the upcoming
> >> VOP for rk3576.
> >>
> >> Add support for it.
> >
> >Out of interest, how was this tested? There is no 32x8 modifier in the
> >format list in format_modifiers_afbc[], so it seems like it shouldn't
> >be possible to get a 32x8 buffer on a plane at all.
>
> The 32x8 modifier added in PATCH 16/16:
>
> +/* used from rk3576, afbc 32*8 half mode */
> +static const uint64_t format_modifiers_rk3576_afbc[] = {
> + DRM_FORMAT_MOD_ARM_AFBC(AFBC_FORMAT_MOD_BLOCK_SIZE_32x8 |
> + AFBC_FORMAT_MOD_SPLIT),
> +
Hmmm, that's strange; I applied the whole series with b4 but wasn't
seeing that block defined. Maybe a bad conflict resolution. Sorry for
the confusion.
> I write an ovltest[0] tool which can take linear/AFBC rgb/yuv data from a file, then
> commit to drm driver, I use this tool for most basic format test.
>
> But when tested on weston, I found that weston does not use the AFBC format for display,
> don't know why.
You'll need a Mesa tree with e0f48568c7f2 included; if you have this
then it should just work out of the box.
Cheers,
Daniel
