* [PATCH] drm/phy: rockchip: fix RK3506 DSI low-power command handling
@ 2026-11-21 7:58 ` ZhuXiangyu
0 siblings, 0 replies; 8+ messages in thread
From: ZhuXiangyu @ 2026-11-21 7:58 UTC (permalink / raw)
To: Vinod Koul, Neil Armstrong, Heiko Stuebner, Sandy Huang
Cc: Andy Yan, Maarten Lankhorst, Maxime Ripard, Thomas Zimmermann,
David Airlie, Simona Vetter, Manivannan Sadhasivam, linux-phy,
dri-devel, linux-arm-kernel, linux-rockchip, linux-kernel,
ZhuXiangyu
Two bugs keep the RK3506 MIPI-DSI link from initialising a panel: the
DPHY programs the wrong high-speed timing entry, and the PHY data lanes
are never enabled in the GRF.
1. phy-rockchip-inno-dsidphy picks the wrong HS timing entry
The 1.5 GHz inno DSI PHY timing table stores its rates in Mbps while
the other tables and the lookup use Hz. The mode enable code compares
inno->pll.rate in Hz (e.g. 372000000) against timings[].rate in Mbps
(e.g. 400), so the comparison never matches. The loop runs to the end
and the last, fastest entry is used, which programs a TLPX/LPX
counter that is far too large. The panel then cannot decode the
low-power DCS commands and stays in sleep mode, so the display stays
black even though the LP packets are visible on the data lane.
Convert the 1.5 GHz timing table rates to Hz so that the lookup
selects the correct entry.
2. The RK3506 DSI GRF lane enable bits are never written
rk3506_chip_data only clears the turnaround / force-stop fields, so
the PHY data lanes stay disabled unless the boot loader happens to
enable them. Program RK3506_DSI_PHY_ENABLE_LANE0/1 as well.
Tested on the RK3506B JerryTech board: the panel now receives the init
sequence over LP and the framebuffer console is visible.
Signed-off-by: ZhuXiangyu <1194781887@qq.com>
---
.../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 6 +++-
.../phy/rockchip/phy-rockchip-inno-dsidphy.c | 28 +++++++++----------
2 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
index 30d6f83c..116cc140 100644
--- a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
+++ b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
@@ -199,6 +199,8 @@
#define RK3506_SYS_GRF_SOC_CON6 0x0018
#define RK3506_DSI_FORCETXSTOPMODE (0xf << 4)
+#define RK3506_DSI_PHY_ENABLE_LANE1 BIT(9)
+#define RK3506_DSI_PHY_ENABLE_LANE0 BIT(8)
#define RK3506_DSI_TURNDISABLE BIT(2)
#define RK3506_DSI_FORCERXMODE BIT(0)
@@ -1727,7 +1729,9 @@ static const struct rockchip_dw_dsi_chip_data rk3506_chip_data[] = {
.lanecfg1_grf_reg = RK3506_SYS_GRF_SOC_CON6,
.lanecfg1 = (FIELD_PREP_WM16_CONST(RK3506_DSI_TURNDISABLE, 0) |
FIELD_PREP_WM16_CONST(RK3506_DSI_FORCERXMODE, 0) |
- FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0)),
+ FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE0, 1) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE1, 1)),
.max_data_lanes = 2,
.max_bit_rate_per_lane = 1500000000UL,
.dphy_get_timing = dw_mipi_dsi_phy_px30_get_timing,
diff --git a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
index 6ad04b0c..fcf7aa17 100644
--- a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
+++ b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
@@ -282,20 +282,20 @@ struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1ghz[] = {
static const
struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1_5ghz[] = {
- { 110, 0x02, 0x7f, 0x16, 0x02, 0x02},
- { 150, 0x02, 0x7f, 0x16, 0x03, 0x02},
- { 200, 0x02, 0x7f, 0x17, 0x04, 0x02},
- { 250, 0x02, 0x7f, 0x17, 0x05, 0x04},
- { 300, 0x02, 0x7f, 0x18, 0x06, 0x04},
- { 400, 0x03, 0x7e, 0x19, 0x07, 0x04},
- { 500, 0x03, 0x7c, 0x1b, 0x07, 0x08},
- { 600, 0x03, 0x70, 0x1d, 0x08, 0x10},
- { 700, 0x05, 0x40, 0x1e, 0x08, 0x30},
- { 800, 0x05, 0x02, 0x1f, 0x09, 0x30},
- {1000, 0x05, 0x08, 0x20, 0x09, 0x30},
- {1200, 0x06, 0x03, 0x32, 0x14, 0x0f},
- {1400, 0x09, 0x03, 0x32, 0x14, 0x0f},
- {1500, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
+ { 110000000, 0x02, 0x7f, 0x16, 0x02, 0x02},
+ { 150000000, 0x02, 0x7f, 0x16, 0x03, 0x02},
+ { 200000000, 0x02, 0x7f, 0x17, 0x04, 0x02},
+ { 250000000, 0x02, 0x7f, 0x17, 0x05, 0x04},
+ { 300000000, 0x02, 0x7f, 0x18, 0x06, 0x04},
+ { 400000000, 0x03, 0x7e, 0x19, 0x07, 0x04},
+ { 500000000, 0x03, 0x7c, 0x1b, 0x07, 0x08},
+ { 600000000, 0x03, 0x70, 0x1d, 0x08, 0x10},
+ { 700000000, 0x05, 0x40, 0x1e, 0x08, 0x30},
+ { 800000000, 0x05, 0x02, 0x1f, 0x09, 0x30},
+ {1000000000, 0x05, 0x08, 0x20, 0x09, 0x30},
+ {1200000000, 0x06, 0x03, 0x32, 0x14, 0x0f},
+ {1400000000, 0x09, 0x03, 0x32, 0x14, 0x0f},
+ {1500000000, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
};
static const
--
2.47.3
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH] drm/phy: rockchip: fix RK3506 DSI low-power command handling
@ 2026-11-21 7:58 ` ZhuXiangyu
0 siblings, 0 replies; 8+ messages in thread
From: ZhuXiangyu @ 2026-11-21 7:58 UTC (permalink / raw)
To: Vinod Koul, Neil Armstrong, Heiko Stuebner, Sandy Huang
Cc: Andy Yan, Maarten Lankhorst, Maxime Ripard, Thomas Zimmermann,
David Airlie, Simona Vetter, Manivannan Sadhasivam, linux-phy,
dri-devel, linux-arm-kernel, linux-rockchip, linux-kernel,
ZhuXiangyu
Two bugs keep the RK3506 MIPI-DSI link from initialising a panel: the
DPHY programs the wrong high-speed timing entry, and the PHY data lanes
are never enabled in the GRF.
1. phy-rockchip-inno-dsidphy picks the wrong HS timing entry
The 1.5 GHz inno DSI PHY timing table stores its rates in Mbps while
the other tables and the lookup use Hz. The mode enable code compares
inno->pll.rate in Hz (e.g. 372000000) against timings[].rate in Mbps
(e.g. 400), so the comparison never matches. The loop runs to the end
and the last, fastest entry is used, which programs a TLPX/LPX
counter that is far too large. The panel then cannot decode the
low-power DCS commands and stays in sleep mode, so the display stays
black even though the LP packets are visible on the data lane.
Convert the 1.5 GHz timing table rates to Hz so that the lookup
selects the correct entry.
2. The RK3506 DSI GRF lane enable bits are never written
rk3506_chip_data only clears the turnaround / force-stop fields, so
the PHY data lanes stay disabled unless the boot loader happens to
enable them. Program RK3506_DSI_PHY_ENABLE_LANE0/1 as well.
Tested on the RK3506B JerryTech board: the panel now receives the init
sequence over LP and the framebuffer console is visible.
Signed-off-by: ZhuXiangyu <1194781887@qq.com>
---
.../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 6 +++-
.../phy/rockchip/phy-rockchip-inno-dsidphy.c | 28 +++++++++----------
2 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
index 30d6f83c..116cc140 100644
--- a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
+++ b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
@@ -199,6 +199,8 @@
#define RK3506_SYS_GRF_SOC_CON6 0x0018
#define RK3506_DSI_FORCETXSTOPMODE (0xf << 4)
+#define RK3506_DSI_PHY_ENABLE_LANE1 BIT(9)
+#define RK3506_DSI_PHY_ENABLE_LANE0 BIT(8)
#define RK3506_DSI_TURNDISABLE BIT(2)
#define RK3506_DSI_FORCERXMODE BIT(0)
@@ -1727,7 +1729,9 @@ static const struct rockchip_dw_dsi_chip_data rk3506_chip_data[] = {
.lanecfg1_grf_reg = RK3506_SYS_GRF_SOC_CON6,
.lanecfg1 = (FIELD_PREP_WM16_CONST(RK3506_DSI_TURNDISABLE, 0) |
FIELD_PREP_WM16_CONST(RK3506_DSI_FORCERXMODE, 0) |
- FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0)),
+ FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE0, 1) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE1, 1)),
.max_data_lanes = 2,
.max_bit_rate_per_lane = 1500000000UL,
.dphy_get_timing = dw_mipi_dsi_phy_px30_get_timing,
diff --git a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
index 6ad04b0c..fcf7aa17 100644
--- a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
+++ b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
@@ -282,20 +282,20 @@ struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1ghz[] = {
static const
struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1_5ghz[] = {
- { 110, 0x02, 0x7f, 0x16, 0x02, 0x02},
- { 150, 0x02, 0x7f, 0x16, 0x03, 0x02},
- { 200, 0x02, 0x7f, 0x17, 0x04, 0x02},
- { 250, 0x02, 0x7f, 0x17, 0x05, 0x04},
- { 300, 0x02, 0x7f, 0x18, 0x06, 0x04},
- { 400, 0x03, 0x7e, 0x19, 0x07, 0x04},
- { 500, 0x03, 0x7c, 0x1b, 0x07, 0x08},
- { 600, 0x03, 0x70, 0x1d, 0x08, 0x10},
- { 700, 0x05, 0x40, 0x1e, 0x08, 0x30},
- { 800, 0x05, 0x02, 0x1f, 0x09, 0x30},
- {1000, 0x05, 0x08, 0x20, 0x09, 0x30},
- {1200, 0x06, 0x03, 0x32, 0x14, 0x0f},
- {1400, 0x09, 0x03, 0x32, 0x14, 0x0f},
- {1500, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
+ { 110000000, 0x02, 0x7f, 0x16, 0x02, 0x02},
+ { 150000000, 0x02, 0x7f, 0x16, 0x03, 0x02},
+ { 200000000, 0x02, 0x7f, 0x17, 0x04, 0x02},
+ { 250000000, 0x02, 0x7f, 0x17, 0x05, 0x04},
+ { 300000000, 0x02, 0x7f, 0x18, 0x06, 0x04},
+ { 400000000, 0x03, 0x7e, 0x19, 0x07, 0x04},
+ { 500000000, 0x03, 0x7c, 0x1b, 0x07, 0x08},
+ { 600000000, 0x03, 0x70, 0x1d, 0x08, 0x10},
+ { 700000000, 0x05, 0x40, 0x1e, 0x08, 0x30},
+ { 800000000, 0x05, 0x02, 0x1f, 0x09, 0x30},
+ {1000000000, 0x05, 0x08, 0x20, 0x09, 0x30},
+ {1200000000, 0x06, 0x03, 0x32, 0x14, 0x0f},
+ {1400000000, 0x09, 0x03, 0x32, 0x14, 0x0f},
+ {1500000000, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
};
static const
--
2.47.3
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH] drm/phy: rockchip: fix RK3506 DSI low-power command handling
@ 2026-11-21 7:58 ` ZhuXiangyu
0 siblings, 0 replies; 8+ messages in thread
From: ZhuXiangyu @ 2026-11-21 7:58 UTC (permalink / raw)
To: Vinod Koul, Neil Armstrong, Heiko Stuebner, Sandy Huang
Cc: Andy Yan, Maarten Lankhorst, Maxime Ripard, Thomas Zimmermann,
David Airlie, Simona Vetter, Manivannan Sadhasivam, linux-phy,
dri-devel, linux-arm-kernel, linux-rockchip, linux-kernel,
ZhuXiangyu
Two bugs keep the RK3506 MIPI-DSI link from initialising a panel: the
DPHY programs the wrong high-speed timing entry, and the PHY data lanes
are never enabled in the GRF.
1. phy-rockchip-inno-dsidphy picks the wrong HS timing entry
The 1.5 GHz inno DSI PHY timing table stores its rates in Mbps while
the other tables and the lookup use Hz. The mode enable code compares
inno->pll.rate in Hz (e.g. 372000000) against timings[].rate in Mbps
(e.g. 400), so the comparison never matches. The loop runs to the end
and the last, fastest entry is used, which programs a TLPX/LPX
counter that is far too large. The panel then cannot decode the
low-power DCS commands and stays in sleep mode, so the display stays
black even though the LP packets are visible on the data lane.
Convert the 1.5 GHz timing table rates to Hz so that the lookup
selects the correct entry.
2. The RK3506 DSI GRF lane enable bits are never written
rk3506_chip_data only clears the turnaround / force-stop fields, so
the PHY data lanes stay disabled unless the boot loader happens to
enable them. Program RK3506_DSI_PHY_ENABLE_LANE0/1 as well.
Tested on the RK3506B JerryTech board: the panel now receives the init
sequence over LP and the framebuffer console is visible.
Signed-off-by: ZhuXiangyu <1194781887@qq.com>
---
.../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 6 +++-
.../phy/rockchip/phy-rockchip-inno-dsidphy.c | 28 +++++++++----------
2 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
index 30d6f83c..116cc140 100644
--- a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
+++ b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
@@ -199,6 +199,8 @@
#define RK3506_SYS_GRF_SOC_CON6 0x0018
#define RK3506_DSI_FORCETXSTOPMODE (0xf << 4)
+#define RK3506_DSI_PHY_ENABLE_LANE1 BIT(9)
+#define RK3506_DSI_PHY_ENABLE_LANE0 BIT(8)
#define RK3506_DSI_TURNDISABLE BIT(2)
#define RK3506_DSI_FORCERXMODE BIT(0)
@@ -1727,7 +1729,9 @@ static const struct rockchip_dw_dsi_chip_data rk3506_chip_data[] = {
.lanecfg1_grf_reg = RK3506_SYS_GRF_SOC_CON6,
.lanecfg1 = (FIELD_PREP_WM16_CONST(RK3506_DSI_TURNDISABLE, 0) |
FIELD_PREP_WM16_CONST(RK3506_DSI_FORCERXMODE, 0) |
- FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0)),
+ FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE0, 1) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE1, 1)),
.max_data_lanes = 2,
.max_bit_rate_per_lane = 1500000000UL,
.dphy_get_timing = dw_mipi_dsi_phy_px30_get_timing,
diff --git a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
index 6ad04b0c..fcf7aa17 100644
--- a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
+++ b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
@@ -282,20 +282,20 @@ struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1ghz[] = {
static const
struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1_5ghz[] = {
- { 110, 0x02, 0x7f, 0x16, 0x02, 0x02},
- { 150, 0x02, 0x7f, 0x16, 0x03, 0x02},
- { 200, 0x02, 0x7f, 0x17, 0x04, 0x02},
- { 250, 0x02, 0x7f, 0x17, 0x05, 0x04},
- { 300, 0x02, 0x7f, 0x18, 0x06, 0x04},
- { 400, 0x03, 0x7e, 0x19, 0x07, 0x04},
- { 500, 0x03, 0x7c, 0x1b, 0x07, 0x08},
- { 600, 0x03, 0x70, 0x1d, 0x08, 0x10},
- { 700, 0x05, 0x40, 0x1e, 0x08, 0x30},
- { 800, 0x05, 0x02, 0x1f, 0x09, 0x30},
- {1000, 0x05, 0x08, 0x20, 0x09, 0x30},
- {1200, 0x06, 0x03, 0x32, 0x14, 0x0f},
- {1400, 0x09, 0x03, 0x32, 0x14, 0x0f},
- {1500, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
+ { 110000000, 0x02, 0x7f, 0x16, 0x02, 0x02},
+ { 150000000, 0x02, 0x7f, 0x16, 0x03, 0x02},
+ { 200000000, 0x02, 0x7f, 0x17, 0x04, 0x02},
+ { 250000000, 0x02, 0x7f, 0x17, 0x05, 0x04},
+ { 300000000, 0x02, 0x7f, 0x18, 0x06, 0x04},
+ { 400000000, 0x03, 0x7e, 0x19, 0x07, 0x04},
+ { 500000000, 0x03, 0x7c, 0x1b, 0x07, 0x08},
+ { 600000000, 0x03, 0x70, 0x1d, 0x08, 0x10},
+ { 700000000, 0x05, 0x40, 0x1e, 0x08, 0x30},
+ { 800000000, 0x05, 0x02, 0x1f, 0x09, 0x30},
+ {1000000000, 0x05, 0x08, 0x20, 0x09, 0x30},
+ {1200000000, 0x06, 0x03, 0x32, 0x14, 0x0f},
+ {1400000000, 0x09, 0x03, 0x32, 0x14, 0x0f},
+ {1500000000, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
};
static const
--
2.47.3
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/phy: rockchip: fix RK3506 DSI low-power command handling
2026-11-21 7:58 ` ZhuXiangyu
@ 2026-11-21 8:03 ` sashiko-bot
-1 siblings, 0 replies; 8+ messages in thread
From: sashiko-bot @ 2026-11-21 8:03 UTC (permalink / raw)
To: ZhuXiangyu; +Cc: linux-phy, dri-devel, vkoul, neil.armstrong, olteanv
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/phy: rockchip: missing Fixes: trailers for RK3506 DSI and
DPHY fixes
--
commit d9fc037cd18d975d189c46c8a1d083b08c417a92
Author: ZhuXiangyu <1194781887@qq.com>
> drm/phy: rockchip: fix RK3506 DSI low-power command handling
>
> Two bugs keep the RK3506 MIPI-DSI link from initialising a panel: the
> DPHY programs the wrong high-speed timing entry, and the PHY data lanes
> are never enabled in the GRF.
>
> 1. phy-rockchip-inno-dsidphy picks the wrong HS timing entry
>
> The 1.5 GHz inno DSI PHY timing table stores its rates in Mbps while
> the other tables and the lookup use Hz. The mode enable code compares
> inno->pll.rate in Hz (e.g. 372000000) against timings[].rate in Mbps
> (e.g. 400), so the comparison never matches. The loop runs to the end
> and the last, fastest entry is used, which programs a TLPX/LPX
> counter that is far too large. The panel then cannot decode the
> low-power DCS commands and stays in sleep mode, so the display stays
> black even though the LP packets are visible on the data lane.
>
> Convert the 1.5 GHz timing table rates to Hz so that the lookup
> selects the correct entry.
>
> 2. The RK3506 DSI GRF lane enable bits are never written
>
> rk3506_chip_data only clears the turnaround / force-stop fields, so
> the PHY data lanes stay disabled unless the boot loader happens to
> enable them. Program RK3506_DSI_PHY_ENABLE_LANE0/1 as well.
>
> Tested on the RK3506B JerryTech board: the panel now receives the init
> sequence over LP and the framebuffer console is visible.
>
> Signed-off-by: ZhuXiangyu <1194781887@qq.com>
[Severity: Low]
This fixes bugs in the RK3506 DPHY and DSI support. Should the commit
message include:
Fixes: 785a9d5bb145 ("phy: rockchip: inno-dsidphy: Add support for rk3506")
Fixes: cabeacc7eadc ("drm/rockchip: dsi: Add support for rk3506")
--
Sashiko AI review · https://sashiko.dev/#/patchset/tencent_6F7C9E04169BCBAE4E162DAA3DCD5395B209@qq.com?part=1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/phy: rockchip: fix RK3506 DSI low-power command handling
@ 2026-11-21 8:03 ` sashiko-bot
0 siblings, 0 replies; 8+ messages in thread
From: sashiko-bot @ 2026-11-21 8:03 UTC (permalink / raw)
To: ZhuXiangyu; +Cc: linux-phy, dri-devel, vkoul, neil.armstrong, olteanv
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/phy: rockchip: missing Fixes: trailers for RK3506 DSI and
DPHY fixes
--
commit d9fc037cd18d975d189c46c8a1d083b08c417a92
Author: ZhuXiangyu <1194781887@qq.com>
> drm/phy: rockchip: fix RK3506 DSI low-power command handling
>
> Two bugs keep the RK3506 MIPI-DSI link from initialising a panel: the
> DPHY programs the wrong high-speed timing entry, and the PHY data lanes
> are never enabled in the GRF.
>
> 1. phy-rockchip-inno-dsidphy picks the wrong HS timing entry
>
> The 1.5 GHz inno DSI PHY timing table stores its rates in Mbps while
> the other tables and the lookup use Hz. The mode enable code compares
> inno->pll.rate in Hz (e.g. 372000000) against timings[].rate in Mbps
> (e.g. 400), so the comparison never matches. The loop runs to the end
> and the last, fastest entry is used, which programs a TLPX/LPX
> counter that is far too large. The panel then cannot decode the
> low-power DCS commands and stays in sleep mode, so the display stays
> black even though the LP packets are visible on the data lane.
>
> Convert the 1.5 GHz timing table rates to Hz so that the lookup
> selects the correct entry.
>
> 2. The RK3506 DSI GRF lane enable bits are never written
>
> rk3506_chip_data only clears the turnaround / force-stop fields, so
> the PHY data lanes stay disabled unless the boot loader happens to
> enable them. Program RK3506_DSI_PHY_ENABLE_LANE0/1 as well.
>
> Tested on the RK3506B JerryTech board: the panel now receives the init
> sequence over LP and the framebuffer console is visible.
>
> Signed-off-by: ZhuXiangyu <1194781887@qq.com>
[Severity: Low]
This fixes bugs in the RK3506 DPHY and DSI support. Should the commit
message include:
Fixes: 785a9d5bb145 ("phy: rockchip: inno-dsidphy: Add support for rk3506")
Fixes: cabeacc7eadc ("drm/rockchip: dsi: Add support for rk3506")
--
Sashiko AI review · https://sashiko.dev/#/patchset/tencent_6F7C9E04169BCBAE4E162DAA3DCD5395B209@qq.com?part=1
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH] drm/phy: rockchip: fix RK3506 DSI low-power command handling
@ 2026-11-21 8:05 ` ZhuXiangyu
0 siblings, 0 replies; 8+ messages in thread
From: ZhuXiangyu @ 2026-11-21 8:05 UTC (permalink / raw)
To: Vinod Koul, Neil Armstrong, Heiko Stuebner, Sandy Huang
Cc: Andy Yan, Maarten Lankhorst, Maxime Ripard, Thomas Zimmermann,
David Airlie, Simona Vetter, Manivannan Sadhasivam, linux-phy,
dri-devel, linux-arm-kernel, linux-rockchip, linux-kernel,
ZhuXiangyu
Two bugs keep the RK3506 MIPI-DSI link from initialising a panel: the
DPHY programs the wrong high-speed timing entry, and the PHY data lanes
are never enabled in the GRF.
1. phy-rockchip-inno-dsidphy picks the wrong HS timing entry
The 1.5 GHz inno DSI PHY timing table stores its rates in Mbps while
the other tables and the lookup use Hz. The mode enable code compares
inno->pll.rate in Hz (e.g. 372000000) against timings[].rate in Mbps
(e.g. 400), so the comparison never matches. The loop runs to the end
and the last, fastest entry is used, which programs a TLPX/LPX
counter that is far too large. The panel then cannot decode the
low-power DCS commands and stays in sleep mode, so the display stays
black even though the LP packets are visible on the data lane.
Convert the 1.5 GHz timing table rates to Hz so that the lookup
selects the correct entry.
2. The RK3506 DSI GRF lane enable bits are never written
rk3506_chip_data only clears the turnaround / force-stop fields, so
the PHY data lanes stay disabled unless the boot loader happens to
enable them. Program RK3506_DSI_PHY_ENABLE_LANE0/1 as well.
Tested on the RK3506B JerryTech board: the panel now receives the init
sequence over LP and the framebuffer console is visible.
Fixes: 785a9d5bb145 ("phy: rockchip: inno-dsidphy: Add support for rk3506")
Fixes: cabeacc7eadc ("drm/rockchip: dsi: Add support for rk3506")
Signed-off-by: ZhuXiangyu <1194781887@qq.com>
---
.../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 6 +++-
.../phy/rockchip/phy-rockchip-inno-dsidphy.c | 28 +++++++++----------
2 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
index 30d6f83c..116cc140 100644
--- a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
+++ b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
@@ -199,6 +199,8 @@
#define RK3506_SYS_GRF_SOC_CON6 0x0018
#define RK3506_DSI_FORCETXSTOPMODE (0xf << 4)
+#define RK3506_DSI_PHY_ENABLE_LANE1 BIT(9)
+#define RK3506_DSI_PHY_ENABLE_LANE0 BIT(8)
#define RK3506_DSI_TURNDISABLE BIT(2)
#define RK3506_DSI_FORCERXMODE BIT(0)
@@ -1727,7 +1729,9 @@ static const struct rockchip_dw_dsi_chip_data rk3506_chip_data[] = {
.lanecfg1_grf_reg = RK3506_SYS_GRF_SOC_CON6,
.lanecfg1 = (FIELD_PREP_WM16_CONST(RK3506_DSI_TURNDISABLE, 0) |
FIELD_PREP_WM16_CONST(RK3506_DSI_FORCERXMODE, 0) |
- FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0)),
+ FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE0, 1) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE1, 1)),
.max_data_lanes = 2,
.max_bit_rate_per_lane = 1500000000UL,
.dphy_get_timing = dw_mipi_dsi_phy_px30_get_timing,
diff --git a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
index 6ad04b0c..fcf7aa17 100644
--- a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
+++ b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
@@ -282,20 +282,20 @@ struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1ghz[] = {
static const
struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1_5ghz[] = {
- { 110, 0x02, 0x7f, 0x16, 0x02, 0x02},
- { 150, 0x02, 0x7f, 0x16, 0x03, 0x02},
- { 200, 0x02, 0x7f, 0x17, 0x04, 0x02},
- { 250, 0x02, 0x7f, 0x17, 0x05, 0x04},
- { 300, 0x02, 0x7f, 0x18, 0x06, 0x04},
- { 400, 0x03, 0x7e, 0x19, 0x07, 0x04},
- { 500, 0x03, 0x7c, 0x1b, 0x07, 0x08},
- { 600, 0x03, 0x70, 0x1d, 0x08, 0x10},
- { 700, 0x05, 0x40, 0x1e, 0x08, 0x30},
- { 800, 0x05, 0x02, 0x1f, 0x09, 0x30},
- {1000, 0x05, 0x08, 0x20, 0x09, 0x30},
- {1200, 0x06, 0x03, 0x32, 0x14, 0x0f},
- {1400, 0x09, 0x03, 0x32, 0x14, 0x0f},
- {1500, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
+ { 110000000, 0x02, 0x7f, 0x16, 0x02, 0x02},
+ { 150000000, 0x02, 0x7f, 0x16, 0x03, 0x02},
+ { 200000000, 0x02, 0x7f, 0x17, 0x04, 0x02},
+ { 250000000, 0x02, 0x7f, 0x17, 0x05, 0x04},
+ { 300000000, 0x02, 0x7f, 0x18, 0x06, 0x04},
+ { 400000000, 0x03, 0x7e, 0x19, 0x07, 0x04},
+ { 500000000, 0x03, 0x7c, 0x1b, 0x07, 0x08},
+ { 600000000, 0x03, 0x70, 0x1d, 0x08, 0x10},
+ { 700000000, 0x05, 0x40, 0x1e, 0x08, 0x30},
+ { 800000000, 0x05, 0x02, 0x1f, 0x09, 0x30},
+ {1000000000, 0x05, 0x08, 0x20, 0x09, 0x30},
+ {1200000000, 0x06, 0x03, 0x32, 0x14, 0x0f},
+ {1400000000, 0x09, 0x03, 0x32, 0x14, 0x0f},
+ {1500000000, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
};
static const
--
2.47.3
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH] drm/phy: rockchip: fix RK3506 DSI low-power command handling
@ 2026-11-21 8:05 ` ZhuXiangyu
0 siblings, 0 replies; 8+ messages in thread
From: ZhuXiangyu @ 2026-11-21 8:05 UTC (permalink / raw)
To: Vinod Koul, Neil Armstrong, Heiko Stuebner, Sandy Huang
Cc: Andy Yan, Maarten Lankhorst, Maxime Ripard, Thomas Zimmermann,
David Airlie, Simona Vetter, Manivannan Sadhasivam, linux-phy,
dri-devel, linux-arm-kernel, linux-rockchip, linux-kernel,
ZhuXiangyu
Two bugs keep the RK3506 MIPI-DSI link from initialising a panel: the
DPHY programs the wrong high-speed timing entry, and the PHY data lanes
are never enabled in the GRF.
1. phy-rockchip-inno-dsidphy picks the wrong HS timing entry
The 1.5 GHz inno DSI PHY timing table stores its rates in Mbps while
the other tables and the lookup use Hz. The mode enable code compares
inno->pll.rate in Hz (e.g. 372000000) against timings[].rate in Mbps
(e.g. 400), so the comparison never matches. The loop runs to the end
and the last, fastest entry is used, which programs a TLPX/LPX
counter that is far too large. The panel then cannot decode the
low-power DCS commands and stays in sleep mode, so the display stays
black even though the LP packets are visible on the data lane.
Convert the 1.5 GHz timing table rates to Hz so that the lookup
selects the correct entry.
2. The RK3506 DSI GRF lane enable bits are never written
rk3506_chip_data only clears the turnaround / force-stop fields, so
the PHY data lanes stay disabled unless the boot loader happens to
enable them. Program RK3506_DSI_PHY_ENABLE_LANE0/1 as well.
Tested on the RK3506B JerryTech board: the panel now receives the init
sequence over LP and the framebuffer console is visible.
Fixes: 785a9d5bb145 ("phy: rockchip: inno-dsidphy: Add support for rk3506")
Fixes: cabeacc7eadc ("drm/rockchip: dsi: Add support for rk3506")
Signed-off-by: ZhuXiangyu <1194781887@qq.com>
---
.../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 6 +++-
.../phy/rockchip/phy-rockchip-inno-dsidphy.c | 28 +++++++++----------
2 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
index 30d6f83c..116cc140 100644
--- a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
+++ b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
@@ -199,6 +199,8 @@
#define RK3506_SYS_GRF_SOC_CON6 0x0018
#define RK3506_DSI_FORCETXSTOPMODE (0xf << 4)
+#define RK3506_DSI_PHY_ENABLE_LANE1 BIT(9)
+#define RK3506_DSI_PHY_ENABLE_LANE0 BIT(8)
#define RK3506_DSI_TURNDISABLE BIT(2)
#define RK3506_DSI_FORCERXMODE BIT(0)
@@ -1727,7 +1729,9 @@ static const struct rockchip_dw_dsi_chip_data rk3506_chip_data[] = {
.lanecfg1_grf_reg = RK3506_SYS_GRF_SOC_CON6,
.lanecfg1 = (FIELD_PREP_WM16_CONST(RK3506_DSI_TURNDISABLE, 0) |
FIELD_PREP_WM16_CONST(RK3506_DSI_FORCERXMODE, 0) |
- FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0)),
+ FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE0, 1) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE1, 1)),
.max_data_lanes = 2,
.max_bit_rate_per_lane = 1500000000UL,
.dphy_get_timing = dw_mipi_dsi_phy_px30_get_timing,
diff --git a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
index 6ad04b0c..fcf7aa17 100644
--- a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
+++ b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
@@ -282,20 +282,20 @@ struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1ghz[] = {
static const
struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1_5ghz[] = {
- { 110, 0x02, 0x7f, 0x16, 0x02, 0x02},
- { 150, 0x02, 0x7f, 0x16, 0x03, 0x02},
- { 200, 0x02, 0x7f, 0x17, 0x04, 0x02},
- { 250, 0x02, 0x7f, 0x17, 0x05, 0x04},
- { 300, 0x02, 0x7f, 0x18, 0x06, 0x04},
- { 400, 0x03, 0x7e, 0x19, 0x07, 0x04},
- { 500, 0x03, 0x7c, 0x1b, 0x07, 0x08},
- { 600, 0x03, 0x70, 0x1d, 0x08, 0x10},
- { 700, 0x05, 0x40, 0x1e, 0x08, 0x30},
- { 800, 0x05, 0x02, 0x1f, 0x09, 0x30},
- {1000, 0x05, 0x08, 0x20, 0x09, 0x30},
- {1200, 0x06, 0x03, 0x32, 0x14, 0x0f},
- {1400, 0x09, 0x03, 0x32, 0x14, 0x0f},
- {1500, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
+ { 110000000, 0x02, 0x7f, 0x16, 0x02, 0x02},
+ { 150000000, 0x02, 0x7f, 0x16, 0x03, 0x02},
+ { 200000000, 0x02, 0x7f, 0x17, 0x04, 0x02},
+ { 250000000, 0x02, 0x7f, 0x17, 0x05, 0x04},
+ { 300000000, 0x02, 0x7f, 0x18, 0x06, 0x04},
+ { 400000000, 0x03, 0x7e, 0x19, 0x07, 0x04},
+ { 500000000, 0x03, 0x7c, 0x1b, 0x07, 0x08},
+ { 600000000, 0x03, 0x70, 0x1d, 0x08, 0x10},
+ { 700000000, 0x05, 0x40, 0x1e, 0x08, 0x30},
+ { 800000000, 0x05, 0x02, 0x1f, 0x09, 0x30},
+ {1000000000, 0x05, 0x08, 0x20, 0x09, 0x30},
+ {1200000000, 0x06, 0x03, 0x32, 0x14, 0x0f},
+ {1400000000, 0x09, 0x03, 0x32, 0x14, 0x0f},
+ {1500000000, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
};
static const
--
2.47.3
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH] drm/phy: rockchip: fix RK3506 DSI low-power command handling
@ 2026-11-21 8:05 ` ZhuXiangyu
0 siblings, 0 replies; 8+ messages in thread
From: ZhuXiangyu @ 2026-11-21 8:05 UTC (permalink / raw)
To: Vinod Koul, Neil Armstrong, Heiko Stuebner, Sandy Huang
Cc: Andy Yan, Maarten Lankhorst, Maxime Ripard, Thomas Zimmermann,
David Airlie, Simona Vetter, Manivannan Sadhasivam, linux-phy,
dri-devel, linux-arm-kernel, linux-rockchip, linux-kernel,
ZhuXiangyu
Two bugs keep the RK3506 MIPI-DSI link from initialising a panel: the
DPHY programs the wrong high-speed timing entry, and the PHY data lanes
are never enabled in the GRF.
1. phy-rockchip-inno-dsidphy picks the wrong HS timing entry
The 1.5 GHz inno DSI PHY timing table stores its rates in Mbps while
the other tables and the lookup use Hz. The mode enable code compares
inno->pll.rate in Hz (e.g. 372000000) against timings[].rate in Mbps
(e.g. 400), so the comparison never matches. The loop runs to the end
and the last, fastest entry is used, which programs a TLPX/LPX
counter that is far too large. The panel then cannot decode the
low-power DCS commands and stays in sleep mode, so the display stays
black even though the LP packets are visible on the data lane.
Convert the 1.5 GHz timing table rates to Hz so that the lookup
selects the correct entry.
2. The RK3506 DSI GRF lane enable bits are never written
rk3506_chip_data only clears the turnaround / force-stop fields, so
the PHY data lanes stay disabled unless the boot loader happens to
enable them. Program RK3506_DSI_PHY_ENABLE_LANE0/1 as well.
Tested on the RK3506B JerryTech board: the panel now receives the init
sequence over LP and the framebuffer console is visible.
Fixes: 785a9d5bb145 ("phy: rockchip: inno-dsidphy: Add support for rk3506")
Fixes: cabeacc7eadc ("drm/rockchip: dsi: Add support for rk3506")
Signed-off-by: ZhuXiangyu <1194781887@qq.com>
---
.../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 6 +++-
.../phy/rockchip/phy-rockchip-inno-dsidphy.c | 28 +++++++++----------
2 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
index 30d6f83c..116cc140 100644
--- a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
+++ b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
@@ -199,6 +199,8 @@
#define RK3506_SYS_GRF_SOC_CON6 0x0018
#define RK3506_DSI_FORCETXSTOPMODE (0xf << 4)
+#define RK3506_DSI_PHY_ENABLE_LANE1 BIT(9)
+#define RK3506_DSI_PHY_ENABLE_LANE0 BIT(8)
#define RK3506_DSI_TURNDISABLE BIT(2)
#define RK3506_DSI_FORCERXMODE BIT(0)
@@ -1727,7 +1729,9 @@ static const struct rockchip_dw_dsi_chip_data rk3506_chip_data[] = {
.lanecfg1_grf_reg = RK3506_SYS_GRF_SOC_CON6,
.lanecfg1 = (FIELD_PREP_WM16_CONST(RK3506_DSI_TURNDISABLE, 0) |
FIELD_PREP_WM16_CONST(RK3506_DSI_FORCERXMODE, 0) |
- FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0)),
+ FIELD_PREP_WM16_CONST(RK3506_DSI_FORCETXSTOPMODE, 0) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE0, 1) |
+ FIELD_PREP_WM16_CONST(RK3506_DSI_PHY_ENABLE_LANE1, 1)),
.max_data_lanes = 2,
.max_bit_rate_per_lane = 1500000000UL,
.dphy_get_timing = dw_mipi_dsi_phy_px30_get_timing,
diff --git a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
index 6ad04b0c..fcf7aa17 100644
--- a/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
+++ b/drivers/phy/rockchip/phy-rockchip-inno-dsidphy.c
@@ -282,20 +282,20 @@ struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1ghz[] = {
static const
struct inno_mipi_dphy_timing inno_mipi_dphy_timing_table_max_1_5ghz[] = {
- { 110, 0x02, 0x7f, 0x16, 0x02, 0x02},
- { 150, 0x02, 0x7f, 0x16, 0x03, 0x02},
- { 200, 0x02, 0x7f, 0x17, 0x04, 0x02},
- { 250, 0x02, 0x7f, 0x17, 0x05, 0x04},
- { 300, 0x02, 0x7f, 0x18, 0x06, 0x04},
- { 400, 0x03, 0x7e, 0x19, 0x07, 0x04},
- { 500, 0x03, 0x7c, 0x1b, 0x07, 0x08},
- { 600, 0x03, 0x70, 0x1d, 0x08, 0x10},
- { 700, 0x05, 0x40, 0x1e, 0x08, 0x30},
- { 800, 0x05, 0x02, 0x1f, 0x09, 0x30},
- {1000, 0x05, 0x08, 0x20, 0x09, 0x30},
- {1200, 0x06, 0x03, 0x32, 0x14, 0x0f},
- {1400, 0x09, 0x03, 0x32, 0x14, 0x0f},
- {1500, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
+ { 110000000, 0x02, 0x7f, 0x16, 0x02, 0x02},
+ { 150000000, 0x02, 0x7f, 0x16, 0x03, 0x02},
+ { 200000000, 0x02, 0x7f, 0x17, 0x04, 0x02},
+ { 250000000, 0x02, 0x7f, 0x17, 0x05, 0x04},
+ { 300000000, 0x02, 0x7f, 0x18, 0x06, 0x04},
+ { 400000000, 0x03, 0x7e, 0x19, 0x07, 0x04},
+ { 500000000, 0x03, 0x7c, 0x1b, 0x07, 0x08},
+ { 600000000, 0x03, 0x70, 0x1d, 0x08, 0x10},
+ { 700000000, 0x05, 0x40, 0x1e, 0x08, 0x30},
+ { 800000000, 0x05, 0x02, 0x1f, 0x09, 0x30},
+ {1000000000, 0x05, 0x08, 0x20, 0x09, 0x30},
+ {1200000000, 0x06, 0x03, 0x32, 0x14, 0x0f},
+ {1400000000, 0x09, 0x03, 0x32, 0x14, 0x0f},
+ {1500000000, 0x0d, 0x42, 0x36, 0x0e, 0x0f},
};
static const
--
2.47.3
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply related [flat|nested] 8+ messages in thread
end of thread, other threads:[~2026-11-21 8:06 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-21 7:58 [PATCH] drm/phy: rockchip: fix RK3506 DSI low-power command handling ZhuXiangyu
2026-11-21 7:58 ` ZhuXiangyu
2026-11-21 7:58 ` ZhuXiangyu
2026-11-21 8:03 ` sashiko-bot
2026-11-21 8:03 ` sashiko-bot
-- strict thread matches above, loose matches on Subject: below --
2026-11-21 8:05 ZhuXiangyu
2026-11-21 8:05 ` ZhuXiangyu
2026-11-21 8:05 ` ZhuXiangyu
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.