[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <89225569-1cd3-ae0e-94ed-bbb2b3dd8e9c@codeaurora.org>
Date: Wed, 16 Oct 2019 13:22:55 +0530
From: Taniya Das <tdas@...eaurora.org>
To: Vinod Koul <vkoul@...nel.org>,
Rajendra Nayak <rnayak@...eaurora.org>
Cc: agross@...nel.org, robh+dt@...nel.org, bjorn.andersson@...aro.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: sc7180: Add minimal dts/dtsi files for
SC7180 soc
Hi Vinod,
On 10/16/2019 10:55 AM, Vinod Koul wrote:
> On 15-10-19, 16:03, Rajendra Nayak wrote:
>
>> + timer {
>> + compatible = "arm,armv8-timer";
>> + interrupts = <GIC_PPI 1 IRQ_TYPE_LEVEL_LOW>,
>> + <GIC_PPI 2 IRQ_TYPE_LEVEL_LOW>,
>> + <GIC_PPI 3 IRQ_TYPE_LEVEL_LOW>,
>> + <GIC_PPI 0 IRQ_TYPE_LEVEL_LOW>;
>> + };
>> +
>> + clocks {
>
> Can we have these sorted alphabetically please
>
>> + xo_board: xo-board {
>> + compatible = "fixed-clock";
>> + clock-frequency = <38400000>;
>> + clock-output-names = "xo_board";
>> + #clock-cells = <0>;
>> + };
>> +
>> + sleep_clk: sleep-clk {
>> + compatible = "fixed-clock";
>> + clock-frequency = <32764>;
>> + clock-output-names = "sleep_clk";
>> + #clock-cells = <0>;
>> + };
>> +
>> + bi_tcxo: bi_tcxo {
>
> why is this a clock defined here? Isnt this gcc clock?
>
This is a RPMH-controlled clock and not from GCC. It is the parent clock
for GCC RCGs/PLLs.
Once the RPMH clock support is added these would be removed.
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation.
--
Powered by blists - more mailing lists