LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux PPC Mailing List <linuxppc-dev@lists.ozlabs.org>
Subject: followup: kernel manipulation of {bus,brg}-frequency for MPC8360?
Date: Sat, 7 May 2016 09:09:31 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1605070850530.5054@localhost.localdomain> (raw)


  followup to earlier post and WARNING -- my ppc dev box is suddenly
off the net so i'm doing all this from memory. le *sigh*.

  again in context of porting linux (4.1 kernel, using v2015.10 uboot)
to MPC8360 target, a couple of questions.

  first, while in this case u-boot might be modifying some of the
values in the DTB before passing it to the kernel, is it true that the
contents of the /proc/devicetree directory on the running linux system
represent the DTB as it was passed from u-boot, or after it was
possibly modified by the PPC kernel boot code? (clearly, this isn't
exclusively a PPC issue -- it's a more general device tree issue.)

  second (and more involved) question, i noticed pretty quickly that
the two frequency values i was interested in were visible under /sys
... from memory, /sys/firmware(?).../ and so on. i also noticed they
were stored in internal format so i needed to run them through
"hexdump" to get their values, no problem.

  i'm assuming *those* values for {bus,brg}-frequency visible under
/sys *are* the final values, after possible processing by the kernel
boot code. in my case (MPC8360), which ppc boot files are responsible
for checking the values passed in the DTB and possibly adjusting them
early in the boot process?

  not looking for extensive explanation, i already see what look like
potentially relevant files under arch/powerpc:

  * sysdev/fsl_soc.c
  * sysdev/qe_lib/qe.c
  * boot/devtree.c

am i at least looking in the right place? thanks.

rday

p.s. if there is something online that addresses the values of
bus-frequency and brg-frequency that's relevant, by all means, let me
know. i'm just perusing the kernel doc file
Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe.txt

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

                 reply	other threads:[~2016-05-07 13:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.20.1605070850530.5054@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linuxppc-dev@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox