Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758024AbaDHX0Y (ORCPT ); Tue, 8 Apr 2014 19:26:24 -0400 Received: from smtp.codeaurora.org ([198.145.11.231]:51725 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756798AbaDHX0V (ORCPT ); Tue, 8 Apr 2014 19:26:21 -0400 Date: Tue, 8 Apr 2014 16:26:20 -0700 From: Stephen Boyd To: Kumar Gala Cc: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Russell King , David Brown , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org Subject: Re: [PATCH v2] ARM: qcom: Add initial APQ8064 SoC and IFC6410 board device trees Message-ID: <20140408232619.GL9985@codeaurora.org> References: <1396972391-11759-1-git-send-email-galak@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1396972391-11759-1-git-send-email-galak@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/08, Kumar Gala wrote: > Add basic APQ8064 SoC include device tree and support for basic booting on > the IFC6410 board. > > Signed-off-by: Kumar Gala > --- > v2: > * created a v2.0 apq8064.dtsi to handle differences in Si rev in future > * changed /include/ to #include > * added PMU node > * dropped interrupts from cpus node, not currently part of binding > > > arch/arm/boot/dts/Makefile | 1 + > arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 12 +++ > arch/arm/boot/dts/qcom-apq8064-v2.0.dtsi | 1 + > arch/arm/boot/dts/qcom-apq8064.dtsi | 154 +++++++++++++++++++++++++++++ > arch/arm/mach-qcom/board.c | 1 + I suspect the arm-soc folks would like us to split the mach-qcom changes from the dts changes. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/