[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ae61b485-d3af-4226-b2f8-e89ef5b4ed71@kernel.org>
Date: Mon, 28 Oct 2024 08:05:47 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Imran Shaik <quic_imrashai@...cinc.com>
Cc: 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>, Ajit Pandey <quic_ajipan@...cinc.com>,
Taniya Das <quic_tdas@...cinc.com>, Jagadeesh Kona <quic_jkona@...cinc.com>,
Satya Priya Kakitapalli <quic_skakitap@...cinc.com>,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: clock: qcom: Add GPU clocks for
QCS8300
On 28/10/2024 06:15, Imran Shaik wrote:
>
>
> On 10/26/2024 5:50 PM, Krzysztof Kozlowski wrote:
>> On Thu, Oct 24, 2024 at 07:01:14PM +0530, Imran Shaik wrote:
>>> The QCS8300 GPU clock controller is mostly identical to SA8775P, but
>>> QCS8300 has few additional clocks and minor differences. Hence, reuse
>>> SA8775P gpucc bindings and add additional clocks required for QCS8300.
>>
>> IIUC, these clocks are not valid for SA8775p. How do we deal with such
>> cases for other Qualcomm SoCs?
>>
>
> These newly added clocks are not applicable to SA8755P. In the
> gpucc-sa8775p driver, these clocks are marked to NULL for the SA8755P,
> ensuring they are not registered to the CCF.
I meant bindings. And existing practice.
Best regards,
Krzysztof
Powered by blists - more mailing lists