public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Søren Steen Christensen" <sorenschristensen@stofanet.dk>
To: 'Elvis Dowson' <elvis.dowson@mac.com>,
	'Linux OMAP Users' <linux-omap@vger.kernel.org>
Cc: "'Søren Steen Christensen'" <sorenschristensen@stofanet.dk>
Subject: RE: GPMC address signals gpmc_a11 to gpmc_a26
Date: Wed, 25 Feb 2009 19:46:05 +0100	[thread overview]
Message-ID: <002501c99779$50d1bf10$f2753d30$@dk> (raw)
In-Reply-To: <8DB4EBB8-F339-43DC-B7EF-208CB77BC8A3@mac.com>

> Hi,
> 	Can someone tell me why gpmc_a11 to gpmc_a26 signals are
> missing from
> initial pages for the CBB package specification, in the OMAP3515/03
> Applications Processor document (Rev. C)?
> 
> If you go down to page 91 of the same document, it lists gpmc_a11 to
> gpmc_a26.
> 
> Are the address lines multiplexed somehow for the TI OMAP GPMC,
> because if you look at the following table, the pin numbers are the
> same for a couple of them, e.g AC16 for gpmc_a3, gpmc_a19. I can't
> seem to find a pattern here.
> 
> Best regards,
> 
> Elvis


Hi Elvis,

The GPMC is an address/data-multiplexed bus sharing the lower 16 address
lines between address and data.
I admit, that the naming in the Datasheet might be a bit misleading, but the
way it should be read is like:

GPMC_dxx is the 16 data lines for data

GPMC_dxx is the lower 16 address lines for address
GPMC_a1 is address line 17
GPMC_a2 address line 18
GPMC_a3 address line 19 - and so forth

This as well explains why you though that address lines 3 and 19 could be
multiplexed :-)

Best regards
  Søren


--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

           reply	other threads:[~2009-02-25 19:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <8DB4EBB8-F339-43DC-B7EF-208CB77BC8A3@mac.com>]

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='002501c99779$50d1bf10$f2753d30$@dk' \
    --to=sorenschristensen@stofanet.dk \
    --cc=elvis.dowson@mac.com \
    --cc=linux-omap@vger.kernel.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