From: Benjamin Gaignard <benjamin.gaignard@collabora.com>
To: Adam Ford <aford173@gmail.com>, linux-media@vger.kernel.org
Cc: ezequiel@vanguardiasur.com.ar, hverkuil@xs4all.nl,
tharvey@gateworks.com, nicolas@ndufresne.ca,
aford@beaconembedded.com, Rob Herring <robh+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-staging@lists.linux.dev
Subject: Re: [RFC V2 0/2] arm64: imx8mm: Enable Hantro VPUs
Date: Wed, 1 Dec 2021 10:27:58 +0100 [thread overview]
Message-ID: <a07677bc-0a18-c910-222d-d6faee3fe5a0@collabora.com> (raw)
In-Reply-To: <20211201013329.15875-1-aford173@gmail.com>
Le 01/12/2021 à 02:33, Adam Ford a écrit :
> The i.MX8M has two Hantro video decoders, called G1 and G2 which appear
> to be related to the video decoders used on the i.MX8MQ, but because of
> how the Mini handles the power domains, the VPU driver does not need to
> handle all the functions, nor does it support the post-processor,
> so a new compatible flag is required.
>
> With the suggestion from Hans Verkuil, I was able to get the G2 splat to go away
> with changes to FORCE_MAX_ZONEORDER, but I found I could also set cma=512M, however
> it's unclear to me if that's an acceptable alternative.
>
> At the suggestion of Ezequiel Garcia and Nicolas Dufresne I have some
> results from Fluster. However, the G2 VPU appears to fail most tests.
>
> ./fluster.py run -dGStreamer-H.264-V4L2SL-Gst1.0
> Ran 90/135 tests successfully in 76.431 secs
>
> ./fluster.py run -d GStreamer-VP8-V4L2SL-Gst1.0
> Ran 55/61 tests successfully in 21.454 secs
>
> ./fluster.py run -d GStreamer-VP9-V4L2SL-Gst1.0
> Ran 0/303 tests successfully in 20.016 secs
>
> Each day seems to show more and more G2 submissions, and gstreamer seems to be
> still working on the VP9, so I am not sure if I should drop G2 as well.
I think it is going in the good direction.
I'm trying to do the same on IMX6MQ but still have hang issue on G2.
Regards,
Benjamin
>
> Adam Ford (2):
> media: hantro: Add support for i.MX8M Mini
> arm64: dts: imx8mm: Enable VPU-G1 and VPU-G2
>
> arch/arm64/boot/dts/freescale/imx8mm.dtsi | 41 +++++++++++++++
> drivers/staging/media/hantro/hantro_drv.c | 2 +
> drivers/staging/media/hantro/hantro_hw.h | 2 +
> drivers/staging/media/hantro/imx8m_vpu_hw.c | 57 +++++++++++++++++++++
> 4 files changed, 102 insertions(+)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-01 9:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 1:33 [RFC V2 0/2] arm64: imx8mm: Enable Hantro VPUs Adam Ford
2021-12-01 1:33 ` [RFC V2 1/2] media: hantro: Add support for i.MX8M Mini Adam Ford
2021-12-01 12:25 ` Ezequiel Garcia
2021-12-01 12:36 ` Adam Ford
2021-12-01 12:58 ` Ezequiel Garcia
2021-12-01 21:03 ` Nicolas Dufresne
2021-12-02 0:58 ` Adam Ford
2021-12-01 1:33 ` [RFC V2 2/2] arm64: dts: imx8mm: Enable VPU-G1 and VPU-G2 Adam Ford
2021-12-01 9:27 ` Benjamin Gaignard [this message]
2021-12-01 17:23 ` [RFC V2 0/2] arm64: imx8mm: Enable Hantro VPUs Tim Harvey
2021-12-01 17:32 ` Lucas Stach
2021-12-01 18:16 ` Tim Harvey
2021-12-01 18:37 ` Lucas Stach
2021-12-01 18:52 ` Adam Ford
2021-12-01 19:04 ` Lucas Stach
2021-12-01 19:27 ` Adam Ford
2021-12-01 20:04 ` Tim Harvey
2021-12-02 1:07 ` Adam Ford
2021-12-02 3:57 ` Adam Ford
2021-12-01 18:21 ` Adam Ford
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=a07677bc-0a18-c910-222d-d6faee3fe5a0@collabora.com \
--to=benjamin.gaignard@collabora.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.com \
/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;
as well as URLs for NNTP newsgroup(s).