Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 570A4C433FE for ; Thu, 16 Dec 2021 23:03:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236749AbhLPXD6 (ORCPT ); Thu, 16 Dec 2021 18:03:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51586 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236223AbhLPXD5 (ORCPT ); Thu, 16 Dec 2021 18:03:57 -0500 Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E1BD9C06173F for ; Thu, 16 Dec 2021 15:03:56 -0800 (PST) Received: by mail-ed1-x530.google.com with SMTP id z7so1005452edc.11 for ; Thu, 16 Dec 2021 15:03:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vanguardiasur-com-ar.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4XGBi9AWqlgW2iEFwQL1/1nQ3YHkq178Ji39UpQv5Mc=; b=5Z/zpo/llfSzl3vtey+5DTAVBphRj7/CDJ9pOYMjp3eqjbJXmr/AEdLxoqB69mFv5j ZpwLQI2rHW7KiiUd8nvbKYaBDF7hBvG1sITJkCnUq2r3HhLPikA52eYtnpIS8WB94HPh K5++om3EAiuvbLWowQ4mrDzb6BJQUbeomwO4G5kkrc/hm8MyeVdr3IdRfWVlRIHsBnB0 SZDB77wt9U079h1sU4FLwKwQ2VBgNHae7A/yaW8mYjJy5az1ZTi8VDdO1vC9woQKGaFc bM2PAcIX0LN3bauj8SGE+llAKBWqtX8LLgNyFd3MnoXhKqBccaqVcOp90/uwWN21dVsC tW1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4XGBi9AWqlgW2iEFwQL1/1nQ3YHkq178Ji39UpQv5Mc=; b=s9bZAFVeLRUT9Q1BvbrCeWuHuf/MoiY2UQbgN4/CGYyAR67KeXuOHjb5vhgev8qL+i 85lY96RAnOes1niyh+Xm22bj75cfiOFB7O6f/o0hWC7wsfRLaq4O0k+vt9zVvTBBfY7y ZSpqGRC5zXa/JWb9e8pMgHbQUdzikwe5ZqEE9ZhKIb+4lX9f1+TLVFYgecrC5R4sP+Zq ofKNcrCjRAdDmsuNewsDaYRD5CMhyD8GCWjkgvjsdIr3S0rZgNzz4RiyR6HvAU31Os7l 0IrdVIx+i9dey0Hwc9w+xkWPwNmw9as/vZXu6eIsEp5HDdcJHS6EVc9sg23C9xumBCuw zeLQ== X-Gm-Message-State: AOAM530nmToxjqOF7sM7Tfgahpiku3mDWkQu8Gs/T1O8U8JyXzalj3PO ZLmSckFaSjCrREZzVu7ifyrMvXKOu2qZRoZgBXNCig== X-Google-Smtp-Source: ABdhPJwik5gP8WcxT/LlRWowNvewmqUiNaIiabdowVwZ57bu4+JUk4W5a8admDXC7cAvMFqmgEIUFgnO/YFxPYict7s= X-Received: by 2002:a17:907:9608:: with SMTP id gb8mr243974ejc.301.1639695835285; Thu, 16 Dec 2021 15:03:55 -0800 (PST) MIME-Version: 1.0 References: <20211216111256.2362683-1-aford173@gmail.com> <20211216111256.2362683-9-aford173@gmail.com> In-Reply-To: From: Ezequiel Garcia Date: Thu, 16 Dec 2021 20:03:43 -0300 Message-ID: Subject: Re: [PATCH V2 08/10] dt-bindings: media: nxp,imx8mq-vpu: Add support for G1 and G2 on imx8mm To: Adam Ford Cc: Rob Herring , linux-media , Abel Vesa , Adam Ford-BE , Benjamin Gaignard , Hans Verkuil , Philipp Zabel , Mauro Carvalho Chehab , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Greg Kroah-Hartman , Lucas Stach , "open list:HANTRO VPU CODEC DRIVER" , devicetree , arm-soc , Linux Kernel Mailing List , "open list:STAGING SUBSYSTEM" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Adam, On Thu, 16 Dec 2021 at 18:21, Adam Ford wrote: > > On Thu, Dec 16, 2021 at 3:07 PM Rob Herring wrote: > > > > On Thu, Dec 16, 2021 at 05:12:53AM -0600, Adam Ford wrote: > > > The i.MX8M mini appears to have a similar G1 and G2 decoder but the > > > post-procesing isn't present, so different compatible flags are requred. > > > > post-processing > > > > > Since all the other parameters are the same with imx8mq, just add > > > the new compatible flags to nxp,imx8mq-vpu.yaml. > > > > > > Signed-off-by: Adam Ford > > > > > > diff --git a/Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.yaml b/Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.yaml > > > index c1e157251de7..b1f24c48c73b 100644 > > > --- a/Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.yaml > > > +++ b/Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.yaml > > > @@ -5,7 +5,7 @@ > > > $id: "http://devicetree.org/schemas/media/nxp,imx8mq-vpu.yaml#" > > > $schema: "http://devicetree.org/meta-schemas/core.yaml#" > > > > > > -title: Hantro G1/G2 VPU codecs implemented on i.MX8MQ SoCs > > > +title: Hantro G1/G2 VPU codecs implemented on i.MX8MQ/i.MX8MM SoCs > > > > Just 'i.MX8' so we don't have to change this everytime? > > Are you OK with i.MX8M? 8MQ, 8MM, and 8MP all appear to have G1 and > G2 decoders. The i.MX8 is different. > > > > > > > > maintainers: > > > - Philipp Zabel > > > @@ -20,6 +20,8 @@ properties: > > > deprecated: true > > > - const: nxp,imx8mq-vpu-g1 > > > - const: nxp,imx8mq-vpu-g2 > > > + - const: nxp,imx8mm-vpu-g1 > > > + - const: nxp,imx8mm-vpu-g2 > > > > Not compatible with the imx8mq variants? > > No, the structures associated with these compatible flags telling the > driver what features are available have options for the post-processor > in the 8MQ which are not present in the 8MM. > Just as G1 and G2 are different blocks, their "post-processor" features are really different too. The G2 core typically produces a tiled format, NV12_4L4, and it an inline post-processor to convert that to linear NV12. How does this work on the 8MM? What pixel format does it produce natively? It's hard to imagine the G2 block doesn't do linear NV12, so I'm inclined to think it has that post-processing feature. Thanks, Ezequiel