From: Heiko Stuebner <heiko@sntech.de>
To: vkoul@kernel.org, kishon@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
quentin.schulz@cherry.de, sebastian.reichel@collabora.com,
heiko@sntech.de, 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,
dse@thaumatec.com
Subject: [PATCH v4 0/2] MIPI DSI phy for rk3588
Date: Tue, 26 Nov 2024 14:17:33 +0100 [thread overview]
Message-ID: <20241126131736.465111-1-heiko@sntech.de> (raw)
This adds the phy driver need for DSI output on rk3588.
The phy itself is used for both DSI output and CSI input, though the
CSI part for the whole chain needs a lot more work, so is left out for
now and only the DSI part implemented.
This allows the rk3588 with its current VOP support to drive a DSI display
using the DSI2 controller driver I'll submit in a next step.
Only generic phy interfaces are used, so the DSI part is pretty straight
forward.
changes in v4:
- moved to #phy-cells = 1 as suggested by Sebastian, with the argument
denoting the requested phy-type (C-PHY, D-PHY). This works similarly
how the Mediatek C/D-PHY already implements this, see mails around:
https://lore.kernel.org/all/20230608200552.GA3303349-robh@kernel.org/
- dropped Krzysztof's review tag from the binding because of this
- dropped custom UPDATE macro and use FIELD_PREP instead
- build a FIELD_PREP_HIWORD macro for the GRF settings
- add received Tested-by tags
changes in v3:
- add Krzysztof review tag to the binding
- address Sebastian's review comments
- better error handling
- dropping empty function
- headers
- not using of_match_ptr - this should also make the
test-robot happier
changes in v2:
- fix error in dt-binding example
- drop unused frequency table
- pull in some more recent improvements from the vendor-kernel
which includes a lot less magic values
- already include the support for rk3576
- use dev_err_probe
Heiko Stuebner (2):
dt-bindings: phy: Add Rockchip MIPI C-/D-PHY schema
phy: rockchip: Add Samsung MIPI D-/C-PHY driver
.../phy/rockchip,rk3588-mipi-dcphy.yaml | 87 +
drivers/phy/rockchip/Kconfig | 12 +
drivers/phy/rockchip/Makefile | 1 +
.../phy/rockchip/phy-rockchip-samsung-dcphy.c | 1602 +++++++++++++++++
4 files changed, 1702 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
create mode 100644 drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c
--
2.45.2
next reply other threads:[~2024-11-26 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 13:17 Heiko Stuebner [this message]
2024-11-26 13:17 ` [PATCH v4 1/2] dt-bindings: phy: Add Rockchip MIPI C-/D-PHY schema Heiko Stuebner
2024-11-26 16:02 ` Sebastian Reichel
2024-11-26 17:44 ` Conor Dooley
2024-11-26 18:38 ` Heiko Stübner
2024-11-27 16:23 ` Conor Dooley
2024-11-26 13:17 ` [PATCH v4 2/2] phy: rockchip: Add Samsung MIPI D-/C-PHY driver Heiko Stuebner
2024-11-26 16:11 ` Sebastian Reichel
2024-11-28 9:13 ` kernel test robot
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=20241126131736.465111-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dse@thaumatec.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.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=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--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;
as well as URLs for NNTP newsgroup(s).