LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Hane <jeff.hane@maxim-ic.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: GPIOs 49-63 on 460EX
Date: Mon, 31 Aug 2009 15:01:20 -0700	[thread overview]
Message-ID: <1251756080.19346.44.camel@qu102.quarc.com> (raw)


Hello,

 We are having a problem trying to use gpio 49-63 on our amcc
canyonlands board.  I'm aware these pins are shared with the trace port,
so wrote 0x7ff to SDR0_PFC0 register to make sure they were all in gpio
mode. 

 I set the gpio to output and then try to drive a 1 out but I can never
see it.  I doubled checked the pin with the value reported by the SW and
it never toggles.  If I set the value to 1, I can see a 1 in the gpio OR
register, but the IR stays 0(IR is what is read by get_value)
 
 I can change the direction and value the first 16 gpios in gpio
controller 1 but not the upper 16 bits.  So this means that gpio 48
doesn't work either; thus 16 of the gpio don't work(for out, I haven't
tried in)

 I am running 2.6.30.  Has anybody seen this?  Am I missing a register
somewhere?

thanks,
jeff

                 reply	other threads:[~2009-08-31 22:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1251756080.19346.44.camel@qu102.quarc.com \
    --to=jeff.hane@maxim-ic.com \
    --cc=linuxppc-dev@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