From: Heiko Stuebner <heiko@sntech.de>
To: dri-devel@lists.freedesktop.org
Cc: devicetree@vger.kernel.org, dafna.hirschfeld@collabora.com,
cmuellner@linux.com, hjc@rock-chips.com,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
helen.koike@collabora.com, robh+dt@kernel.org,
sebastian.fricke@posteo.net, ezequiel@collabora.com,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: [PATCH 0/6] Support second Image Signal Processor on rk3399
Date: Tue, 2 Feb 2021 15:56:26 +0100 [thread overview]
Message-ID: <20210202145632.1263136-1-heiko@sntech.de> (raw)
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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2021-02-02 14:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 14:56 Heiko Stuebner [this message]
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 ` [PATCH 0/6] Support second Image Signal Processor " Sebastian Fricke
2021-02-03 19:54 ` 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=20210202145632.1263136-1-heiko@sntech.de \
--to=heiko@sntech.de \
--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=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 \
--cc=sebastian.fricke@posteo.net \
/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).