All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	'Thomas Abraham' <thomas.ab@samsung.com>,
	'Ilho Lee' <ilho215.lee@samsung.com>
Subject: Re: [PATCH v2 1/3] arm64: dts: add initial dts for Samsung GH7 SoC and SSDK-GH7 board
Date: Fri, 14 Mar 2014 12:48:31 +0000	[thread overview]
Message-ID: <20140314124831.GU366@sirena.org.uk> (raw)
In-Reply-To: <20140313103329.GD5035@e106331-lin.cambridge.arm.com>

[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]

On Thu, Mar 13, 2014 at 10:33:29AM +0000, Mark Rutland wrote:
> On Wed, Mar 12, 2014 at 04:31:56AM +0000, Kukjin Kim wrote:

> > > > +/ {
> > > > +	model = "SAMSUNG SSDK-GH7 board based on GH7 SoC";

> > > Is the "based on GH7 SoC" part necessary? Does the "SSDK-GH7" not give
> > > that away?

> > In this case, yes, SSDK-GH7 is enough but I though, in case of different
> > board adding what SoC is used on the board in that is useful. Anyway, OK.

> Looking at ePAPR, the recommended format is "manufacturer,model", and
> the string is intended to identify a particular implementation. It is
> not intended to give details about the implementation that can be
> derived from the name.

> We seem to have ignored the format (and to some degree purpose) of the
> model property so far, but I don't see any reason to fill it with
> unnecessary information.

Might it be worth defining a property explicitly intended to be used as
a display name for human consumption?  Half the problem with model is
that we don't have a way to use it for quirking so nobody ever really
looks at it (though I guess we will want that at some point now we're
going for fixed ABI stuff), but not having a place to put a pretty name
does encourage this sort of thing.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] arm64: dts: add initial dts for Samsung GH7 SoC and SSDK-GH7 board
Date: Fri, 14 Mar 2014 12:48:31 +0000	[thread overview]
Message-ID: <20140314124831.GU366@sirena.org.uk> (raw)
In-Reply-To: <20140313103329.GD5035@e106331-lin.cambridge.arm.com>

On Thu, Mar 13, 2014 at 10:33:29AM +0000, Mark Rutland wrote:
> On Wed, Mar 12, 2014 at 04:31:56AM +0000, Kukjin Kim wrote:

> > > > +/ {
> > > > +	model = "SAMSUNG SSDK-GH7 board based on GH7 SoC";

> > > Is the "based on GH7 SoC" part necessary? Does the "SSDK-GH7" not give
> > > that away?

> > In this case, yes, SSDK-GH7 is enough but I though, in case of different
> > board adding what SoC is used on the board in that is useful. Anyway, OK.

> Looking at ePAPR, the recommended format is "manufacturer,model", and
> the string is intended to identify a particular implementation. It is
> not intended to give details about the implementation that can be
> derived from the name.

> We seem to have ignored the format (and to some degree purpose) of the
> model property so far, but I don't see any reason to fill it with
> unnecessary information.

Might it be worth defining a property explicitly intended to be used as
a display name for human consumption?  Half the problem with model is
that we don't have a way to use it for quirking so nobody ever really
looks at it (though I guess we will want that at some point now we're
going for fixed ABI stuff), but not having a place to put a pretty name
does encourage this sort of thing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140314/14d82e38/attachment.sig>

  parent reply	other threads:[~2014-03-14 12:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 22:51 [PATCH v2 0/3] arm64: add new support Samsung GH7 SoC and SSDK board Kukjin Kim
2014-03-10 22:51 ` Kukjin Kim
2014-03-10 22:51 ` [PATCH v2 1/3] arm64: dts: add initial dts for Samsung GH7 SoC and SSDK-GH7 board Kukjin Kim
2014-03-10 22:51   ` Kukjin Kim
2014-03-11 11:59   ` Catalin Marinas
2014-03-11 11:59     ` Catalin Marinas
2014-03-11 18:29   ` Mark Rutland
2014-03-11 18:29     ` Mark Rutland
2014-03-12  4:31     ` Kukjin Kim
2014-03-12  4:31       ` Kukjin Kim
2014-03-13 10:33       ` Mark Rutland
2014-03-13 10:33         ` Mark Rutland
2014-03-14  1:26         ` Kukjin Kim
2014-03-14  1:26           ` Kukjin Kim
2014-03-18 18:10           ` Mark Rutland
2014-03-18 18:10             ` Mark Rutland
2014-03-19  8:33             ` Kukjin Kim
2014-03-19  8:33               ` Kukjin Kim
2014-03-14 12:48         ` Mark Brown [this message]
2014-03-14 12:48           ` Mark Brown
2014-03-10 22:51 ` [PATCH v2 2/3] arm64: defconfig: Enable ARCH_GH7 by default Kukjin Kim
2014-03-10 22:51   ` Kukjin Kim
2014-03-11 12:01   ` Catalin Marinas
2014-03-11 12:01     ` Catalin Marinas
2014-03-11 22:45     ` Kukjin Kim
2014-03-11 22:45       ` Kukjin Kim
2014-03-10 22:51 ` [PATCH v2 3/3] Documentation: DT: add new entry for Samsung GH7 SoC and SSDK board Kukjin Kim
2014-03-10 22:51   ` Kukjin Kim
2014-03-11 12:02   ` Catalin Marinas
2014-03-11 12:02     ` Catalin Marinas

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=20140314124831.GU366@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Catalin.Marinas@arm.com \
    --cc=ilho215.lee@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=thomas.ab@samsung.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.