linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] ep93xx: added chip revision reading function
Date: Sat, 20 Mar 2010 19:25:00 +0100	[thread overview]
Message-ID: <20100320182500.GF30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <56d259a01003201107s758b420bmafa154714a8a8fee@mail.gmail.com>

On Sat, Mar 20, 2010 at 06:07:50PM +0000, Martin Guy wrote:
>   The chip revision is normally placed in the global unsigned int
> "system_rev", which is also reported by /proc/cpuinfo.

No, that's the hardware revision number, which is different from the
chip revision number.

system_rev is also what is exported via /proc/cpuinfo because userland
software may need this information to adjust their runtime behaviour.

>   It normally seems to be set from the atags passed by the bootloader
> but uboot on this platform doesn't provide that, so it remains 0.

And this is exactly why it should be passed down from the bootloader.
Either the bootloader is special to each hardware revision (which is
command practice), or it is able to read the revision number from a
bunch of pull-up/down resistors.

>   The same applies to the very similar variables system_serial_low and
> system_serial_high (which also remain 0 on this u-boot platform).
> Shall we also set these from the hardware on ep93xx during thus giving
> them non-zero values in /proc/cpuinfo too?

If the ep93xx provides a unique serial number, then this could be an
idea. I would still only set it in case it has not been given by the
bootloader though.

Daniel

  reply	other threads:[~2010-03-20 18:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 16:59 [PATCH v2 0/3] spi: driver for Cirrus EP93xx SPI controller Mika Westerberg
2010-03-18 17:00 ` [PATCH v2 1/3] spi: implemented " Mika Westerberg
2010-03-18 17:00   ` [PATCH v2 2/3] ep93xx: added chip revision reading function Mika Westerberg
2010-03-18 17:00     ` [PATCH v2 3/3] ep93xx: SPI driver platform support code Mika Westerberg
2010-03-18 17:27     ` [spi-devel-general] [PATCH v2 2/3] ep93xx: added chip revision reading function H Hartley Sweeten
2010-03-25  9:06       ` Mika Westerberg
2010-03-25 17:20         ` H Hartley Sweeten
2010-03-26 15:40           ` Martin Guy
2010-03-20 18:07     ` Martin Guy
2010-03-20 18:25       ` Daniel Mack [this message]
2010-03-20 18:40         ` Martin Guy
2010-03-20 19:31           ` H Hartley Sweeten
2010-03-20 19:48             ` Martin Guy
2010-03-20 18:31       ` Mika Westerberg
2010-03-20 19:42         ` H Hartley Sweeten
2010-03-21 18:45           ` Mika Westerberg
2010-03-25 13:49   ` [PATCH v2 1/3] spi: implemented driver for Cirrus EP93xx SPI controller Martin Guy
2010-03-25 18:43     ` Mika Westerberg
2010-04-01  0:15       ` Martin Guy
2010-04-01  3:00         ` Ryan Mallon
2010-04-01  6:26         ` Mika Westerberg
2010-04-06  5:44         ` Mika Westerberg
2010-04-06 12:50           ` Martin Guy
2010-04-06 18:18             ` Mika Westerberg
2010-04-06 21:28               ` Martin Guy
2010-04-09 17:56                 ` Martin Guy
2010-04-09 18:08                   ` Martin Guy
2010-04-10 15:54                   ` Mika Westerberg
2010-04-11 14:24                     ` Martin Guy
2010-04-12 10:03                     ` Martin Guy

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=20100320182500.GF30801@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --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).