From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932531AbdAGDBe (ORCPT ); Fri, 6 Jan 2017 22:01:34 -0500 Received: from mail-oi0-f53.google.com ([209.85.218.53]:36578 "EHLO mail-oi0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752417AbdAGDBY (ORCPT ); Fri, 6 Jan 2017 22:01:24 -0500 Date: Fri, 6 Jan 2017 21:01:20 -0600 From: Andy Gross To: John Stultz Cc: Bjorn Andersson , David Brown , Rob Herring , Mark Rutland , "linux-arm-msm@vger.kernel.org" , linux-soc@vger.kernel.org, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-arm-kernel@lists.infradead.org" , lkml Subject: Re: [PATCH 1/5] ARM: dts: qcom: apq8064: Add missing scm clock Message-ID: <20170107030120.GC5710@hector.attlocal.net> References: <20161221114939.19973-1-bjorn.andersson@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 06, 2017 at 05:10:44PM -0800, John Stultz wrote: > On Wed, Dec 21, 2016 at 3:49 AM, Bjorn Andersson > wrote: > > As per the device tree binding the apq8064 scm node requires the core > > clock to be specified, so add this. > > > > Cc: John Stultz > > Signed-off-by: Bjorn Andersson > > --- > > arch/arm/boot/dts/qcom-apq8064.dtsi | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/arch/arm/boot/dts/qcom-apq8064.dtsi b/arch/arm/boot/dts/qcom-apq8064.dtsi > > index 268bd470c865..78bf155a52f3 100644 > > --- a/arch/arm/boot/dts/qcom-apq8064.dtsi > > +++ b/arch/arm/boot/dts/qcom-apq8064.dtsi > > @@ -303,6 +303,9 @@ > > firmware { > > scm { > > compatible = "qcom,scm-apq8064"; > > + > > + clocks = <&gcc CE3_CORE_CLK>; > > + clock-names = "core"; > > > Tested-by: John Stultz > > I know Bjorn has a new version of this patch that uses the > RPM_DAYTONA_FABRIC_CLK value, but that one results in problems with > usb gadget functionality on my Nexus7. This one seems to work ok > though. Odd. Is the usb gadget using the daytona but not getting a reference? I wonder if this is related to not having the bus driver running the bus clk enablement and frequencies. Andy