[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E796D737-E343-4EDB-BB34-CE6E0295CF3E@linaro.org>
Date: Wed, 25 Nov 2020 09:19:24 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
To: Stephen Boyd <sboyd@...nel.org>, mturquette@...libre.com,
robh+dt@...nel.org
CC: bjorn.andersson@...aro.org, vkoul@...nel.org,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: clock: Add SDX55 GCC clock bindings
On 25 November 2020 7:44:10 AM IST, Stephen Boyd <sboyd@...nel.org> wrote:
>Quoting Manivannan Sadhasivam (2020-11-18 23:27:11)
>> diff --git
>a/Documentation/devicetree/bindings/clock/qcom,gcc-sdx55.yaml
>b/Documentation/devicetree/bindings/clock/qcom,gcc-sdx55.yaml
>> new file mode 100644
>> index 000000000000..9d8981817ae3
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/clock/qcom,gcc-sdx55.yaml
>> @@ -0,0 +1,73 @@
>[...]
>> +
>> +properties:
>> + compatible:
>> + const: qcom,gcc-sdx55
>> +
>> + clocks:
>> + items:
>[...]
>> + - description: PLL test clock source
>> +
>> + clock-names:
>> + items:
>[...]
>> + - const: core_bi_pll_test_se
>
>Is it optional? As far as I know this clk has never been implemented
>because it's a hardware validation thing and not used otherwise.
It is implemented in drivers but not used as you said. But since it is the parent clk of PLLs I'm not sure we can make it optional.
Thanks,
Mani
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists