From: Ezequiel Garcia <ezequiel@collabora.com>
To: Philipp Zabel <p.zabel@pengutronix.de>, linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
kernel@pengutronix.de, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 0/4] Add initial i.MX8MQ support
Date: Mon, 23 Mar 2020 19:41:45 -0300 [thread overview]
Message-ID: <db57d62e189b4578aec20280d69b893797588c3d.camel@collabora.com> (raw)
In-Reply-To: <20200320131256.23294-1-p.zabel@pengutronix.de>
Hi Philipp,
Tested on the EVK, looks great.
On Fri, 2020-03-20 at 14:12 +0100, Philipp Zabel wrote:
> With the i.MX8MQ decoders in active use and the i.MX8MM power domain
> support still up in the air, I think it makes sense to merge i.MX8MQ
> Hantro support now and accept that i.MX8MM may or may not require
> different bindings.
>
> Patch 4 depends on [2] for the MAINTAINERS change.
>
Thanks a lot for stepping up and helping to maintain
the driver!
For all patches:
Reviewed-by: Ezequiel Garcia <ezequiel@collabora.com>
> Changes since v5 [1]:
> - Drop merged patches
> - Drop i.MX8MM bindings
> - Change example node name to video-codec
> - Convert i.MX8MQ bindings to YAML
> - Drop i.MX8MM support
> - Rebase onto media/master
> - Enable h.264 and VP8 decoding
> - Enable post-processing
>
> [1] https://lore.kernel.org/linux-media/20190612093915.18973-1-p.zabel@pengutronix.de
> [2] https://lore.kernel.org/linux-media/20200318132108.21873-9-ezequiel@collabora.com
>
> regards
> Philipp
>
> Philipp Zabel (4):
> media: dt-bindings: Document i.MX8MQ VPU bindings
> media: hantro: add initial i.MX8MQ support
> arm64: dts: imx8mq: enable Hantro G1/G2 VPU
> media: MAINTAINERS: add myself to co-maintain Hantro G1/G2 for i.MX8MQ
>
> .../bindings/media/nxp,imx8mq-vpu.yaml | 77 ++++++
> MAINTAINERS | 2 +
> arch/arm64/boot/dts/freescale/imx8mq.dtsi | 27 +++
> drivers/staging/media/hantro/Kconfig | 16 +-
> drivers/staging/media/hantro/Makefile | 3 +
> drivers/staging/media/hantro/hantro_drv.c | 3 +
> drivers/staging/media/hantro/hantro_hw.h | 1 +
> drivers/staging/media/hantro/imx8m_vpu_hw.c | 220 ++++++++++++++++++
> 8 files changed, 345 insertions(+), 4 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.yaml
> create mode 100644 drivers/staging/media/hantro/imx8m_vpu_hw.c
>
prev parent reply other threads:[~2020-03-23 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 13:12 [PATCH v6 0/4] Add initial i.MX8MQ support Philipp Zabel
2020-03-20 13:12 ` [PATCH v6 1/4] media: dt-bindings: Document i.MX8MQ VPU bindings Philipp Zabel
2020-03-20 17:25 ` Rob Herring
2020-03-20 13:12 ` [PATCH v6 2/4] media: hantro: add initial i.MX8MQ support Philipp Zabel
2020-03-20 13:12 ` [PATCH v6 3/4] arm64: dts: imx8mq: enable Hantro G1/G2 VPU Philipp Zabel
2020-05-27 16:19 ` Philipp Zabel
2020-05-28 1:02 ` Ezequiel Garcia
2020-06-10 0:19 ` Ezequiel Garcia
2020-06-16 14:07 ` Shawn Guo
2020-03-20 13:12 ` [PATCH v6 4/4] media: MAINTAINERS: add myself to co-maintain Hantro G1/G2 for i.MX8MQ Philipp Zabel
2020-03-23 22:41 ` Ezequiel Garcia [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=db57d62e189b4578aec20280d69b893797588c3d.camel@collabora.com \
--to=ezequiel@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).