devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Nicolas Pitre <nicolas.pitre@linaro.org>,
	Dave Martin <dave.martin@linaro.org>,
	Andrew Lunn <andrew@lunn.ch>, Tony Lindgren <tony@atomide.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Jon Medhurst <tixy@linaro.org>, Sekhar Nori <nsekhar@ti.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
	Lennert Buytenhek <kernel@wantstofly.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Russell King <linux@arm.linux.org.uk>,
	Magnus Damm <magnus.damm@gmail.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	David Brown <davidb@codeaurora.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Dinh Nguyen <dinguyen@altera.com>, Arnd Bergmann <arnd@arndb.de>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	Simon Horman <horms@verge.net.au>,
	Bar
Subject: Re: [RFC PATCH 2/2] ARM: DT: kernel: DT cpu node bindings update
Date: Wed, 17 Apr 2013 18:24:09 +0200	[thread overview]
Message-ID: <1366215849.24994.70.camel@pasglop> (raw)
In-Reply-To: <516EBC66.20508@wwwdotorg.org>

On Wed, 2013-04-17 at 09:14 -0600, Stephen Warren wrote:
> On 04/17/2013 03:14 AM, Mark Rutland wrote:
> > Hi Stephen,
> > 
> >>> +	- enable-method
> >>> +		Usage: required on ARM 64-bit systems, optional on ARM 32-bit
> >>> +		       systems
> >>> +		Value type: <string>
> >>> +		Definition: On ARM 64-bit systems must be "spin-table" [1].
> >>
> >> Can that be an integer instead? with dtc+cpp support, that shouldn't
> >> hurt the eyes too much any more.
> > 
> > The "enable-method" property is described as a stringlist by ePAPR, and is
> > currently in use on arm64 as such. It *must* remain a string(list) for arm64.
> > 
> > Having it as an integer for arm is only going to cause us additional work,
> > makes it impossible to share a common dt between 64bit and 32bit, and goes
> > against the standard. I think it should be a stringlist for arm.
> 
> OK, that's a great reason for this case.
> 
> I hope we don't introduce any more standards that use strings, but that
> may just be my personal preference...

I happen to have the exact opposite opinion :-)

Cheers,
Ben.

  parent reply	other threads:[~2013-04-17 16:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 16:13 [RFC PATCH 0/2] ARM: DT cpu bindings updates Lorenzo Pieralisi
2013-04-15 16:13 ` [RFC PATCH 1/2] ARM: DT: kernel: move temporary cpu map stack array to static data Lorenzo Pieralisi
     [not found] ` <1366042402-8987-1-git-send-email-lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
2013-04-15 16:13   ` [RFC PATCH 2/2] ARM: DT: kernel: DT cpu node bindings update Lorenzo Pieralisi
     [not found]     ` <1366042402-8987-3-git-send-email-lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
2013-04-15 19:26       ` Stephen Warren
2013-04-16 10:45         ` Lorenzo Pieralisi
     [not found]           ` <20130416104545.GA19837-7AyDDHkRsp3ZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-04-16 15:57             ` Stephen Warren
2013-04-16 16:21               ` Benjamin Herrenschmidt
     [not found]         ` <516C544A.4090107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-04-16 14:30           ` Dave Martin
2013-04-17  9:14         ` Mark Rutland
     [not found]           ` <20130417091457.GB5012-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-04-17 15:14             ` Stephen Warren
2013-04-17 16:02               ` Nicolas Pitre
     [not found]                 ` <alpine.LFD.2.03.1304171146530.17375-hIgblCxmbi8OMTOF05IoTw@public.gmane.org>
2013-04-17 16:23                   ` Stephen Warren
     [not found]                     ` <516ECC8A.2070508-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-04-17 16:36                       ` Nicolas Pitre
     [not found]                         ` <alpine.LFD.2.03.1304171231130.17375-hIgblCxmbi8OMTOF05IoTw@public.gmane.org>
2013-04-17 16:56                           ` Dave Martin
2013-04-17 16:24               ` Benjamin Herrenschmidt [this message]
     [not found]               ` <516EBC66.20508-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-04-18 12:40                 ` Grant Likely
2013-04-16  2:41       ` Simon Horman
2013-04-16 11:00         ` Lorenzo Pieralisi
2013-04-17  9:35     ` Nicolas Ferre
2013-04-17 11:44       ` Lorenzo Pieralisi
2013-04-17  9:48     ` Arnd Bergmann
2013-04-17 11:02       ` Lorenzo Pieralisi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1366215849.24994.70.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Catalin.Marinas@arm.com \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=dave.martin@linaro.org \
    --cc=davidb@codeaurora.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dinguyen@altera.com \
    --cc=grant.likely@secretlab.ca \
    --cc=horms@verge.net.au \
    --cc=kernel@wantstofly.org \
    --cc=kgene.kim@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=nicolas.pitre@linaro.org \
    --cc=nsekhar@ti.com \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.org \
    --cc=tixy@linaro.org \
    --cc=tony@atomide.com \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).