From: Michael Riesch <michael.riesch@collabora.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Frank Li <Frank.li@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Kever Yang <kever.yang@rock-chips.com>,
Collabora Kernel Team <kernel@collabora.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: defconfig: enable designware mipi csi-2 receiver
Date: Mon, 9 Mar 2026 10:02:35 +0100 [thread overview]
Message-ID: <d670a203-6fc1-4fbc-a7b2-c2366745d794@collabora.com> (raw)
In-Reply-To: <20260307-majestic-otter-of-contentment-eeba71@quoll>
Hi Krzysztof,
On 3/7/26 16:34, Krzysztof Kozlowski wrote:
> On Fri, Mar 06, 2026 at 03:09:51PM +0100, Michael Riesch wrote:
>> The Synopsys DesignWare MIPI CSI-2 Receiver is integrated into
>> recent Rockchip SoCs, such as the RK3568 and the RK3588.
>
> ... and used on boards foo bar.
foo bar = pretty much any recent board with a Rockchip SoC on it...
(plus NXP users, as there is a series by Frank in the works)
>
> (becuse we take defconfig for boards, not for SoCs - if there is no
> single board using it, then it should not be enabled because it means
> you do it for downstream which simply does not exist for us).
... but there is not yet a mainline example. Next item on my TODO list
is to send out basic RK3588 VICAP support including the device tree bits
for the Radxa ROCK 5B+ plus camera modules. Should I include the patch
in that series? Or wait until that series has been accepted? Or will you
just take my word for it that there will be plenty of boards using that
receiver in near future?
Best regards,
Michael
next prev parent reply other threads:[~2026-03-09 9:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 14:09 [PATCH 0/4] media: synopsys: csi2rx: add support for rk3588 variant Michael Riesch via B4 Relay
2026-03-06 14:09 ` [PATCH 1/4] media: dt-bindings: rockchip,rk3568-mipi-csi2: add rk3588 compatible Michael Riesch via B4 Relay
2026-03-07 15:33 ` Krzysztof Kozlowski
2026-03-09 8:50 ` Michael Riesch
2026-03-09 9:11 ` Krzysztof Kozlowski
2026-03-09 15:44 ` Frank Li
2026-03-06 14:09 ` [PATCH 2/4] media: synopsys: csi2rx: add support for rk3588 variant Michael Riesch via B4 Relay
2026-03-07 15:35 ` Krzysztof Kozlowski
2026-03-06 14:09 ` [PATCH 3/4] arm64: dts: rockchip: add mipi csi-2 receiver nodes to rk3588 Michael Riesch via B4 Relay
2026-03-06 14:09 ` [PATCH 4/4] arm64: defconfig: enable designware mipi csi-2 receiver Michael Riesch via B4 Relay
2026-03-07 15:34 ` Krzysztof Kozlowski
2026-03-09 9:02 ` Michael Riesch [this message]
2026-03-09 9:11 ` 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=d670a203-6fc1-4fbc-a7b2-c2366745d794@collabora.com \
--to=michael.riesch@collabora.com \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--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=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®