Re: [PATCH v6 1/9] dt-bindings: vendor-prefixes: add verisilicon

[Drew Fustini <fustini@kernel.org>]

On Fri, Jan 23, 2026 at 05:28:22PM +0800, Icenowy Zheng wrote:
> From: Icenowy Zheng <uwu@icenowy.me>
> 
> VeriSilicon is a Silicon IP vendor, which is the current owner of
> Vivante series video-related IPs and Hantro series video codec IPs.
> 
> Add a vendor prefix for this company.
> 
> Signed-off-by: Icenowy Zheng <uwu@icenowy.me>
> Signed-off-by: Icenowy Zheng <zhengxingda@iscas.ac.cn>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> No changes since v4.
> 
> Changes in v3:
> - Add Rob's ACK.
> 
> No changes in v2.
> 
>  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index c7591b2aec2a7..18f931f369198 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -1745,6 +1745,8 @@ patternProperties:
>      description: Variscite Ltd.
>    "^vdl,.*":
>      description: Van der Laan b.v.
> +  "^verisilicon,.*":
> +    description: VeriSilicon Microelectronics (Shanghai) Co., Ltd.
>    "^vertexcom,.*":
>      description: Vertexcom Technologies, Inc.
>    "^via,.*":
> -- 
> 2.52.0
> 

I've applied the bindings patches (1, 2, 4) to thead-dt-for-next as well
so that 'make W=1 dtbs_check' won't break for the next release of
linux-next.

https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git/log/?h=thead-dt-for-next

I wouldn't normally pick bindings patches but it is a short timeline if
we want to get some testing done in linux-next before sending v6.20 pull
requests. I have created an immutable branch thead-dt-v6.20-dpu-hdmi in
case that helps.

https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git/log/?h=thead-dt-v6.20-dpu-hdmi

I can drop the yaml patches from thead-dt-for-next if people think that
was the wrong thing to do. If we think that the driver changes won't
actually be ready for the merge window, then I can drop all these
patches from thead-dt-for-next.

Thanks,
Drew