Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756148Ab3H2Juc (ORCPT ); Thu, 29 Aug 2013 05:50:32 -0400 Received: from service87.mimecast.com ([91.220.42.44]:40192 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755530Ab3H2Jua convert rfc822-to-8bit (ORCPT ); Thu, 29 Aug 2013 05:50:30 -0400 Date: Thu, 29 Aug 2013 10:50:23 +0100 From: Lorenzo Pieralisi To: Grant Likely Cc: Mark Rutland , Sudeep KarkadaNagesha , Rob Herring , Benjamin Herrenschmidt , Jonas Bonn , "devicetree@vger.kernel.org" , Michal Simek , "linux-pm@vger.kernel.org" , Tomasz Figa , "rob.herring@calxeda.com" , "linux-kernel@vger.kernel.org" , "Rafael J. Wysocki" , "linuxppc-dev@lists.ozlabs.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [RFC PATCH v2 3/4] powerpc: refactor of_get_cpu_node to support other architectures Message-ID: <20130829095023.GB2878@e102568-lin.cambridge.arm.com> References: <1376586580-5409-1-git-send-email-Sudeep.KarkadaNagesha@arm.com> <1376674791-28244-1-git-send-email-Sudeep.KarkadaNagesha@arm.com> <1376674791-28244-2-git-send-email-Sudeep.KarkadaNagesha@arm.com> <2032060.4bgTKOdEX2@flatron> <1376777376.25016.11.camel@pasglop> <20130819101922.GI3719@e106331-lin.cambridge.arm.com> <5212177C.8000709@gmail.com> <521223FA.5050903@arm.com> <20130822135930.GC23152@e106331-lin.cambridge.arm.com> <20130828194638.AB78E3E0A6F@localhost> MIME-Version: 1.0 In-Reply-To: <20130828194638.AB78E3E0A6F@localhost> User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginalArrivalTime: 29 Aug 2013 09:50:24.0478 (UTC) FILETIME=[2EF25FE0:01CEA49D] X-MC-Unique: 113082910502708401 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3133 Lines: 69 On Wed, Aug 28, 2013 at 08:46:38PM +0100, Grant Likely wrote: > On Thu, 22 Aug 2013 14:59:30 +0100, Mark Rutland wrote: > > On Mon, Aug 19, 2013 at 02:56:10PM +0100, Sudeep KarkadaNagesha wrote: > > > On 19/08/13 14:02, Rob Herring wrote: > > > > On 08/19/2013 05:19 AM, Mark Rutland wrote: > > > >> On Sat, Aug 17, 2013 at 11:09:36PM +0100, Benjamin Herrenschmidt wrote: > > > >>> On Sat, 2013-08-17 at 12:50 +0200, Tomasz Figa wrote: > > > >>>> I wonder how would this handle uniprocessor ARM (pre-v7) cores, for > > > >>>> which > > > >>>> the updated bindings[1] define #address-cells = <0> and so no reg > > > >>>> property. > > > >>>> > > > >>>> [1] - http://thread.gmane.org/gmane.linux.ports.arm.kernel/260795 > > > >>> > > > >>> Why did you do that in the binding ? That sounds like looking to create > > > >>> problems ... > > > >>> > > > >>> Traditionally, UP setups just used "0" as the "reg" property on other > > > >>> architectures, why do differently ? > > > >> > > > >> The decision was taken because we defined our reg property to refer to > > > >> the MPIDR register's Aff{2,1,0} bitfields, and on UP cores before v7 > > > >> there's no MPIDR register at all. Given there can only be a single CPU > > > >> in that case, describing a register that wasn't present didn't seem > > > >> necessary or helpful. > > > > > > > > What exactly reg represents is up to the binding definition, but it > > > > still should be present IMO. I don't see any issue with it being > > > > different for pre-v7. > > > > > > > Yes it's better to have 'reg' with value 0 than not having it. > > > Otherwise this generic of_get_cpu_node implementation would need some > > > _hack_ to handle that case. > > > > I'm not sure that having some code to handle a difference in standard > > between two architectures is a hack. If anything, I'd argue encoding a > > reg of 0 that corresponds to a nonexistent MPIDR value (given that's > > what the reg property is defined to map to on ARM) is more of a hack ;) > > > > I'm not averse to having a reg value of 0 for this case, but given that > > there are existing devicetrees without it, requiring a reg property will > > break compatibility with them. > > Then special cases those device trees, but you changing existing > convention really needs to be avoided. The referenced documentation > change is brand new, so we're not stuck with it. I have no problem with changing the bindings and forcing: #address-cells = <1>; reg = <0>; for UP predating v7, my big worry is related to in-kernel dts that we already patched to follow the #address-cells = <0> rule (and we had to do it since we got asked that question multiple times on the public lists). What do you mean by "special case those device trees" ? I have not planned to patch them again, unless we really consider that a necessary evil. Thanks, Lorenzo -- 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/