public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Adam Ford <aford173@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-arm-kernel@lists.infradead.org,
	Abel Vesa <abel.vesa@nxp.com>,
	Alexander Stein <alexander.stein@ew.tq-group.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Fabio Estevam <festevam@gmail.com>, Jacky Bai <ping.bai@nxp.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Lucas Stach <l.stach@pengutronix.de>,
	Markus Niebel <Markus.Niebel@ew.tq-group.com>,
	NXP Linux Team <linux-imx@nxp.com>, Peng Fan <peng.fan@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Richard Cochran <richardcochran@gmail.com>,
	Richard Zhu <hongxing.zhu@nxp.com>,
	Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH] arm64: dts: imx8mp: Add Hantro G1, G2, VC8000E DT nodes
Date: Sun, 18 Dec 2022 05:21:35 +0100	[thread overview]
Message-ID: <636a2079-76dc-b60c-965e-5fa54ac232f9@denx.de> (raw)
In-Reply-To: <CAHCN7xJKmq3D_btePOfNC2=oSocrEwDPHaZbpjhBkowc15USAg@mail.gmail.com>

On 12/18/22 05:16, Adam Ford wrote:
> On Sat, Dec 17, 2022 at 8:37 PM Marek Vasut <marex@denx.de> wrote:
>>
>> On 12/18/22 02:36, Laurent Pinchart wrote:
>>
>> Hi,
>>
>> [...]
>>
>>>> diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>>> index 34c2c80c47eb5..5040b3a545c32 100644
>>>> --- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>>> +++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>>> @@ -1639,6 +1639,39 @@ gpu2d: gpu@38008000 {
>>>>                       power-domains = <&pgc_gpu2d>;
>>>>               };
>>>>
>>>> +            vpu_g1: video-codec@38300000 {
>>>> +                    compatible = "nxp,imx8mm-vpu-g1";
>>>> +                    reg = <0x38300000 0x10000>;
>>>> +                    interrupts = <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>;
>>>> +                    clocks = <&clk IMX8MP_CLK_VPU_G1_ROOT>;
>>>> +                    assigned-clocks = <&clk IMX8MP_CLK_VPU_G1>;
>>>> +                    assigned-clock-parents = <&clk IMX8MP_VPU_PLL_OUT>;
>>>> +                    assigned-clock-rates = <700000000>;
>>>> +                    power-domains = <&vpumix_blk_ctrl IMX8MP_VPUBLK_PD_G1>;
>>>> +            };
>>>> +
>>>> +            vpu_g2: video-codec@38310000 {
>>>> +                    compatible = "nxp,imx8mq-vpu-g2";
>>>> +                    reg = <0x38310000 0x10000>;
>>>> +                    interrupts = <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>;
>>>> +                    clocks = <&clk IMX8MP_CLK_VPU_G2_ROOT>;
>>>> +                    assigned-clocks = <&clk IMX8MP_CLK_VPU_G2>;
>>>> +                    assigned-clock-parents = <&clk IMX8MP_VPU_PLL_OUT>;
>>>> +                    assigned-clock-rates = <700000000>;
>>>> +                    power-domains = <&vpumix_blk_ctrl IMX8MP_VPUBLK_PD_G2>;
>>>> +            };
>>>> +
>>>> +            vpu_vc8000e: vpu_vc8000e@38320000 {
>>>> +                    compatible = "nxp,imx8mp-vpu-vc8000e";
>>>
>>> I tried to look for the patch that defined this compatible value, but
>>> couldn't find it. Same for driver support. Have they been posted
>>> somewhere ?
>>
>> Not the vc8000e to my knowledge, the other two are upstream.
> 
> For what it's worth, I'm still working on getting my imx8mp up and
> running with a mainline kernel, but the g1 and g2 enumerate:
> 
> [    7.039007] hantro-vpu 38300000.video-codec: registered
> nxp,imx8mm-vpu-g1-dec as /dev/video0
> [    7.054049] hantro-vpu 38310000.video-codec: registered
> nxp,imx8mq-vpu-g2-dec as /dev/video1
> 
> I'm hoping to get a more mainline version of g-streamer to be able to
> do video decoding and run some fluster tests, but I want to get HDMI
> and DSI video working before I'll have more time to spend on the
> decoders.
> If there isn't a driver for the vc8000e, I wonder if it wouldn't make
> sense to post a V2 with just the G1 and G2 decoders enabled.

Let's do that

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-12-18  4:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18  1:06 [PATCH] arm64: dts: imx8mp: Add Hantro G1, G2, VC8000E DT nodes Marek Vasut
2022-12-18  1:36 ` Laurent Pinchart
2022-12-18  2:37   ` Marek Vasut
2022-12-18  4:16     ` Adam Ford
2022-12-18  4:21       ` Marek Vasut [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=636a2079-76dc-b60c-965e-5fa54ac232f9@denx.de \
    --to=marex@denx.de \
    --cc=Markus.Niebel@ew.tq-group.com \
    --cc=abel.vesa@nxp.com \
    --cc=aford173@gmail.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=festevam@gmail.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=l.stach@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=peng.fan@nxp.com \
    --cc=ping.bai@nxp.com \
    --cc=richardcochran@gmail.com \
    --cc=robh+dt@kernel.org \
    --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