Re: [PATCH v4 0/2] gpu/drm: tegra: add DSI support for Tegra20/Tegra30

From: Svyatoslav Ryhel

Date: Mon Apr 27 2026 - 02:24:00 EST


пн, 9 бер. 2026 р. о 09:53 Svyatoslav Ryhel <clamor95@xxxxxxxxx> пише:
>
> Tegra20/Tegra30 DSI is quite similar to Tegra114+ apart MIPI calibration
> logic and clocks. With a few minor tweaks, existing tegra DSI driver
> should work on Tegra20/Tegra30 devices just fine. Tested on
> Motorola Atrix 4G (T20) and ASUS VivoTab RT TF600T (T30).
>
> This patchset depends on Tegra20/Tegra30 CSI bringup since both share
> MIPI calibration logic. Ideally these patches should be picked after
> CSI bringup but they will not break anything even if picked before
> CSI patches.
>
> ---
> Changes in v2:
> - removed all MIPI calibration, it is handled within CSI bringup
> - added per-soc structures into of_match
> - added fix for hang caused by register access with uninited hw
>
> Changes in v3:
> - switched from version DSI to boolean flags
> - added comment regarding Tegra30 clock configuration
> - commits were picked:
> "clk: tegra20: reparent dsi clock to pll_d_out0"
> "ARM: tegra: adjust DSI nodes for Tegra20/Tegra30"
> - commit adapted to recent DSI changes:
> "gpu/drm: tegra: dsi: move prepare function at the top of encoder
> enable" > "gpu/drm: tegra: dsi: re-add clear enable register if
> DSI was powered by bootloader"
>
> Changes in v4:
> - switched to device_get_match_data and added check
> - added comment regarding Tegra124+ quirk
> - adjusted commit titles and message formatting
> ---
>
> Svyatoslav Ryhel (2):
> drm/tegra: dsi: add support for Tegra20/Tegra30
> drm/tegra: dsi: re-add clear enable register if DSI was powered by
> bootloader
>
> drivers/gpu/drm/tegra/drm.c | 2 +
> drivers/gpu/drm/tegra/dsi.c | 126 +++++++++++++++++++++++++++---------
> drivers/gpu/drm/tegra/dsi.h | 10 +++
> 3 files changed, 107 insertions(+), 31 deletions(-)
>
> --
> 2.51.0
>

Hello Thierry!

May you please pick these patch if you are fine with them when you
have some spare time? It is ok if they end up in the next.

Best regards,
Svyatoslav R.