From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936356AbcHJT5w (ORCPT ); Wed, 10 Aug 2016 15:57:52 -0400 Received: from foss.arm.com ([217.140.101.70]:49353 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935703AbcHJSgT (ORCPT ); Wed, 10 Aug 2016 14:36:19 -0400 Date: Wed, 10 Aug 2016 17:06:34 +0100 From: Juri Lelli To: Sudeep Holla Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, peterz@infradead.org, vincent.guittot@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com, linux@arm.linux.org.uk, lorenzo.pieralisi@arm.com, catalin.marinas@arm.com, will.deacon@arm.com, morten.rasmussen@arm.com, dietmar.eggemann@arm.com, broonie@kernel.org, Liviu Dudau , Pawel Moll , Ian Campbell , Kumar Gala Subject: Re: [PATCH v6 3/8] arm, dts: add TC2 cpu capacity-dmips-mhz information Message-ID: <20160810160634.GL3540@e106622-lin> References: <1468932048-31635-1-git-send-email-juri.lelli@arm.com> <1468932048-31635-4-git-send-email-juri.lelli@arm.com> <7ac935dc-9f8b-8af0-e67b-ef1c469d76f1@arm.com> <20160810154324.GJ3540@e106622-lin> <08d9e2ff-3c66-5129-1c82-df314e2204db@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <08d9e2ff-3c66-5129-1c82-df314e2204db@arm.com> 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 10/08/16 16:52, Sudeep Holla wrote: > > > On 10/08/16 16:43, Juri Lelli wrote: > >Hi, > > > >On 10/08/16 16:33, Sudeep Holla wrote: > >>Hi Juri, > >> > >>On 19/07/16 13:40, Juri Lelli wrote: > >>>Add TC2 cpu capacity binding information. > >>> > >> > >>If you repost it, > >> > >>s/binding// > >> > > > >Yes, I think I'll need to repost, squashing the arm64 fix in the > >appropriate patch. Thanks. > > > >>>Cc: Liviu Dudau > >>>Cc: Sudeep Holla > >> > >>Acked-by: Sudeep Holla > > > >Thanks! > > > >>(assuming you take it via some other tree, let us know if it's > >> OK to merge the DTS separately and you want us to pick them) > >> > > > >As per off-line discussion with Russell, binding doc and arm bits should > >go via his patch system. While arm64 bits could go separately via aarch64. > > > >Does this make sense? > > Yes, we can pick up the juno and tc2 dts changes and send it via > arm-soc. If this works better for you it is fine by me! I'll only use Russell's system for docs and arm parsing/sysfs implementation then. Thanks, - Juri