[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260205-psychedelic-brave-toad-db4936@quoll>
Date: Thu, 5 Feb 2026 14:18:31 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Joey Lu <a0987203069@...il.com>
Cc: airlied@...il.com, simona@...ll.ch, maarten.lankhorst@...ux.intel.com,
mripard@...nel.org, tzimmermann@...e.de, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, ychuang3@...oton.com, schung@...oton.com, yclu4@...oton.com,
linux-arm-kernel@...ts.infradead.org, dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: display: nuvoton: add MA35D1 DCU
binding
On Thu, Jan 29, 2026 at 12:05:30PM +0800, Joey Lu wrote:
> +
> + clocks:
> + items:
> + - description: DCU Gate clock for register access
> + - description: DCU Pixel clock for display timing
> +
> + clock-names:
> + items:
> + - const: dcu_gate
That's bus or apb
> + - const: dcup_div
That's pixel
Use descriptive names of functions here. Not your clock controller. It
is completely irrelevant whether you provide here gate or div or mux or
whatever else. If by any chance in new design you put here mux, not div,
then completely new binding?
Best regards,
Krzysztof
Powered by blists - more mailing lists