From: Alex Bee <knaerzche@gmail.com>
To: "Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, Alex Bee <knaerzche@gmail.com>
Subject: [PATCH 0/7] Add DSI support for RK3128
Date: Mon, 6 May 2024 21:43:35 +0200 [thread overview]
Message-ID: <20240506194343.282119-1-knaerzche@gmail.com> (raw)
This series aims to add support for the DesignWare MIPI DSI controller and
the Innoslicon DPHY found in RK3128 SoCs. The code additions are rather
tiny: It only need some code in the Rockchip dw-mipi-dsi glue layer for
this SoC and some changes in the clock driver. Support for the DPHY has
already been added when the driver was initially submitted. I tested it
with a 800x1280 DSI panel where all 4 lanes that are supported are used.
Alex Bee (7):
dt-bindings: display: rockchip,dw-mipi-dsi: Document RK3128 DSI
dt-bindings: clock: rk3128: Add PCLK_MIPIPHY
clk: rockchip: rk3128: Export PCLK_MIPIPHY
clk: rockchip: rk3128: Add hclk_vio_h2p to critical clocks
drm/rockchip: dsi: Add support for RK3128
ARM: dts: rockchip: Add DPHY for RK3128
ARM: dts: rockchip: Add DSI for RK3128
.../rockchip/rockchip,dw-mipi-dsi.yaml | 2 +
arch/arm/boot/dts/rockchip/rk3128.dtsi | 49 +++++++++++++++++++
drivers/clk/rockchip/clk-rk3128.c | 3 +-
.../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 20 ++++++++
include/dt-bindings/clock/rk3128-cru.h | 1 +
5 files changed, 74 insertions(+), 1 deletion(-)
--
2.43.2
next reply other threads:[~2024-05-06 19:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 19:43 Alex Bee [this message]
2024-05-06 19:43 ` [PATCH 1/7] dt-bindings: display: rockchip, dw-mipi-dsi: Document RK3128 DSI Alex Bee
2024-05-07 16:52 ` Conor Dooley
2024-05-06 19:43 ` [PATCH 2/7] dt-bindings: clock: rk3128: Add PCLK_MIPIPHY Alex Bee
2024-05-07 16:51 ` Conor Dooley
2024-05-06 19:43 ` [PATCH 3/7] clk: rockchip: rk3128: Export PCLK_MIPIPHY Alex Bee
2024-05-06 19:43 ` [PATCH 4/7] clk: rockchip: rk3128: Add hclk_vio_h2p to critical clocks Alex Bee
2024-05-06 19:43 ` [PATCH 5/7] drm/rockchip: dsi: Add support for RK3128 Alex Bee
2024-05-06 19:43 ` [PATCH 6/7] ARM: dts: rockchip: Add DPHY " Alex Bee
2024-05-06 19:43 ` [PATCH 7/7] ARM: dts: rockchip: Add DSI " Alex Bee
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=20240506194343.282119-1-knaerzche@gmail.com \
--to=knaerzche@gmail.com \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=tzimmermann@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).