linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ed Goforth <egoforth@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: 440gx GPIO
Date: Tue, 14 Feb 2006 12:10:15 -0500	[thread overview]
Message-ID: <75b39f010602140910v39bc60dcxeba0acb6065a4bbd@mail.gmail.com> (raw)
In-Reply-To: <20060214170140.GB12465@gate.ebshome.net>

On 2/14/06, Eugene Surovegin <ebs@ebshome.net> wrote:
> On Tue, Feb 14, 2006 at 08:48:56AM -0500, Ed Goforth wrote:
> > I posted the original from home, and didn't have the contents of the
> > config register.  It is
> > cfg     0x00103e00
> > Which I interpret as having bit 11 set: "1 Enable GPIO11 as GPIO11"
> > from the manual.
> >
> > I originally tried to call ioremap64(PPC440GX_GPIO0_ADDR,) directly, bu=
t got
> > "unresolved symbol ioremap64".  From inspection of ioremap(), the
> > fixup for 0x40000700 translates to 0x140000700, and I get the same
> > values in my code as I see from a "/proc/ocotea/gpio".
> >
> > Is my approach valid?
>
> It seems to be.

At least I've got that. :)

>
> Try writing the same GPIO output register value as you read from it
> (without clearing bit 11). Also, try changing some other GPIO bit
> (e.g. one which is not connected in your design). Maybe board hangs
> exactly because you set GPIO bit 11 low :).

I have successfully written back the same values that were read from
it.  I will try your suggestion about fiddling with other GPIO bits
that we aren't (supposed to be) using.

>
> Also, connect scope to that GPIO pin and see what is really going on.
>
> --
> Eugene
>

Thanks,
Ed

  reply	other threads:[~2006-02-14 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14  5:20 440gx GPIO Ed Goforth
2006-02-14  6:59 ` Eugene Surovegin
2006-02-14 13:48   ` Ed Goforth
2006-02-14 17:01     ` Eugene Surovegin
2006-02-14 17:10       ` Ed Goforth [this message]
2006-02-14 21:47         ` Ed Goforth
2006-02-20 17:20       ` Ed Goforth
  -- strict thread matches above, loose matches on Subject: below --
2006-02-15  0:01 Howard, Marc
2006-02-20 17:13 ` Ed Goforth

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=75b39f010602140910v39bc60dcxeba0acb6065a4bbd@mail.gmail.com \
    --to=egoforth@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).