From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/6] dts: ipq4019: Add support for IPQ4019 DK01 board
Date: Thu, 18 Feb 2016 18:43:50 -0800 [thread overview]
Message-ID: <20160219024350.GQ4847@codeaurora.org> (raw)
In-Reply-To: <59152C1B-683F-417D-9C23-C6E3F53D7096@codeaurora.org>
On 02/16, Matthew McClintock wrote:
> On Feb 8, 2016, at 4:43 PM, Stephen Boyd <sboyd@codeaurora.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?
>
The sleep clk is typically a pin on the SoC package. Look at your
schematic. Same goes for the XO.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-02-19 2:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1447975173-29485-1-git-send-email-mmcclint@qca.qualcomm.com>
2015-11-19 23:19 ` [PATCH v3 4/6] qcom: ipq4019: Add basic board/dts support for IPQ4019 SoC Matthew McClintock
2016-02-08 22:45 ` Stephen Boyd
2015-11-19 23:19 ` [PATCH v3 5/6] dts: ipq4019: Add support for IPQ4019 DK01 board Matthew McClintock
2016-02-08 22:43 ` Stephen Boyd
2016-02-16 20:43 ` Matthew McClintock
2016-02-19 2:43 ` Stephen Boyd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160219024350.GQ4847@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).