From: Michael Riesch <michael.riesch@wolfvision.net>
To: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
Peter Geis <pgwipeout@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
Liang Chen <cl@rock-chips.com>
Subject: Re: [PATCH 0/3] Add support for the RK356x variant of the Inno CSI DPHY
Date: Mon, 22 Aug 2022 09:27:52 +0200 [thread overview]
Message-ID: <ef5e2424-a5c3-4032-71ec-9884d38ec190@wolfvision.net> (raw)
In-Reply-To: <20220720091527.1270365-1-michael.riesch@wolfvision.net>
On 7/20/22 11:15, Michael Riesch wrote:
> Hi all,
>
> This series adds support for the variant of the Innosilicon MIPI CSI DPHY that
> can be found in Rockchip RK356x SoCs.
>
> Please note that only the basic operating mode is supported, in which all four
> CSI lanes are controlled by the Rockchip ISP. Split lane operation (e.g., two
> lanes to ISP and two lanes to VICAP) is not supported.
>
> This has been tested on a Radxa ROCK3 Model A board together with an IMX219
> camera sensor and a patched version of the rkisp1 driver (with support for the
> RK356x variant V2.1 added in a very crude way).
>
> Looking forward to your comments!
>
> Best regards,
> Michael
>
> Michael Riesch (3):
> dt-bindings: phy: add compatible for rk356x to rockchip-inno-csi-dphy
> phy: rockchip: add support for the rk356x variant to
> rockchip-inno-csidphy
> arm64: dts: rockchip: add csi dphy node to rk356x
>
> .../bindings/phy/rockchip-inno-csi-dphy.yaml | 1 +
> arch/arm64/boot/dts/rockchip/rk356x.dtsi | 12 ++++++++++
> .../phy/rockchip/phy-rockchip-inno-csidphy.c | 24 +++++++++++++++++++
> 3 files changed, 37 insertions(+)
>
Gentle ping on this one. I am aware of course that it is still vacation
season and the merge window was there as well, but it would be nice to
have some feedback.
Thanks and best regards,
Michael
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-08-22 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 9:15 [PATCH 0/3] Add support for the RK356x variant of the Inno CSI DPHY Michael Riesch
2022-07-20 9:15 ` [PATCH 1/3] dt-bindings: phy: add compatible for rk356x to rockchip-inno-csi-dphy Michael Riesch
2022-07-25 22:22 ` Rob Herring
2022-08-23 11:50 ` Heiko Stübner
2022-07-20 9:15 ` [PATCH 2/3] phy: rockchip: add support for the rk356x variant to rockchip-inno-csidphy Michael Riesch
2022-08-23 11:51 ` Heiko Stübner
2022-07-20 9:15 ` [PATCH 3/3] arm64: dts: rockchip: add csi dphy node to rk356x Michael Riesch
2022-07-21 9:38 ` [PATCH 0/3] Add support for the RK356x variant of the Inno CSI DPHY Michael Riesch
2022-08-22 7:27 ` Michael Riesch [this message]
2022-09-02 17:31 ` Vinod Koul
2022-09-04 17:22 ` (subset) " Heiko Stuebner
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=ef5e2424-a5c3-4032-71ec-9884d38ec190@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=frattaroli.nicolas@gmail.com \
--cc=heiko@sntech.de \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=vkoul@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