public inbox for linux-amlogic@lists.infradead.org
 help / color / mirror / Atom feed
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: Thu, 5 Mar 2026 12:08:43 +0100	[thread overview]
Message-ID: <69900d76-3820-467a-9fbc-13f79189df2f@kernel.org> (raw)
In-Reply-To: <26d0f52e-3681-46ce-b0dc-0cb020e8d9a1@amlogic.com>

On 05/03/2026 12:01, Zhentao Guo wrote:
> 
>       2. Why canvas is needed?
> 
>  1. Since the ARM IOMMU HW is not integrated into the Amlogic SOCs,we
>     need canvas to prevent the DDR memory used by the decoder from being
>     rewrote by other hardware. Canvas provides the decoder with a
>     configurable DDR memory range, as well as hardware-based detection
>     and blocking for out-of-bounds access.
>   2. From the diagram above, we can see a lite CPU called AMRISC. AMRISC
>     is the controller of the decoder HW and the decoder driver needs to
>     access the decoder hardware through AMRISC. However, AMRISC is a
>     16-bit CPU and cannot directly handle 32-bit or 64-bit physical
>     addresses. Therefore, canvas is required to convert the addresses
>     into index to facilitate processing by the AMRISC core.

This suggests "Canvas" is IOMMU, thus use proper IOMMU abstractions and
you cannot have own phandle for it.

Best regards,
Krzysztof

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2026-03-05 11:08 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
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 [this message]
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=69900d76-3820-467a-9fbc-13f79189df2f@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