[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165097689885.514433.2090850997592209113.b4-ty@cerno.tech>
Date: Tue, 26 Apr 2022 14:41:31 +0200
From: Maxime Ripard <maxime@...no.tech>
To: Chen-Yu Tsai <wens@...e.org>, Maxime Ripard <mripard@...nel.org>,
Samuel Holland <samuel@...lland.org>,
Jernej Skrabec <jernej.skrabec@...il.com>
Cc: Maxime Ripard <maxime@...no.tech>, David Airlie <airlied@...ux.ie>,
linux-kernel@...r.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
linux-sunxi@...ts.linux.dev, dri-devel@...ts.freedesktop.org,
devicetree@...r.kernel.org, Daniel Vetter <daniel@...ll.ch>
Subject: Re: (subset) [PATCH v3 01/14] dt-bindings: display: Separate clock item lists by compatible
On Sun, 24 Apr 2022 11:26:19 -0500, Samuel Holland wrote:
> So far, the binding and driver have relied on the fact that the H6
> clocks are both a prefix and a subset of the R40 clocks. This allows
> them to share the clocks/clock-names items and the clock-output-names
> order between the hardware variants.
>
> However, the D1 hardware has TCON TV0 and DSI, but no TCON TV1. This
> cannot be supported by the existing scheme because it puts a gap in the
> middle of the item lists. To prepare for adding D1 support, use separate
> lists for variants with different combinations of clocks.
>
> [...]
Applied to drm/drm-misc (drm-misc-next).
Thanks!
Maxime
Powered by blists - more mailing lists