From: Vinod Koul <vkoul@kernel.org>
To: Michael Riesch <michael.riesch@collabora.com>
Cc: jason98166@gmail.com, Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Guochun Huang <hero.huang@rock-chips.com>,
Philipp Zabel <p.zabel@pengutronix.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
Subject: Re: [PATCH v2 1/4] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys
Date: Thu, 6 Aug 2026 21:26:53 +0530 [thread overview]
Message-ID: <anSuxfeitSqmSHNr@vaman> (raw)
In-Reply-To: <82da3622-9c3a-454c-87bc-fb4ec7adb68d@collabora.com>
On 03-08-26, 13:17, Michael Riesch wrote:
> > + Two cells select the PHY type and the direction, so that the
> > + transmitter (DSI) and the receiver (CSI) can be described as
> > + independent consumers of the same PHY:
> > + - <PHY_TYPE_DPHY RK_DCPHY_DIR_TX>
> > + - <PHY_TYPE_DPHY RK_DCPHY_DIR_RX>
>
> How is that Rockchip specific? As you state above this is either MIPI
> CSI or MIPI DSI, two perfectly standard protocols.
>
> @all Would it be reasonable to introduce PHY_TYPE_CSI and PHY_TYPE_DSI?
I think yes...
--
~Vinod
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Michael Riesch <michael.riesch@collabora.com>
Cc: jason98166@gmail.com, Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Guochun Huang <hero.huang@rock-chips.com>,
Philipp Zabel <p.zabel@pengutronix.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
Subject: Re: [PATCH v2 1/4] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys
Date: Thu, 6 Aug 2026 21:26:53 +0530 [thread overview]
Message-ID: <anSuxfeitSqmSHNr@vaman> (raw)
In-Reply-To: <82da3622-9c3a-454c-87bc-fb4ec7adb68d@collabora.com>
On 03-08-26, 13:17, Michael Riesch wrote:
> > + Two cells select the PHY type and the direction, so that the
> > + transmitter (DSI) and the receiver (CSI) can be described as
> > + independent consumers of the same PHY:
> > + - <PHY_TYPE_DPHY RK_DCPHY_DIR_TX>
> > + - <PHY_TYPE_DPHY RK_DCPHY_DIR_RX>
>
> How is that Rockchip specific? As you state above this is either MIPI
> CSI or MIPI DSI, two perfectly standard protocols.
>
> @all Would it be reasonable to introduce PHY_TYPE_CSI and PHY_TYPE_DSI?
I think yes...
--
~Vinod
--
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: Vinod Koul <vkoul@kernel.org>
To: Michael Riesch <michael.riesch@collabora.com>
Cc: jason98166@gmail.com, Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Guochun Huang <hero.huang@rock-chips.com>,
Philipp Zabel <p.zabel@pengutronix.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
Subject: Re: [PATCH v2 1/4] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys
Date: Thu, 6 Aug 2026 21:26:53 +0530 [thread overview]
Message-ID: <anSuxfeitSqmSHNr@vaman> (raw)
In-Reply-To: <82da3622-9c3a-454c-87bc-fb4ec7adb68d@collabora.com>
On 03-08-26, 13:17, Michael Riesch wrote:
> > + Two cells select the PHY type and the direction, so that the
> > + transmitter (DSI) and the receiver (CSI) can be described as
> > + independent consumers of the same PHY:
> > + - <PHY_TYPE_DPHY RK_DCPHY_DIR_TX>
> > + - <PHY_TYPE_DPHY RK_DCPHY_DIR_RX>
>
> How is that Rockchip specific? As you state above this is either MIPI
> CSI or MIPI DSI, two perfectly standard protocols.
>
> @all Would it be reasonable to introduce PHY_TYPE_CSI and PHY_TYPE_DSI?
I think yes...
--
~Vinod
next prev parent reply other threads:[~2026-08-06 15:57 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 14:55 [PATCH v2 0/4] phy: rockchip-samsung-dcphy: support the D-PHY receiver direction Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` [PATCH v2 1/4] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 15:02 ` sashiko-bot
2026-07-26 15:02 ` sashiko-bot
2026-08-03 11:17 ` Michael Riesch
2026-08-03 11:17 ` Michael Riesch
2026-08-03 11:17 ` Michael Riesch
2026-08-06 15:56 ` Vinod Koul [this message]
2026-08-06 15:56 ` Vinod Koul
2026-08-06 15:56 ` Vinod Koul
2026-08-07 21:33 ` Michael Riesch
2026-08-07 21:33 ` Michael Riesch
2026-08-07 21:33 ` Michael Riesch
2026-08-06 16:14 ` Bryan O'Donoghue
2026-08-06 16:14 ` Bryan O'Donoghue
2026-08-06 16:14 ` Bryan O'Donoghue
2026-07-26 14:55 ` [PATCH v2 2/4] phy: rockchip-samsung-dcphy: factor MIPI D-PHY power on/off into helpers Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-08-06 16:17 ` Bryan O'Donoghue
2026-08-06 16:17 ` Bryan O'Donoghue
2026-08-06 16:17 ` Bryan O'Donoghue
2026-08-06 19:31 ` Sebastian Reichel
2026-08-06 19:31 ` Sebastian Reichel
2026-08-06 19:31 ` Sebastian Reichel
2026-08-07 9:09 ` Bryan O'Donoghue
2026-08-07 9:09 ` Bryan O'Donoghue
2026-08-07 9:09 ` Bryan O'Donoghue
2026-07-26 14:55 ` [PATCH v2 3/4] phy: rockchip-samsung-dcphy: model TX and RX as separate PHYs Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-08-03 12:05 ` Michael Riesch
2026-08-03 12:05 ` Michael Riesch
2026-08-03 12:05 ` Michael Riesch
2026-08-04 5:38 ` 楊智成
2026-08-04 5:38 ` 楊智成
2026-08-04 5:38 ` 楊智成
2026-08-07 22:59 ` Michael Riesch
2026-08-07 22:59 ` Michael Riesch
2026-08-07 22:59 ` Michael Riesch
2026-07-26 14:55 ` [PATCH v2 4/4] phy: rockchip-samsung-dcphy: add MIPI D-PHY receiver support Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 15:07 ` sashiko-bot
2026-07-26 15:07 ` sashiko-bot
2026-07-27 2:01 ` 楊智成
2026-07-27 2:01 ` 楊智成
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=anSuxfeitSqmSHNr@vaman \
--to=vkoul@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=hero.huang@rock-chips.com \
--cc=jason98166@gmail.com \
--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=michael.riesch@collabora.com \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@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.