From: Hugues FRUCHET <hugues.fruchet@foss.st.com>
To: Alex Bee <knaerzche@gmail.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>
Cc: Marco Felsch <m.felsch@pengutronix.de>,
Adam Ford <aford173@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Andrzej Pietrasiewicz <andrzej.p@collabora.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Benjamin Mugnier <benjamin.mugnier@foss.st.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
<linux-kernel@vger.kernel.org>,
Daniel Almeida <daniel.almeida@collabora.com>,
Heiko Stuebner <heiko@sntech.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>,
<devicetree@vger.kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
<linux-media@vger.kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: [PATCH v5 0/5] Add support for video hardware codec of STMicroelectronics STM32 SoC series
Date: Tue, 9 Jan 2024 10:24:43 +0100 [thread overview]
Message-ID: <1c76d85c-6f20-4971-a6df-61e4c534b351@foss.st.com> (raw)
In-Reply-To: <e5ba1e14-4bbf-43e3-933a-fee6d4b90641@gmail.com>
Hi Alex,
v6 sent with all the variants in a single file.
Best regards,
Hugues.
On 12/21/23 14:31, Alex Bee wrote:
> Hi Hugues,
>
> Am 21.12.23 um 14:08 schrieb Hugues FRUCHET:
>> Hi Alex,
>>
>> This is because VDEC and VENC are two separated IPs with their own
>> hardware resources and no links between both.
>> On future SoCs, VDEC can ship on its own, same for VENC.
>>
> I think that's what the driver is/was designed for :)
>
> I don't think there _has_ to be a link between variants in the same file.
> For Rockchip we only had the issue that there _is_ a link (shared
> resources) between encoder and decoder and they had (for that reason) to be
> defined has a _single_ variant. And there is no reason you can ship decoder
> and encoder seperated when you have two variants (with different
> compatibles).
> For Rockchip and iMX those files are even containing variants for completly
> different generations / different SoCs. I had to cleanup this mess for
> Rockchip once - and it was no fun :) Anyways: It's up to the maintainers I
> guess - I just wanted to ask if I missunderstand something here.
>
> Greetings,
>
> Alex
>
>> Hoping that this clarify.
>>
>> Best regards,
>> Hugues.
>>
>> On 12/21/23 13:40, Alex Bee wrote:
>>> Hi Hugues, Hi Nicolas,
>>>
>>> is there any specific reason I'm not understanding / seeing why this
>>> is added in two seperate vdec* / venc* files and not a single vpu*
>>> file? Is it only for the seperate clocks (-names) / irqs (-names) /
>>> callbacks? Those are defined per variant and perfectly fit in a
>>> single file holding one vdec and one venc variant.
>>>
>>> Alex
>>>
>>> Am 21.12.23 um 09:47 schrieb Hugues Fruchet:
>>>> This patchset introduces support for VDEC video hardware decoder
>>>> and VENC video hardware encoder of STMicroelectronics STM32MP25
>>>> SoC series.
>>>>
>>>> This initial support implements H264 decoding, VP8 decoding and
>>>> JPEG encoding.
>>>>
>>>> This has been tested on STM32MP257F-EV1 evaluation board.
>>>>
>>>> ===========
>>>> = history =
>>>> ===========
>>>> version 5:
>>>> - Precise that video decoding as been successfully tested up to
>>>> full HD
>>>> - Add Nicolas Dufresne reviewed-by
>>>>
>>>> version 4:
>>>> - Fix comments from Nicolas about dropping encoder raw steps
>>>>
>>>> version 3:
>>>> - Fix remarks from Krzysztof Kozlowski:
>>>> - drop "items", we keep simple enum in such case
>>>> - drop second example - it is the same as the first
>>>> - Drop unused node labels as suggested by Conor Dooley
>>>> - Revisit min/max resolutions as suggested by Nicolas Dufresne
>>>>
>>>> version 2:
>>>> - Fix remarks from Krzysztof Kozlowski on v1:
>>>> - single video-codec binding for both VDEC/VENC
>>>> - get rid of "-names"
>>>> - use of generic node name "video-codec"
>>>>
>>>> version 1:
>>>> - Initial submission
>>>>
>>>> Hugues Fruchet (5):
>>>> dt-bindings: media: Document STM32MP25 VDEC & VENC video codecs
>>>> media: hantro: add support for STM32MP25 VDEC
>>>> media: hantro: add support for STM32MP25 VENC
>>>> arm64: dts: st: add video decoder support to stm32mp255
>>>> arm64: dts: st: add video encoder support to stm32mp255
>>>>
>>>> .../media/st,stm32mp25-video-codec.yaml | 50 ++++++++
>>>> arch/arm64/boot/dts/st/stm32mp251.dtsi | 12 ++
>>>> arch/arm64/boot/dts/st/stm32mp255.dtsi | 17 +++
>>>> drivers/media/platform/verisilicon/Kconfig | 14 ++-
>>>> drivers/media/platform/verisilicon/Makefile | 4 +
>>>> .../media/platform/verisilicon/hantro_drv.c | 4 +
>>>> .../media/platform/verisilicon/hantro_hw.h | 2 +
>>>> .../platform/verisilicon/stm32mp25_vdec_hw.c | 92 ++++++++++++++
>>>> .../platform/verisilicon/stm32mp25_venc_hw.c | 115
>>>> ++++++++++++++++++
>>>> 9 files changed, 307 insertions(+), 3 deletions(-)
>>>> create mode 100644
>>>> Documentation/devicetree/bindings/media/st,stm32mp25-video-codec.yaml
>>>> create mode 100644
>>>> drivers/media/platform/verisilicon/stm32mp25_vdec_hw.c
>>>> create mode 100644
>>>> drivers/media/platform/verisilicon/stm32mp25_venc_hw.c
>>>>
>>>
prev parent reply other threads:[~2024-01-09 9:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 8:47 [PATCH v5 0/5] Add support for video hardware codec of STMicroelectronics STM32 SoC series Hugues Fruchet
2023-12-21 8:47 ` [PATCH v5 1/5] dt-bindings: media: Document STM32MP25 VDEC & VENC video codecs Hugues Fruchet
2023-12-21 9:08 ` Krzysztof Kozlowski
2023-12-21 8:47 ` [PATCH v5 2/5] media: hantro: add support for STM32MP25 VDEC Hugues Fruchet
2023-12-21 11:18 ` Sebastian Fricke
2023-12-21 8:47 ` [PATCH v5 3/5] media: hantro: add support for STM32MP25 VENC Hugues Fruchet
2023-12-21 11:18 ` Sebastian Fricke
2023-12-21 13:05 ` Hugues FRUCHET
2023-12-21 8:47 ` [PATCH v5 4/5] arm64: dts: st: add video decoder support to stm32mp255 Hugues Fruchet
2023-12-21 8:47 ` [PATCH v5 5/5] arm64: dts: st: add video encoder " Hugues Fruchet
2023-12-21 12:40 ` [PATCH v5 0/5] Add support for video hardware codec of STMicroelectronics STM32 SoC series Alex Bee
2023-12-21 13:08 ` Hugues FRUCHET
2023-12-21 13:31 ` Alex Bee
2023-12-21 13:38 ` Adam Ford
2023-12-21 13:46 ` Alex Bee
2023-12-21 13:55 ` Hugues FRUCHET
2023-12-21 14:18 ` Alex Bee
2024-01-09 9:24 ` Hugues FRUCHET [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=1c76d85c-6f20-4971-a6df-61e4c534b351@foss.st.com \
--to=hugues.fruchet@foss.st.com \
--cc=aford173@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrzej.p@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=benjamin.mugnier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=knaerzche@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=m.felsch@pengutronix.de \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.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).