From: "Heiko Stübner" <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,
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: Re: [PATCH v6 0/2] MIPI DSI phy for rk3588
Date: Thu, 13 Feb 2025 22:09:03 +0100 [thread overview]
Message-ID: <6831884.31tnzDBltd@diego> (raw)
In-Reply-To: <20250213210554.1645755-1-heiko@sntech.de>
Am Donnerstag, 13. Februar 2025, 22:05:46 MEZ schrieb Heiko Stuebner:
> 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 v6:
> - rebase onto 6.14-rc1
> - add Krzysztof binding review
> - v5 was sent at the beginning of december '24, so probably has been lost
>
> changes in v5:
> - add bitfield.h for the FIELD_PROP definition
> (reported by kernel-test-robot)
> - add Sebastian's Reviewed-by
> - add Conor's Ack to the dt-binding
>
> 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 | 1604 +++++++++++++++++
> 4 files changed, 1704 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
> create mode 100644 drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c
Forgot to transplant from the v5 cover-letter - the series got a
Tested-by: Quentin Schulz <quentin.schulz@cherry.de>
on RK3588 Tiger with Haikou Video Demo in [0]
[0] https://lore.kernel.org/r/63cda072-3671-42c9-9650-7a3ece39dec6@cherry.de
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <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,
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: Re: [PATCH v6 0/2] MIPI DSI phy for rk3588
Date: Thu, 13 Feb 2025 22:09:03 +0100 [thread overview]
Message-ID: <6831884.31tnzDBltd@diego> (raw)
In-Reply-To: <20250213210554.1645755-1-heiko@sntech.de>
Am Donnerstag, 13. Februar 2025, 22:05:46 MEZ schrieb Heiko Stuebner:
> 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 v6:
> - rebase onto 6.14-rc1
> - add Krzysztof binding review
> - v5 was sent at the beginning of december '24, so probably has been lost
>
> changes in v5:
> - add bitfield.h for the FIELD_PROP definition
> (reported by kernel-test-robot)
> - add Sebastian's Reviewed-by
> - add Conor's Ack to the dt-binding
>
> 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 | 1604 +++++++++++++++++
> 4 files changed, 1704 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
> create mode 100644 drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c
Forgot to transplant from the v5 cover-letter - the series got a
Tested-by: Quentin Schulz <quentin.schulz@cherry.de>
on RK3588 Tiger with Haikou Video Demo in [0]
[0] https://lore.kernel.org/r/63cda072-3671-42c9-9650-7a3ece39dec6@cherry.de
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <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,
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: Re: [PATCH v6 0/2] MIPI DSI phy for rk3588
Date: Thu, 13 Feb 2025 22:09:03 +0100 [thread overview]
Message-ID: <6831884.31tnzDBltd@diego> (raw)
In-Reply-To: <20250213210554.1645755-1-heiko@sntech.de>
Am Donnerstag, 13. Februar 2025, 22:05:46 MEZ schrieb Heiko Stuebner:
> 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 v6:
> - rebase onto 6.14-rc1
> - add Krzysztof binding review
> - v5 was sent at the beginning of december '24, so probably has been lost
>
> changes in v5:
> - add bitfield.h for the FIELD_PROP definition
> (reported by kernel-test-robot)
> - add Sebastian's Reviewed-by
> - add Conor's Ack to the dt-binding
>
> 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 | 1604 +++++++++++++++++
> 4 files changed, 1704 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
> create mode 100644 drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c
Forgot to transplant from the v5 cover-letter - the series got a
Tested-by: Quentin Schulz <quentin.schulz@cherry.de>
on RK3588 Tiger with Haikou Video Demo in [0]
[0] https://lore.kernel.org/r/63cda072-3671-42c9-9650-7a3ece39dec6@cherry.de
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-02-13 21:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 21:05 [PATCH v6 0/2] MIPI DSI phy for rk3588 Heiko Stuebner
2025-02-13 21:05 ` Heiko Stuebner
2025-02-13 21:05 ` Heiko Stuebner
2025-02-13 21:05 ` [PATCH v6 1/2] dt-bindings: phy: Add Rockchip MIPI C-/D-PHY schema Heiko Stuebner
2025-02-13 21:05 ` Heiko Stuebner
2025-02-13 21:05 ` Heiko Stuebner
2025-02-13 21:05 ` [PATCH v6 2/2] phy: rockchip: Add Samsung MIPI D-/C-PHY driver Heiko Stuebner
2025-02-13 21:05 ` Heiko Stuebner
2025-02-13 21:05 ` Heiko Stuebner
2025-02-14 12:13 ` Vinod Koul
2025-02-14 12:13 ` Vinod Koul
2025-02-14 12:13 ` Vinod Koul
2025-02-19 22:51 ` Heiko Stübner
2025-02-19 22:51 ` Heiko Stübner
2025-02-19 22:51 ` Heiko Stübner
2025-03-12 15:51 ` Vinod Koul
2025-03-12 15:51 ` Vinod Koul
2025-03-12 15:51 ` Vinod Koul
2025-02-13 21:09 ` Heiko Stübner [this message]
2025-02-13 21:09 ` [PATCH v6 0/2] MIPI DSI phy for rk3588 Heiko Stübner
2025-02-13 21:09 ` Heiko Stübner
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=6831884.31tnzDBltd@diego \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.