From: Ben Warren <bwarren@qstreams.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: GPIO endianness on MPC8349
Date: Mon, 10 Apr 2006 16:20:20 -0400 [thread overview]
Message-ID: <1144700420.972.112.camel@saruman.qstreams.net> (raw)
In-Reply-To: <6518EE00-812C-4839-AF00-AA976C35E799@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
Sorry for wasting bandwidth (again). Turns out my schematic is for an
earlier spin of the board.
regards,
Ben
On Mon, 2006-04-10 at 15:06 -0500, Kumar Gala wrote:
> On Apr 10, 2006, at 2:48 PM, Ben Warren wrote:
>
> > Hello,
> >
> > I'm a noobie to this CPU, and am utterly confused with how the bits
> > are
> > ordered on the GPIO ports. I imagine it's the same as all Freescale
> > PPCs, but who knows. Anyway...
> >
> > Using an MPC8349MDS eval board, I have one LED to play with. From the
> > schematic, it's connected to GPIO1[1]. From other processors that
> > I've
> > worked with, I would have expected to toggle it with either 0x40000000
> > (IBM 405) or 0x00000002 (68360). Nope. To make this bit move, I mess
> > with bit 0x00000040 in the appropriate DAT register. This leads me to
> > believe that either the bit ordering is something
> > like ...89abcdef01234567 (sorry for the confusing notation, but
> > hopefully it makes sense) or the schematic has a typo. Since I'm
> > trying
> > to write a generic GPIO handler, I'd like to have a little
> > confidence in
> > my extrapolation from a single point.
> >
> > Can anybody shed some light on this?
>
> This is because the Freescale docs are misleading. If you look at
> the schematic you will see the LED is wired to GPIO1[5] which makes
> sense for the 0x40 value you have to use.
>
> - kumar
[-- Attachment #2: Type: text/html, Size: 2480 bytes --]
prev parent reply other threads:[~2006-04-10 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 19:48 GPIO endianness on MPC8349 Ben Warren
2006-04-10 20:06 ` Kumar Gala
2006-04-10 20:20 ` Ben Warren [this message]
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=1144700420.972.112.camel@saruman.qstreams.net \
--to=bwarren@qstreams.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@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