linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] ARM: DT: kernel: DT cpu node bindings update
Date: Thu, 18 Apr 2013 13:40:21 +0100	[thread overview]
Message-ID: <20130418124021.DE4C63E118C@localhost> (raw)
In-Reply-To: <516EBC66.20508@wwwdotorg.org>

On Wed, 17 Apr 2013 09:14:46 -0600, Stephen Warren <swarren@wwwdotorg.org> 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...

We've got lots of bindings using strings like this. I don't really see any problem with it.

g.

  parent reply	other threads:[~2013-04-18 12:40 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
2013-04-15 16:13 ` [RFC PATCH 2/2] ARM: DT: kernel: DT cpu node bindings update Lorenzo Pieralisi
2013-04-15 19:26   ` Stephen Warren
2013-04-16 10:45     ` Lorenzo Pieralisi
2013-04-16 15:57       ` Stephen Warren
2013-04-16 16:21         ` Benjamin Herrenschmidt
2013-04-16 14:30     ` Dave Martin
2013-04-17  9:14     ` Mark Rutland
2013-04-17 15:14       ` Stephen Warren
2013-04-17 16:02         ` Nicolas Pitre
2013-04-17 16:23           ` Stephen Warren
2013-04-17 16:36             ` Nicolas Pitre
2013-04-17 16:56               ` Dave Martin
2013-04-17 16:24         ` Benjamin Herrenschmidt
2013-04-18 12:40         ` Grant Likely [this message]
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=20130418124021.DE4C63E118C@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.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).