[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6043373.ZgY5Yo1tNM@flatron>
Date: Sun, 18 Aug 2013 00:22:43 +0200
From: Tomasz Figa <tomasz.figa@...il.com>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: linux-arm-kernel@...ts.infradead.org,
Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@....com>,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
Jonas Bonn <jonas@...thpole.se>,
Michal Simek <monstr@...str.eu>,
Rob Herring <rob.herring@...xeda.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Grant Likely <grant.likely@...aro.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Subject: Re: [RFC PATCH v2 3/4] powerpc: refactor of_get_cpu_node to support other architectures
On Sunday 18 of August 2013 08:09:36 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 ...
[Copying Lorenzo...]
I'm not the author of the change. I was just passing by, while the
question showed up in my mind. ;)
> Traditionally, UP setups just used "0" as the "reg" property on other
> architectures, why do differently ?
Right, especially since the ARM DT topology parsing code still considers a
device tree without reg property in cpu node invalid.
Best regards,
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists