linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jochen Friedrich <jochen@scram.de>
To: Jochen Friedrich <jochen@scram.de>,
	Scott Wood <scottwood@freescale.com>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH/RFC] powerpc: DBox2 Board Support
Date: Wed, 26 Dec 2007 16:12:30 +0100	[thread overview]
Message-ID: <47726F5E.6040207@scram.de> (raw)
In-Reply-To: <20071225010412.GL21311@localhost.localdomain>

Hi David,

>>>> +			// Port D is LCD exclusive. Don't export as GPIO
>>>> +			CPM1_PIO: pio@970 {
>>>> +				compatible = "fsl,cpm1-pario";
>>>> +				reg = <970 180>;
>>>> +				num-ports = <3>;
>>>> +				#gpio-cells = <2>;
>>>> +			};
>>>> +
>>>> +			lcd@970 {
>>>> +				reg = <970 10>;
>>>> +				compatible = "samsung,ks0713";
>>> Is this representing an LCD controller, or the display itself.  Either
>>> way I'm surprised there's something here in the SoC that has a
>>> compatible string that's not "fsl,something"
>> It's a LCD controller wired to PortD. PortD is used for four 1bit lines
>> and one 8bit bus.
> 
> I'm still kind of confused here.  Does the pio@970 node above
> represent the PortD controller?  If the LCD controller is accessed
> solely through PortD, then it should be a child of the PortD node.
> 
> At present, pio and lcd have overlapping reg resources which is
> certainly wrong.
> 

pio@970 represent 4 ports (A-D). Ports A-C are used as GPIO lines. Port D
is exclusively used for the LCD, but it needs an 8bit accessor. Unfortunately,
the GPIO API doesn't have such an accessor, so the LCD driver needs to access
Port D itself and needs to make sure no other driver can access Port D via the
GPIO API. The representation as child of pio seems reasonable.

Thanks,
Jochen

  reply	other threads:[~2007-12-26 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-22 19:13 [PATCH/RFC] powerpc: DBox2 Board Support Jochen Friedrich
2007-12-23  8:18 ` Stephen Rothwell
2007-12-23 23:03 ` David Gibson
2007-12-24 11:01   ` Jochen Friedrich
2007-12-25  1:04     ` David Gibson
2007-12-26 15:12       ` Jochen Friedrich [this message]
2007-12-24 16:53 ` Kumar Gala
2008-01-02 18:06 ` Scott Wood
2008-01-02 20:29   ` Jochen Friedrich
2008-01-02 21:22     ` 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=47726F5E.6040207@scram.de \
    --to=jochen@scram.de \
    --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).