Currently, the Verisilicon DC-series display controller driver supports
only the DC8200 variant in the T-HEAD TH1520 SoC.  Hence restrict the
dependency on RISCV to ARCH_THEAD, to prevent asking the user about this
driver when configuring a kernel without T-HEAD platform support.

The dependency can be relaxed later, when adding support for appropriate
SoCs from other vendors.

Fixes: dbf21777caa8b8c8 ("drm: verisilicon: add a driver for Verisilicon display controllers")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
 drivers/gpu/drm/verisilicon/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/verisilicon/Kconfig b/drivers/gpu/drm/verisilicon/Kconfig
index 7cce86ec8603c596..f2edde9e0037ebcd 100644
--- a/drivers/gpu/drm/verisilicon/Kconfig
+++ b/drivers/gpu/drm/verisilicon/Kconfig
@@ -2,7 +2,7 @@
 config DRM_VERISILICON_DC
 	tristate "DRM Support for Verisilicon DC-series display controllers"
 	depends on DRM && COMMON_CLK
-	depends on RISCV || COMPILE_TEST
+	depends on ARCH_THEAD || COMPILE_TEST
 	select DRM_BRIDGE_CONNECTOR
 	select DRM_CLIENT_SELECTION
 	select DRM_DISPLAY_HELPER
-- 
2.43.0

在 2026-02-26四的 12:00 +0100，Geert Uytterhoeven写道：
> Currently, the Verisilicon DC-series display controller driver
> supports
> only the DC8200 variant in the T-HEAD TH1520 SoC.  Hence restrict the
> dependency on RISCV to ARCH_THEAD, to prevent asking the user about
> this
> driver when configuring a kernel without T-HEAD platform support.
> 
> The dependency can be relaxed later, when adding support for
> appropriate
> SoCs from other vendors.

Michal Wilczynski has verified that this driver will work on StarFive
JH7110 with some extra glue drivers (but without modification to this
driver itself). [1]

Although this can be considered as future work and changing to
ARCH_THEAD seems okay now.

(BTW the hardware identification values is taken from the vendor driver
and it should support different variants of DC8200)

Thanks
Icenowy

[1]
https://lists.freedesktop.org/archives/dri-devel/2025-November/535442.html

> 
> Fixes: dbf21777caa8b8c8 ("drm: verisilicon: add a driver for
> Verisilicon display controllers")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
>  drivers/gpu/drm/verisilicon/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/verisilicon/Kconfig
> b/drivers/gpu/drm/verisilicon/Kconfig
> index 7cce86ec8603c596..f2edde9e0037ebcd 100644
> --- a/drivers/gpu/drm/verisilicon/Kconfig
> +++ b/drivers/gpu/drm/verisilicon/Kconfig
> @@ -2,7 +2,7 @@
>  config DRM_VERISILICON_DC
>  	tristate "DRM Support for Verisilicon DC-series display
> controllers"
>  	depends on DRM && COMMON_CLK
> -	depends on RISCV || COMPILE_TEST
> +	depends on ARCH_THEAD || COMPILE_TEST
>  	select DRM_BRIDGE_CONNECTOR
>  	select DRM_CLIENT_SELECTION
>  	select DRM_DISPLAY_HELPER

On 2/26/26 16:36, Icenowy Zheng wrote:
> 在 2026-02-26四的 12:00 +0100，Geert Uytterhoeven写道：
>> Currently, the Verisilicon DC-series display controller driver
>> supports
>> only the DC8200 variant in the T-HEAD TH1520 SoC.  Hence restrict the
>> dependency on RISCV to ARCH_THEAD, to prevent asking the user about
>> this
>> driver when configuring a kernel without T-HEAD platform support.
>>
>> The dependency can be relaxed later, when adding support for
>> appropriate
>> SoCs from other vendors.
> 
> Michal Wilczynski has verified that this driver will work on StarFive
> JH7110 with some extra glue drivers (but without modification to this
> driver itself). [1]

Yeah I managed to test successfully (not all resolutions worked for me
but this does seem like HDMI driver issue). Additionally Graham Markall
managed to check on his VF2 independently [1]. Hopefully will find some
time to send an updated v2.

[1] - https://big-grey.co.uk/2026/01/26/testing-starfive-jh7110-display-controller-patches/

Best regards,
-- 
Michal Wilczynski <m.wilczynski@samsung.com>

> 
> Although this can be considered as future work and changing to
> ARCH_THEAD seems okay now.
> 
> (BTW the hardware identification values is taken from the vendor driver
> and it should support different variants of DC8200)
> 
> Thanks
> Icenowy
> 
> [1]
> https://protect2.fireeye.com/v1/url?k=9deb3bf5-c27002f9-9deab0ba-000babff3563-0751fbe2749df7e2&q=1&e=1bdc71ee-fc93-4f72-a715-c25dc3497820&u=https%3A%2F%2Flists.freedesktop.org%2Farchives%2Fdri-devel%2F2025-November%2F535442.html
> 
>>
>> Fixes: dbf21777caa8b8c8 ("drm: verisilicon: add a driver for
>> Verisilicon display controllers")
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> ---
>>  drivers/gpu/drm/verisilicon/Kconfig | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/verisilicon/Kconfig
>> b/drivers/gpu/drm/verisilicon/Kconfig
>> index 7cce86ec8603c596..f2edde9e0037ebcd 100644
>> --- a/drivers/gpu/drm/verisilicon/Kconfig
>> +++ b/drivers/gpu/drm/verisilicon/Kconfig
>> @@ -2,7 +2,7 @@
>>  config DRM_VERISILICON_DC
>>  	tristate "DRM Support for Verisilicon DC-series display
>> controllers"
>>  	depends on DRM && COMMON_CLK
>> -	depends on RISCV || COMPILE_TEST
>> +	depends on ARCH_THEAD || COMPILE_TEST
>>  	select DRM_BRIDGE_CONNECTOR
>>  	select DRM_CLIENT_SELECTION
>>  	select DRM_DISPLAY_HELPER
> 
>