From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zhentao Guo <zhentao.guo@amlogic.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH RFC v4 1/4] media: dt-bindings: Add Amlogic V4L2 video decoder
Date: Fri, 13 Feb 2026 09:16:58 +0100 [thread overview]
Message-ID: <2f68ee18-e9d9-4da6-900c-93a7663b3c9d@kernel.org> (raw)
In-Reply-To: <75e55ceb-e6dd-47b5-a829-66f6fbb3e13e@amlogic.com>
On 13/02/2026 09:02, Zhentao Guo wrote:
> Hi Krzysztof,
>
>
> 在 2026/2/13 15:35, Krzysztof Kozlowski 写道:
>> [ EXTERNAL EMAIL ]
>>
>> On 13/02/2026 06:12, Zhentao Guo via B4 Relay wrote:
>>> From: Zhentao Guo<zhentao.guo@amlogic.com>
>>>
>>> Describe the initial support for the V4L2 stateless video decoder
>>> driver used with the Amlogic S4 (S805X2) platform.
>>>
>>> Signed-off-by: Zhentao Guo<zhentao.guo@amlogic.com>
>>> ---
>>> .../bindings/media/amlogic,s4-vcodec-dec.yaml | 96 ++++++++++++++++++++++
>>> 1 file changed, 96 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/media/amlogic,s4-vcodec-dec.yaml b/Documentation/devicetree/bindings/media/amlogic,s4-vcodec-dec.yaml
>>> new file mode 100644
>>> index 000000000000..88780514d06c
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/media/amlogic,s4-vcodec-dec.yaml
>>> @@ -0,0 +1,96 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +# Copyright (C) 2025 Amlogic, Inc. All rights reserved
>>> +%YAML 1.2
>>> +---
>>> +$id:http://devicetree.org/schemas/media/amlogic,s4-vcodec-dec.yaml#
>>> +$schema:http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Amlogic Video Decode Accelerator
>>> +
>>> +maintainers:
>>> + - Zhentao Guo<zhentao.guo@amlogic.com>
>>> +
>>> +description:
>>> + The Video Decoder Accelerator present on Amlogic SOCs.
>>> + It supports stateless h264 decoding.
>>> +
>>> +properties:
>>> + compatible:
>>> + const: amlogic,s4-vcodec-dec
>> Why do you repeat "dec" twice? codec means decoder, so what is the last
>> "dec" about?
> In fact, codec means encoder+decoder, and dec is short for decoder.
Yes, that's what I meant, so why do you repeat decoder?
>>> +
>>> + reg:
>>> + maxItems: 2
>>> +
>>> + reg-names:
>>> + items:
>>> + - const: dos
>>> + - const: dmc
>>> +
>>> + interrupts:
>>> + maxItems: 3
>>> +
>>> + clocks:
>>> + maxItems: 3
>>> +
>>> + clock-names:
>>> + items:
>>> + - const: vdec
>>> + - const: clk_vdec_mux
>>> + - const: clk_hevcf_mux
>> Name them based on their role/name in this device. Why this device would
>> care that it receives a mux? Not a div? or not a gate?
> Ok, previously we overlooked this. We will improve it in the next version.
>>> +
>>> + power-domains:
>>> + maxItems: 2
>>> +
>>> + power-domain-names:
>>> + items:
>>> + - const: vdec
>>> + - const: hevc
>>> +
>>> + resets:
>>> + maxItems: 1
>>> +
>>> + amlogic,canvas:
>>> + description: should point to a canvas provider node
>> Why? What for?
>>
>> What is canvas provider?
>
> The canvas provider is: drivers/soc/amlogic/meson-canvas.c
What is this "canvas" device.
>
> In short, canvas is a hardware IP inside the Amlogic SoC. The decoder IP
> needs to access DDR through canvas IP, so we need to reference the
Why decoder cannot access DDR directly?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-13 8:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 5:12 [PATCH RFC v4 0/4] Add Amlogic stateless H.264 video decoder for S4 Zhentao Guo via B4 Relay
2026-02-13 5:12 ` [PATCH RFC v4 1/4] media: dt-bindings: Add Amlogic V4L2 video decoder Zhentao Guo via B4 Relay
2026-02-13 7:35 ` Krzysztof Kozlowski
2026-02-13 8:04 ` Zhentao Guo
2026-02-13 8:17 ` Krzysztof Kozlowski
[not found] ` <75e55ceb-e6dd-47b5-a829-66f6fbb3e13e@amlogic.com>
2026-02-13 8:16 ` Krzysztof Kozlowski [this message]
2026-02-13 8:31 ` Zhentao Guo
2026-02-13 8:55 ` Krzysztof Kozlowski
2026-02-13 9:14 ` Zhentao Guo
2026-02-13 11:14 ` Piotr Oniszczuk
2026-02-13 11:30 ` Krzysztof Kozlowski
2026-03-05 11:01 ` Zhentao Guo
2026-03-05 11:08 ` Krzysztof Kozlowski
2026-03-05 11:35 ` Neil Armstrong
2026-03-05 11:53 ` Krzysztof Kozlowski
2026-03-05 15:57 ` Neil Armstrong
2026-02-13 5:12 ` [PATCH RFC v4 2/4] decoder: Add V4L2 stateless H.264 decoder driver Zhentao Guo via B4 Relay
2026-02-13 5:12 ` [PATCH RFC v4 3/4] arm64: dts: amlogic: Add video decoder driver support for S4 SOCs Zhentao Guo via B4 Relay
2026-02-13 5:12 ` [PATCH RFC v4 4/4] arm64: defconfig: Enable VDEC driver for Amlogic SoCs Zhentao Guo via B4 Relay
2026-02-13 7:33 ` Krzysztof Kozlowski
2026-02-13 8:06 ` Zhentao Guo
2026-02-13 8:18 ` Krzysztof Kozlowski
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=2f68ee18-e9d9-4da6-900c-93a7663b3c9d@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=zhentao.guo@amlogic.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