From: Sebastian Fricke <sebastian.fricke@posteo.net>
To: Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, dafna.hirschfeld@collabora.com,
cmuellner@linux.com, hjc@rock-chips.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, helen.koike@collabora.com,
robh+dt@kernel.org, ezequiel@collabora.com,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH 0/6] Support second Image Signal Processor on rk3399
Date: Wed, 3 Feb 2021 19:14:22 +0100 [thread overview]
Message-ID: <20210203181422.txbd6kvujlmz4nju@basti-TUXEDO-Book-XA1510> (raw)
In-Reply-To: <20210202145632.1263136-1-heiko@sntech.de>
Hey Heiko,
I have tested your patch set on my nanoPC-T4, here is a complete log
with:
- relevant kernel log entries
- system information
- media ctl output
- sysfs entry information
https://paste.debian.net/1183874/
Additionally, to your patchset I have applied the following patches:
https://github.com/initBasti/Linux_kernel_media_tree_fork/commits/dual_cam_setup
And just to not cause confusion the `media_dev` entries come from this
unmerged series:
https://patchwork.kernel.org/project/linux-media/list/?series=426269
I have actually been able to stream with both of my cameras at the same
time using the libcamera cam command.
I would like to thank you a lot for making this possible.
If you like to you can add:
Tested-by: Sebastian Fricke <sebastian.fricke@posteo.net>
On 02.02.2021 15:56, Heiko Stuebner wrote:
>The rk3399 has two ISPs and right now only the first one is usable.
>The second ISP is connected to the TXRX dphy on the soc.
>
>The phy of ISP1 is only accessible through the DSI controller's
>io-memory, so this series adds support for simply using the dsi
>controller is a phy if needed.
>
>That solution is needed at least on rk3399 and rk3288 but no-one
>has looked at camera support on rk3288 at all, so right now
>only implement the rk3399 specifics.
>
>
>Heiko Stuebner (6):
> drm/rockchip: dsi: add own additional pclk handling
> dt-bindings: display: rockchip-dsi: add optional #phy-cells property
> drm/rockchip: dsi: add ability to work as a phy instead of full dsi
> arm64: dts: rockchip: add #phy-cells to mipi-dsi1
> arm64: dts: rockchip: add cif clk-control pinctrl for rk3399
> arm64: dts: rockchip: add isp1 node on rk3399
>
> .../display/rockchip/dw_mipi_dsi_rockchip.txt | 1 +
> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 39 ++
> drivers/gpu/drm/rockchip/Kconfig | 2 +
> .../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 342 ++++++++++++++++++
> 4 files changed, 384 insertions(+)
>
>--
>2.29.2
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2021-02-03 18:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 14:56 [PATCH 0/6] Support second Image Signal Processor on rk3399 Heiko Stuebner
2021-02-02 14:56 ` [PATCH 1/6] drm/rockchip: dsi: add own additional pclk handling Heiko Stuebner
2021-02-02 14:56 ` [PATCH 2/6] dt-bindings: display: rockchip-dsi: add optional #phy-cells property Heiko Stuebner
2021-02-09 21:03 ` Rob Herring
2021-02-02 14:56 ` [PATCH 3/6] drm/rockchip: dsi: add ability to work as a phy instead of full dsi Heiko Stuebner
2021-02-02 14:56 ` [PATCH 4/6] arm64: dts: rockchip: add #phy-cells to mipi-dsi1 Heiko Stuebner
2021-02-02 14:56 ` [PATCH 5/6] arm64: dts: rockchip: add cif clk-control pinctrl for rk3399 Heiko Stuebner
2021-02-02 14:56 ` [PATCH 6/6] arm64: dts: rockchip: add isp1 node on rk3399 Heiko Stuebner
2021-02-03 18:14 ` Sebastian Fricke [this message]
2021-02-03 19:54 ` [PATCH 0/6] Support second Image Signal Processor " Heiko Stübner
2021-02-05 6:43 ` Sebastian Fricke
2021-02-05 8:15 ` Heiko Stübner
2021-02-05 14:55 ` Heiko Stübner
2021-02-10 11:15 ` Heiko Stübner
2021-02-11 5:25 ` Sebastian Fricke
2021-02-11 14:42 ` Heiko Stübner
2021-02-13 11:19 ` Sebastian Fricke
2021-02-13 22:33 ` 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=20210203181422.txbd6kvujlmz4nju@basti-TUXEDO-Book-XA1510 \
--to=sebastian.fricke@posteo.net \
--cc=cmuellner@linux.com \
--cc=dafna.hirschfeld@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@collabora.com \
--cc=heiko@sntech.de \
--cc=helen.koike@collabora.com \
--cc=hjc@rock-chips.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=robh+dt@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;
as well as URLs for NNTP newsgroup(s).