From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>
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 07:47:52 +0200 [thread overview]
Message-ID: <63bbce33-9427-4585-a1bb-dc4af05e981f@kernel.org> (raw)
In-Reply-To: <5738059.NG923GbCHz@diego>
On 08/08/2026 16:06, Heiko Stübner wrote:
> Am Samstag, 8. August 2026, 02:42:26 Mitteleuropäische Sommerzeit schrieb Sebastian Reichel:
>> 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>
>
> I'm not sure what the actual rule for defconfig changes is.
>
> In some past thread I remember (hopefully correctly) Krzysztof saying
> that the arm64 defconfig is not supposed to be a distro-config, so
> enabling each and every driver was not the goal.
>
> On the other hand, he did not repeat that in his reply to your v1 ;-) .
>
> We're at -rc7 tomorrow, so it'd be 7.4 material anyway, so enough time
> to get "complaints" I guess ;-) .
I believe defconfig is still mostly for us and the patch fits this
purpose - you need these to fully use mentioned upstream hardware.
I learnt that few distros (I think Fedora) use defconfig directly
instead of customizing it like Ubuntu does, so anyway maybe we should
enable everything for given hardware.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-08-10 5:48 UTC|newest]
Thread overview: 5+ 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 [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=63bbce33-9427-4585-a1bb-dc4af05e981f@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