[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <59152C1B-683F-417D-9C23-C6E3F53D7096@codeaurora.org>
Date: Tue, 16 Feb 2016 14:43:18 -0600
From: Matthew McClintock <mmcclint@...eaurora.org>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: Matthew McClintock <mmcclint@....qualcomm.com>,
Andy Gross <agross@...eaurora.org>,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
qca-upstream.external@....qualcomm.com,
Senthilkumar N L <snlakshm@...eaurora.org>,
Varadarajan Narayanan <varada@...eaurora.org>
Subject: Re: [PATCH v3 5/6] dts: ipq4019: Add support for IPQ4019 DK01 board
On Feb 8, 2016, at 4:43 PM, Stephen Boyd <sboyd@...eaurora.org> wrote:
>
> On 11/19, Matthew McClintock wrote:
>> +
>> +/ {
>> + model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK01.1";
>> + compatible = "qcom,ipq4019";
>> +
>> + clocks {
>> + xo: xo {
>> + compatible = "fixed-clock";
>> + clock-frequency = <48000000>;
>> + #clock-cells = <0>;
>> + };
>> + };
>
> Is there a reason the xo is here and the sleep clk is in the SoC
> dtsi file? Both are board clocks so I would think they would be
> added in the same place.
I’m a little bit confused and I wanted to confirm. I can see the xo clock is on the board itself. However, the sleep_clk is not, can you clarify why they would both be in the same place?
-M
Powered by blists - more mailing lists