[PATCH v6 2/9] dt-bindings: display: add verisilicon,dc

Drew Fustini fustini at kernel.org
Wed Jan 28 12:34:41 PST 2026


On Fri, Jan 23, 2026 at 05:28:23PM +0800, Icenowy Zheng wrote:
> From: Icenowy Zheng <uwu at icenowy.me>
> 
> Verisilicon has a series of display controllers prefixed with DC and
> with self-identification facility like their GC series GPUs.
> 
> Add a device tree binding for it.
> 
> Depends on the specific DC model, it can have either one or two display
> outputs, and each display output could be set to DPI signal or "DP"
> signal (which seems to be some plain parallel bus to HDMI controllers).
> 
> Signed-off-by: Icenowy Zheng <uwu at icenowy.me>
> Signed-off-by: Icenowy Zheng <zhengxingda at iscas.ac.cn>
> Reviewed-by: Rob Herring (Arm) <robh at kernel.org>
> ---
> Changes in v6:
> - Added Rob's R-b.
> 
> Changes in v5:
> - Dropped the requirement of port at 0.
> - Dropped the if clause for TH1520, which seems to be not needed because
>   of implicit DT binding rules.
> 
> Changes in v4:
> - Added a comment for "verisilicon,dc" that says the ID/revision is
>   discoverable via registers.
> - Removed clock minItems constraint w/o specific compatible strings.
> 
> Changes in v3:
> - Added SoC-specific compatible string, and arm the binding with clock /
>   port checking for the specific SoC (with a 2-output DC).
> 
> Changes in v2:
> - Fixed misspelt "versilicon" in title.
> - Moved minItems in clock properties to be earlier than items.
> - Re-aligned multi-line clocks and resets in example.
> 
>  .../bindings/display/verisilicon,dc.yaml      | 122 ++++++++++++++++++
>  1 file changed, 122 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/display/verisilicon,dc.yaml

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

Please see my reply to patch 1 for the rest of my message.

Thanks,
Drew



More information about the linux-riscv mailing list