From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@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 15:37:33 -0600 [thread overview]
Message-ID: <20111117213733.GC14736@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <1321556259-4459-2-git-send-email-timur@freescale.com>
On Thu, Nov 17, 2011 at 12:57:39PM -0600, Timur Tabi wrote:
> When the P1022's DIU video controller is active, the pixis must be accessed
> in "indirect" mode, which uses localbus chip select addresses.
>
> Switching between the DVI and LVDS monitor ports is handled by the pixis,
> so that switching needs to be done via indirect mode.
>
> This has the side-effect of no longer requiring U-Boot to enable the DIU.
> Now Linux can enable the DIU all by itself.
Under what circumstances does Linux do this? How does Linux prevent the
NOR flash driver from binding to the device when this mode has been or
will be used?
-Scott
next prev parent reply other threads:[~2011-11-17 21:37 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 [this message]
2011-11-17 22:12 ` Timur Tabi
2011-11-17 22:25 ` Scott Wood
2011-11-17 22:28 ` Timur Tabi
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=20111117213733.GC14736@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@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).