[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250718-finicky-orangutan-of-piety-fcfd6a@kuoka>
Date: Fri, 18 Jul 2025 09:32:10 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Jessica Zhang <jessica.zhang@....qualcomm.com>
Cc: Abhinav Kumar <quic_abhinavk@...cinc.com>,
Dmitry Baryshkov <lumag@...nel.org>, Sean Paul <sean@...rly.run>,
Marijn Suijten <marijn.suijten@...ainline.org>, David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>, Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Kuogee Hsieh <quic_khsieh@...cinc.com>,
Abel Vesa <abel.vesa@...aro.org>, Bjorn Andersson <andersson@...nel.org>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>,
Mahadevan <quic_mahap@...cinc.com>, Krishna Manikandan <quic_mkrishn@...cinc.com>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Clark <robin.clark@....qualcomm.com>,
Abhinav Kumar <abhinav.kumar@...ux.dev>, Danila Tikhonov <danila@...xyga.com>,
cros-qcom-dts-watchers@...omium.org, Abhinav Kumar <abhinav.kumar@....qualcomm.com>,
linux-arm-msm@...r.kernel.org, dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
Yongxing Mou <quic_yongmou@...cinc.com>
Subject: Re: [PATCH v3 3/5] dt-bindings: display/msm: drop
assigned-clock-parents for dp controller
On Thu, Jul 17, 2025 at 04:28:45PM -0700, Jessica Zhang wrote:
> From: Abhinav Kumar <quic_abhinavk@...cinc.com>
>
> Current documentation of assigned-clock-parents for dp controller does not
> describe its functionality correctly making it harder to extend it for
It does...
> adding multiple streams.
Just extend the list?
>
> Instead of fixing up the documentation, drop the assigned-clock-parents
> and assigned-clocks along with the usages in the chipset specific MDSS
> yaml files.
It should not be added here at all, but since Qualcomm added it, it is
an ABI, so explain why this cannot be fixed or impact of this ABI
change. It is fine to drop it in general, but reasoning in first
paragraph feels incomplete. I don't see any problem in how it describes
the functionality (except that it should not be there...)
Best regards,
Krzysztof
Powered by blists - more mailing lists