From: Hugues FRUCHET <hugues.fruchet@foss.st.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>, <linux-media@vger.kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-rockchip@lists.infradead.org>
Cc: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
Subject: Re: [PATCH 3/7] dt-bindings: media: Document STM32MP25 VENC video encoder
Date: Mon, 9 Oct 2023 16:24:59 +0200 [thread overview]
Message-ID: <fa0e6187-ab7d-bc23-299c-a491c8ff1d8f@foss.st.com> (raw)
In-Reply-To: <1e2a4d87-5478-4655-993d-7f404d507c82@linaro.org>
Hi Krzysztof,
On 10/9/23 15:56, Krzysztof Kozlowski wrote:
> On 09/10/2023 15:49, Hugues FRUCHET wrote:
>> Hi Krzysztof,
>>
>> On 10/5/23 21:45, Krzysztof Kozlowski wrote:
>>> On 04/10/2023 11:15, Hugues Fruchet wrote:
>>>> Add STM32MP25 VENC video encoder bindings.
>>>>
>>>
>>> I don't understand why this binding is separate from video decoder.
>>> Merge them.
>> VDEC and VENC are two independent IPs with their own clock, reset,
>> interrupt & register set, they have their own access to APB/AXI bus.
>> Moreover future chipsets may embed only VENC or VDEC.
>>
>> Hoping that this clarifies the reason of two different bindings.
>
> No, it does not. These are no reasons to have independent bindings,
> except when having actual impact on the bindings. The bindings look
> identical. What are the differences?
I'm sorry but I really don't understand your point, these are two
different IPs with very different registers in it, so why should
I share that in a single binding ?
>
> Best regards,
> Krzysztof
>
BR,
Hugues.
_______________________________________________
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:[~2023-10-09 14:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 9:15 [PATCH 0/7] Add support for video hardware codec of STMicroelectronics STM32 SoC series Hugues Fruchet
2023-10-04 9:15 ` [PATCH 1/7] dt-bindings: media: Document STM32MP25 VDEC video decoder Hugues Fruchet
2023-10-05 19:45 ` Krzysztof Kozlowski
2023-10-09 13:10 ` Hugues FRUCHET
2023-10-04 9:15 ` [PATCH 2/7] media: hantro: add support for STM32MP25 VDEC Hugues Fruchet
2023-10-11 15:21 ` Nicolas Dufresne
2023-10-04 9:15 ` [PATCH 3/7] dt-bindings: media: Document STM32MP25 VENC video encoder Hugues Fruchet
2023-10-04 23:41 ` Adam Ford
2023-10-05 7:44 ` Hugues FRUCHET
2023-10-06 16:27 ` Rob Herring
2023-10-09 13:06 ` Hugues FRUCHET
2023-10-05 19:45 ` Krzysztof Kozlowski
2023-10-09 13:49 ` Hugues FRUCHET
2023-10-09 13:56 ` Krzysztof Kozlowski
2023-10-09 14:24 ` Hugues FRUCHET [this message]
2023-10-09 14:28 ` Krzysztof Kozlowski
2023-10-09 15:56 ` Hugues FRUCHET
2023-10-04 9:15 ` [PATCH 4/7] media: hantro: add support for STM32MP25 VENC Hugues Fruchet
2023-10-04 9:15 ` [PATCH 5/7] arm64: dts: st: add soc & rifsc structure to stm32mp255 Hugues Fruchet
2023-10-05 19:46 ` Krzysztof Kozlowski
2023-10-09 13:54 ` Hugues FRUCHET
2023-10-04 9:15 ` [PATCH 6/7] arm64: dts: st: add video decoder support " Hugues Fruchet
2023-10-04 9:15 ` [PATCH 7/7] arm64: dts: st: add video encoder " Hugues Fruchet
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=fa0e6187-ab7d-bc23-299c-a491c8ff1d8f@foss.st.com \
--to=hugues.fruchet@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrzej.p@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--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=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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).