[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a893eb89-1956-4ba2-84cc-e9b64b87524a@kernel.org>
Date: Wed, 29 May 2024 09:39:28 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Bjorn Andersson <andersson@...nel.org>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd
<sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Taniya Das <quic_tdas@...cinc.com>,
Robert Marko <robimarko@...il.com>, Konrad Dybcio <konrad.dybcio@...aro.org>
Cc: linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 05/10] dt-bindings: clock: qcom,gcc-nopd.yaml: force node
name
On 28/05/2024 22:43, Dmitry Baryshkov wrote:
> Force GCC device nodes to have the name 'clock-controller'. Several
> platforms used 'gcc' here.
Well, only ones coming from Qualcomm being downstream-based:
Author: Varadarajan Narayanan <quic_varada@...cinc.com>
Date: Thu Jun 29 11:48:33 2017 +0530
Author: Sricharan Ramabadhran <quic_srichara@...cinc.com>
Date: Sun Jan 19 18:43:20 2020 +0530
(and there was also older with node name qcom,gcc, so clearly copy-paste
from downstream sources)
yet still we do not enforce names in individual schemas. You add it now
and next month turns out there is a power-reset-clock-controller which
could use gcc.yaml, but cannot because of node name enforcement.
Best regards,
Krzysztof
Powered by blists - more mailing lists