All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: FDT for MPC5200, CPU revision, MSCAN
Date: Fri, 20 Apr 2007 18:11:46 +0200	[thread overview]
Message-ID: <4628E642.1050702@grandegger.com> (raw)
In-Reply-To: <528646bc0704200702i328ba9dbvc62473e5a634d5ac@mail.gmail.com>

Grant Likely wrote:
> On 4/20/07, Wolfgang Grandegger <wg@grandegger.com> wrote:
>> Wolfgang Grandegger wrote:
>> > Hello,
>> >
>> > is there a way to distinguish the CPU revision (Rev.A vs. Rev.B) of the
>> > MPC5200, preferably at run time? Or should this be defined in the FDT?
>> > I ask, because some settings depend on the CPU revision due to hardware
>> > bugs, like the clock source used for MSCAN.
> 
> This stuff is defined in the device tree.  If you need to detect the
> version at runtime, then ideally your bootloader will read the PVR/SVR
> to determine the chip version and then pass the correct FDT to the
> kernel.

OK, I already realized the revision field in the DTS.

>> I found the information here:
>>
>> $ cat Documentation/powerpc/mpc52xx-device-tree-bindings.txt
> <snip>
>> Sorry for the noise.
> 
> Not noise; good question.

OK, then more questions for MSCAN related properties. The clock source 
for MSCAN is either derived from IPB or directly from the oscillator 
clock via CLKSRC bit. I guess that the property "system-clock" should 
provide that frequency:

$ cat Documentation/powerpc/mpc52xx-device-tree-bindings.txt
...
system-frequency        int             Fsystem frequency; source of all
                                         other clocks.

It needs also to be defined by the boot loader.

Thanks.

Wolfgang.

      reply	other threads:[~2007-04-20 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20  6:59 FDT for MPC5200, CPU revision, MSCAN Wolfgang Grandegger
2007-04-20  7:21 ` Wolfgang Grandegger
2007-04-20 14:02   ` Grant Likely
2007-04-20 16:11     ` Wolfgang Grandegger [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=4628E642.1050702@grandegger.com \
    --to=wg@grandegger.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.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 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.