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 4/4] arm64: defconfig: enable Rockchip NPU support
Date: Fri, 7 Aug 2026 07:58:51 +0200 [thread overview]
Message-ID: <c28f33bc-bab4-4d64-9e53-007bceb4d321@kernel.org> (raw)
In-Reply-To: <20260806-rockchip-defconfig-additions-v1-4-6b1d8baa0bf5@collabora.com>
On 06/08/2026 19:24, Sebastian Reichel wrote:
> Enable support for the Rockchip NPU, which can be used with upstream
> mesa on many RK3588 boards, such as the Radxa Rock 5 family or the
> Orange Pis.
>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
This should be squashed with the previous ones. Do not enable item by
item. All your three last patches do the same logical thing: enable
multimedia drivers for Radxa Rock 5 (+ others).
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-07 5:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 17:24 [PATCH 0/4] arm64: defconfig: Rockchip RK3588 defconfig additions Sebastian Reichel
2026-08-06 17:24 ` [PATCH 1/4] arm64: defconfig: enable Rockchip VDEC Sebastian Reichel
2026-08-06 17:24 ` [PATCH 2/4] arm64: defconfig: enable Verisilicon IOMMU for Rockchip RK3588 Sebastian Reichel
2026-08-06 17:24 ` [PATCH 3/4] arm64: defconfig: enable Rock 5B camera support Sebastian Reichel
2026-08-06 17:24 ` [PATCH 4/4] arm64: defconfig: enable Rockchip NPU support Sebastian Reichel
2026-08-07 5:58 ` Krzysztof Kozlowski [this message]
2026-08-07 16:18 ` Sebastian Reichel
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=c28f33bc-bab4-4d64-9e53-007bceb4d321@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