[PATCH v3 1/5] dt-bindings: phy: Add PHY_TYPE_DSI and PHY_TYPE_CSI definitions
Jason Yang <[email protected]>
| Newsgroups | org.kernel.feeds.b4-sent,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-phy,org.infradead.lists.linux-rockchip,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
MIPI D-PHY and C-PHY blocks are increasingly direction-agnostic: the same PHY IP can drive a MIPI DSI display or receive from a MIPI CSI-2 camera, and combo blocks like the Samsung IP on RK3588 expose both directions to independent consumers at the same time. A binding that needs to tell the two consumers apart has nothing generic to reach for: most constants in this header name a protocol (PHY_TYPE_USB3, PHY_TYPE_DP, ...), while the MIPI entries name only the electrical layer. Add PHY_TYPE_DSI and PHY_TYPE_CSI to select a PHY by the MIPI protocol it speaks, which also implies the direction. They do not replace PHY_TYPE_DPHY/PHY_TYPE_CPHY, which remain the right choice where the cell selects the electrical layer. First user is the Rockchip RK3588 MIPI DC-PHY binding. Suggested-by: Michael Riesch <[email protected]> Signed-off-by: Jason Yang <[email protected]> Assisted-by: Claude:claude-fable-5 --- 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