lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160219024350.GQ4847@codeaurora.org>
Date:	Thu, 18 Feb 2016 18:43:50 -0800
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Matthew McClintock <mmcclint@...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 02/16, Matthew McClintock wrote:
> 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?
> 

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ