linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, kumar.gala@freescale.com
Subject: Re: [PATCH 2/2] powerpc/85xx: p1022ds: enable monitor switching via pixis indirect mode
Date: Thu, 17 Nov 2011 16:28:48 -0600	[thread overview]
Message-ID: <4EC58AA0.2070905@freescale.com> (raw)
In-Reply-To: <20111117222515.GA18827@schlenkerla.am.freescale.net>

Scott Wood wrote:

> As we discussed earlier, you could have a kernel boot parameter that
> indicates what mode you'd like the localbus to run in.  Then, platform
> code could update the device tree before any drivers bind.

How do I update the device tree from platform code?

> Or, have U-boot set up the desired mode before entering the kernel, and
> provide an appropriate device tree.

I can both of these features, but not in this patch.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2011-11-17 22:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17 18:57 [PATCH 1/2] powerpc/85xx: add pixis indirect mode device tree node Timur Tabi
2011-11-17 18:57 ` [PATCH 2/2] powerpc/85xx: p1022ds: enable monitor switching via pixis indirect mode Timur Tabi
2011-11-17 21:29   ` Stephen Rothwell
2011-11-17 22:09     ` Timur Tabi
2011-11-19  1:04       ` Stephen Rothwell
2011-11-21 17:01         ` Timur Tabi
2011-11-17 21:37   ` Scott Wood
2011-11-17 22:12     ` Timur Tabi
2011-11-17 22:25       ` Scott Wood
2011-11-17 22:28         ` Timur Tabi [this message]
2011-11-17 22:45           ` Scott Wood
2011-11-18 17:00             ` Timur Tabi
2011-11-18 18:06               ` Scott Wood
2011-11-18 18:08                 ` Timur Tabi
2011-11-17 21:50 ` [PATCH 1/2] powerpc/85xx: add pixis indirect mode device tree node Scott Wood

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=4EC58AA0.2070905@freescale.com \
    --to=timur@freescale.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.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 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).