From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>,
Heiko Stuebner <heiko@sntech.de>
Cc: Detlev Casanova <detlev.casanova@collabora.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Michael Riesch <michael.riesch@collabora.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v3] arm64: defconfig: enable Rockchip Multimedia drivers
Date: Mon, 10 Aug 2026 12:49:14 +0200 [thread overview]
Message-ID: <0a29b9ea-130d-4e53-8d52-584c903516e4@kernel.org> (raw)
In-Reply-To: <20260808-rockchip-defconfig-additions-v3-1-0ed67877e94d@collabora.com>
On 08/08/2026 02:42, Sebastian Reichel wrote:
> Enable multimedia related drivers used by the Radxa ROCK 5B (used as an
> example, the config options are relevant for most Rockchip RK3588 and
> RK3576 boards), so that all hardware is supported by the default config.
>
> * Synopsys MIPI CSI2RX - RK3588 CSI2 Controller
> * RKVDEC - RK3588/RK3576 video decoder for H.264 and H.265
> * Sony IMX415 - Sensor used by the Radxa Cam 4K module
> * Rocket - RK3588 NPU driver
> * Verisilicon IOMMU - IOMMU used by RK3588 AV1 video decoder
> * Innosilicon CSI D-PHY - RK3588 CSI PHY (one of them)
>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
prev parent reply other threads:[~2026-08-10 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 0:42 [PATCH v3] arm64: defconfig: enable Rockchip Multimedia drivers Sebastian Reichel
2026-08-08 8:44 ` Michael Riesch
2026-08-08 14:06 ` Heiko Stübner
2026-08-08 20:08 ` Sebastian Reichel
2026-08-10 5:47 ` Krzysztof Kozlowski
2026-08-10 10:49 ` Krzysztof Kozlowski [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=0a29b9ea-130d-4e53-8d52-584c903516e4@kernel.org \
--to=krzk@kernel.org \
--cc=benjamin.gaignard@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@collabora.com \
--cc=sebastian.reichel@collabora.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