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 1/3] dt-bindings: vdec: Add binding document of Amlogic decoder accelerator
Date: Tue, 28 Oct 2025 12:33:19 +0100 [thread overview]
Message-ID: <606da3b1-f042-4cc1-89d0-4feb257f032f@kernel.org> (raw)
In-Reply-To: <40830266-692a-4731-8957-4462d4993746@amlogic.com>
On 28/10/2025 12:14, Zhentao Guo wrote:
>>> +properties:
>>> + compatible:
>>> + const: amlogic,s4-vcodec-dec
>>> +
>>> + reg:
>>> + maxItems: 2
>>> +
>>> + reg-names:
>>> + items:
>>> + - const: dosbus
>>> + - const: dmcbus
>> Is "bus" really name of this in datasheet?
> No, it is not from the datasheet, in fact it was inherited from the
> older SOCs. Do you have any suggestions about this?
dos, dmc
>>> +
>>> + interrupts:
>>> + maxItems: 3
>>> +
>>> + interrupt-names:
>>> + items:
>>> + - const: mailbox_0
>>> + - const: mailbox_1
>>> + - const: mailbox_2
>> Useless names, so just drop interrupt-names property.
> Yes, we don't need the interrupt names. I'll drop them.
>>
>>> +
>>> + clocks:
>>> + maxItems: 3
>>> +
>>> + clock-names:
>>> + items:
>>> + - const: vdec
>>> + - const: clk_vdec_mux
>>> + - const: clk_hevcf_mux
>>> +
>>> + power-domains:
>>> + maxItems: 2
>>> +
>>> + power-domain-names:
>>> + items:
>>> + - const: pwrc-vdec
>> Drop pwrc
>>
>>> + - const: pwrc-hevc
>> Drop pwrc
> Ok, I'll drop the two pwrc(s) above.
>>
>> Missing iommus. I really doubt hardware works without IOMMU.
>
> IOMMU is not supported by Amlogic SOCs, the decoder hardware needs to
> use contiguous memory.
I assume you speak about hardware, not drivers, so it is fine.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-28 11:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 5:42 [PATCH 0/3] Add Amlogic stateless H.264 video decoder for S4 Zhentao Guo via B4 Relay
2025-10-27 5:42 ` [PATCH 1/3] dt-bindings: vdec: Add binding document of Amlogic decoder accelerator Zhentao Guo via B4 Relay
2025-10-27 13:05 ` Krzysztof Kozlowski
2025-10-28 11:14 ` Zhentao Guo
2025-10-28 11:33 ` Krzysztof Kozlowski [this message]
2025-10-28 12:23 ` Zhentao Guo
2025-10-27 5:42 ` [PATCH 2/3] dts: decoder: Support V4L2 stateless decoder dt node for S4 Zhentao Guo via B4 Relay
2025-10-27 13:06 ` Krzysztof Kozlowski
2025-10-28 11:18 ` Zhentao Guo
2025-10-27 5:42 ` [PATCH 3/3] decoder: Add V4L2 stateless H.264 decoder driver Zhentao Guo via B4 Relay
2025-10-27 13:10 ` Krzysztof Kozlowski
2025-10-28 11:22 ` Zhentao Guo
2025-10-28 11:01 ` Neil Armstrong
2025-10-28 12:16 ` Zhentao Guo
2025-11-08 22:53 ` Martin Blumenstingl
2025-11-10 4:05 ` Zhentao Guo
2025-10-27 12:57 ` [PATCH 0/3] Add Amlogic stateless H.264 video decoder for S4 Christian Hewitt
2025-10-28 11:08 ` Zhentao Guo
2025-10-30 10:50 ` Ferass El Hafidi
2025-10-31 2:32 ` Zhentao Guo
2025-10-28 10:50 ` Neil Armstrong
2025-10-28 11:47 ` Zhentao Guo
2025-11-04 7:28 ` Christian Hewitt
2025-11-04 16:13 ` Nicolas Dufresne
2025-11-05 9:26 ` Zhentao Guo
2025-11-05 13:51 ` Nicolas Dufresne
2025-11-06 2:44 ` Zhentao Guo
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=606da3b1-f042-4cc1-89d0-4feb257f032f@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;
as well as URLs for NNTP newsgroup(s).