From: Arun Iyengar <aiyengar1990@gmail.com>
To: Lukas Splavec <lukas.splavec@puresig.cz>
Cc: detlev.casanova@collabora.com, ezequiel@vanguardiasur.com.ar,
mchehab@kernel.org, heiko@sntech.de, linux-media@vger.kernel.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: rkvdec: Use dma_map_resource() to map RCB SRAM buffers
Date: Sun, 15 Nov 2026 08:01:39 -0000 [thread overview]
Message-ID: <179472969996.3843098.1159119154248532841@gmail.com> (raw)
In-Reply-To: <20261114094916.28744-1-lukas.splavec@puresig.cz>
Tested on an Orange Pi 5 (RK3588S), rkvdec from media next with this
patch, KASAN and lockdep on: all RCBs in SRAM now use IOVAs, no IOMMU
fault or splat, fluster HEVC and H.264 results unchanged.
Tested-by: Arun Iyengar <aiyengar1990@gmail.com>
prev parent reply other threads:[~2026-11-15 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 9:49 [PATCH] media: rkvdec: Use dma_map_resource() to map RCB SRAM buffers Lukas Splavec
2026-11-15 8:01 ` Arun Iyengar [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=179472969996.3843098.1159119154248532841@gmail.com \
--to=aiyengar1990@gmail.com \
--cc=detlev.casanova@collabora.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--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=lukas.splavec@puresig.cz \
--cc=mchehab@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