linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: contact@paulk.fr (Paul Kocialkowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] Documentation: devicetree: root node serial-number property documentation
Date: Wed, 06 May 2015 16:26:13 +0200	[thread overview]
Message-ID: <1430922373.2577.24.camel@collins> (raw)
In-Reply-To: <CAL_JsqKbSgZ4gXVc=FG_RKic-JM4_Mhzdh3Lh26NCa6zrc74dA@mail.gmail.com>

Le mercredi 06 mai 2015 ? 08:26 -0500, Rob Herring a ?crit :
> On Tue, Apr 28, 2015 at 2:29 AM, Paul Kocialkowski <contact@paulk.fr> wrote:
> > Open firmware is already using the serial-number property for passing the
> > device's serial number from the bootloader to the kernel. In addition, lshw
> > already has support for scanning this property.
> >
> > The serial number is a string that somewhat represents the device's serial
> > number. It might come from some form of storage (e.g. an eeprom) and be
> > programmed at factory-time by the manufacturer or come from identification
> > bits available in e.g. the SoC (note that the soc_id property in the SoC bus
> > should hold a full account of those bits).
> >
> > The serial number is taken as-is from the bootloader, so it is up to the
> > bootloader to define where the serial number comes from and what length it
> > should be. Some use cases for the serial number require it to have a maximum
> > length (e.g. for USB serial number) and some other cases imply more restrictions
> > on what the serial number should look like (e.g. in Android, the ro.serialno
> > property is usually a 16-bytes (plus one null byte) representation of a 64 bit
> > number).
> >
> > Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
> 
> Acked-by: Rob Herring <robh@kernel.org>
> 
> What Russell was referring to for submitting is his patch tracker:
> 
> http://www.arm.linux.org.uk/developer/patches/

Thanks for the hint, that's done now.

> > ---
> >  Documentation/devicetree/booting-without-of.txt | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/Documentation/devicetree/booting-without-of.txt b/Documentation/devicetree/booting-without-of.txt
> > index 7768518..95fc385 100644
> > --- a/Documentation/devicetree/booting-without-of.txt
> > +++ b/Documentation/devicetree/booting-without-of.txt
> > @@ -828,6 +828,10 @@ address which can extend beyond that limit.
> >    name may clash with standard defined ones, you prefix them with your
> >    vendor name and a comma.
> >
> > +  Additional properties for the root node:
> > +
> > +    - serial-number : a string representing the device's serial number
> > +
> >    b) The /cpus node
> >
> >    This node is the parent of all individual CPU nodes. It doesn't
> > --
> > 1.9.1
> >

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150506/fc3e1a07/attachment.sig>

      reply	other threads:[~2015-05-06 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28  7:29 [PATCH v4 1/2] Documentation: devicetree: root node serial-number property documentation Paul Kocialkowski
2015-04-28  7:29 ` [PATCH v4 2/2] arch: arm: Show the serial number from devicetree in cpuinfo Paul Kocialkowski
2015-06-07 17:03   ` Grant Likely
2015-06-11  7:06     ` Paul Kocialkowski
2015-05-06 13:26 ` [PATCH v4 1/2] Documentation: devicetree: root node serial-number property documentation Rob Herring
2015-05-06 14:26   ` Paul Kocialkowski [this message]

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=1430922373.2577.24.camel@collins \
    --to=contact@paulk.fr \
    --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).