Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210427111526.1772293-1-acourbot@chromium.org> <34782bc5-d891-8eef-d370-6cfcc547166a@xs4all.nl>
In-Reply-To: <34782bc5-d891-8eef-d370-6cfcc547166a@xs4all.nl>
From:   Alexandre Courbot <acourbot@chromium.org>
Date:   Thu, 13 May 2021 17:06:35 +0900
Message-ID: <CAPBb6MVykfSzXEA5_CWBpr84QduNDx24-aaf=0MUfxKcK69N1g@mail.gmail.com>
Subject: Re: [PATCH v4 00/15] media: mtk-vcodec: support for MT8183 decoder
To:     Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc:     Tiffany Lin <tiffany.lin@mediatek.com>,
        Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
        Rob Herring <robh+dt@kernel.org>,
        Yunfei Dong <yunfei.dong@mediatek.com>,
        Mauro Carvalho Chehab <mchehab@kernel.org>,
        Linux Media Mailing List <linux-media@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        "moderated list:ARM/Mediatek SoC support" 
        <linux-mediatek@lists.infradead.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Apr 29, 2021 at 4:35 PM Hans Verkuil <hverkuil-cisco@xs4all.nl> wrote:
>
> On 27/04/2021 13:15, Alexandre Courbot wrote:
> > This series adds support for the stateless API into mtk-vcodec, by first
> > separating the stateful ops into their own source file, and introducing
> > a new set of ops suitable for stateless decoding. As such, support for
> > stateful decoders should remain completely unaffected.
> >
> > This series has been tested with both MT8183 and MT8173. Decoding was
> > working for both chips, and in the case of MT8173 no regression has been
> > noticed.
> >
> > Patches 1-9 add MT8183 support to the decoder using the stateless API.
> > MT8183 only support H.264 acceleration.
> >
> > Patches 10-15 are follow-ups that further improve compliance for the
> > decoder and encoder, by fixing support for commands on both. Patch 11
> > also makes sure that supported H.264 profiles are exported on MT8173.
>
> For a v5 I would recommend that - where possible - these 'improve compliance'
> patches are moved to the beginning of the series. That way they can be picked
> up quickly without having to wait for the whole series to be accepted.

Makes sense, the current order reflects the chronology these patches
have been written, but I agree that improving compliance should be
merged first. Let me try to reorder things a bit.

Cheers,
Alex.