[PATCH v4 1/7] dt-bindings: phy: Add PHY_TYPE_DSI and PHY_TYPE_CSI definitions
Jason Yang via B4 Relay <[email protected]>
| Newsgroups | org.infradead.lists.linux-phy,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-rockchip,org.kernel.feeds.b4-sent,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
From: Jason Yang <[email protected]> A MIPI D-PHY or C-PHY can be a transmitter (DSI) or a receiver (CSI), and in some PHY blocks both work at the same time. The existing PHY_TYPE_DPHY and PHY_TYPE_CPHY cannot tell whether a consumer wants the transmitter or the receiver. Add PHY_TYPE_DSI and PHY_TYPE_CSI, so that a binding can select both D-PHY or C-PHY and transmitter or receiver. They do not replace PHY_TYPE_DPHY/PHY_TYPE_CPHY, which remain the right choice where a cell selects the mode. The first user is the Rockchip RK3588 MIPI DC-PHY binding. Suggested-by: Michael Riesch <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jason Yang <[email protected]> --- include/dt-bindings/phy/phy.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/dt-bindings/phy/phy.h b/include/dt-bindings/phy/phy.h index 979b5dfd8353..8ee3f88e6d80 100644 --- a/include/dt-bindings/phy/phy.h +++ b/include/dt-bindings/phy/phy.h @@ -24,6 +24,8 @@ #define PHY_TYPE_CPHY 11 #define PHY_TYPE_USXGMII 12 #define PHY_TYPE_XAUI 13 +#define PHY_TYPE_DSI 14 +#define PHY_TYPE_CSI 15 #define PHY_POL_NORMAL 0 #define PHY_POL_INVERT 1 -- 2.43.0 -- linux-phy mailing list [email protected] https://lists.infradead.org/mailman/listinfo/linux-phy