mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Gaignard <benjamin.gaignard@collabora.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: p.zabel@pengutronix.de, mchehab@kernel.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, kernel@pengutronix.de,
	linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
	linux-kernel@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v2 0/2] media: verisilicon: fix reference padding issue
Date: Thu, 12 Dec 2024 17:15:11 +0100	[thread overview]
Message-ID: <21db56f1-ee5d-4309-8fa6-5aaf92782885@collabora.com> (raw)
In-Reply-To: <CAOMZO5DgW3YrpMJPCTzQ-LZCopB4tNPoJhyFQrr6RBvbnBu4VA@mail.gmail.com>


Le 12/12/2024 à 17:10, Fabio Estevam a écrit :
> On Thu, Dec 12, 2024 at 12:43 PM Benjamin Gaignard
> <benjamin.gaignard@collabora.com> wrote:
>> Hantro hardware is splited into two parts: the decoder which produce
>> tiled pixels formats and the post-processor which produce raster pixels
>> formats.
>> When post-processor is used the selected pixels format may not have the
>> some padding/stride than the decoder output pixels format. This led to
>> miscomputing chroma and motion vectors offsets so data are overlapping.
>> This series introduce a reference pixels format that decoder use to
>> compute the various needed offsets and size.
>>
>> With this series Fluster for VP9 tests is now 207/305 vs 145/305.
>> HEVC test score isn't impacted by these patches (still 141/147).
>>
>> Version 2:
>> - rebased on top of media-commiter/next
>> - Add reviewed-by tags
>>
>> Benjamin Gaignard (2):
>>    media: verisilicon: Store reference frames pixels format
>>    media: verisilicon: Fix IMX8 native pixels format steps values
> Do both patches deserve a Fixes tag?

There is dependency in around hevc compress feature in post-proc code.
I don't think it could be applied on stable kernel


      reply	other threads:[~2024-12-12 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 15:43 Benjamin Gaignard
2024-12-12 16:10 ` Fabio Estevam
2024-12-12 16:15   ` Benjamin Gaignard [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=21db56f1-ee5d-4309-8fa6-5aaf92782885@collabora.com \
    --to=benjamin.gaignard@collabora.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@collabora.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mchehab@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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

all inboxes | Powered by JetHome®