[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d4ffa9f0-797e-7a32-147e-64aa46d7e197@linaro.org>
Date: Fri, 17 Feb 2023 21:13:59 +0000
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
linux-arm-msm@...r.kernel.org, andersson@...nel.org,
agross@...nel.org
Cc: marijn.suijten@...ainline.org, Rob Clark <robdclark@...il.com>,
Abhinav Kumar <quic_abhinavk@...cinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Sean Paul <sean@...rly.run>, David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Krishna Manikandan <quic_mkrishn@...cinc.com>,
dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: display/msm: dsi-controller-main: Fix
deprecated QCM2290 compatible
On 17/02/2023 12:24, Krzysztof Kozlowski wrote:
> First, it would be nice to know what was the intention of Bryan's commit?
Sorry I've been grazing this thread but, not responding.
- qcom,dsi-ctrl-6g-qcm2290
is non-compliant with qcom,socid-dsi-ctrl which is our desired naming
convention, so that's what the deprecation is about i.e. moving this
compat to "qcom,qcm2290-dsi-ctrl"
Actually I have the question why we are deciding to go with "sm6115"
instead of "qcm2290" ?
The stamp on the package you receive from Thundercomm says "qcm2290" not
"sm6115"
?
---
bod
Powered by blists - more mailing lists