linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Lada Podivin <lada.podivin@gmail.com>
To: "Cote, Sylvain" <Sylvain.Cote@verint.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: ppc405ex GPIO mapping
Date: Mon, 22 Jun 2009 18:48:34 +0200	[thread overview]
Message-ID: <e35801cc0906220948v22a13e2fxfcae52d51e69c310@mail.gmail.com> (raw)
In-Reply-To: <579B119545DAEF4689C8FBEEFEC5793F01D4FEF815F1@ATLMBX.verint.corp.verintsystems.com>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

Hi,

I have the same board and I had a similar problem. I use 2.6.30, so I don't
know whether 2.6.25 supports the following - however, here's my suggestion.
Set these options in your kernel config: CONFIG_GPIOLIB=y and
CONFIG_PPC4xx_GPIO=y. Before compilation do "export
KCPPFLAGS=-DARCH_NR_GPIOS=32" - you have to let the kernel know, that your
GPIO has 32 pins (default value is 255) and compile the kernel.

Then change the line

compatible = "ibm,gpio-405ex";

to

compatible = "ibm,ppc4xx-gpio";

Ok! After this long journey you shoul be able to work with your GPIO pins
with functions like gpio_set_value() - from include/linux/gpio.h.
Documentation of these functions can be seen at
http://www.mjmwired.net/kernel/Documentation/gpio.txt

So, this is my solution. Maybe there are better ones, but this works well
for me :)

Best,
Lada Podivin

[-- Attachment #2: Type: text/html, Size: 1123 bytes --]

  reply	other threads:[~2009-06-22 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 15:13 ppc405ex GPIO mapping Cote, Sylvain
2009-06-22 16:48 ` Lada Podivin [this message]
2009-06-23  6:29   ` Lada Podivin

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=e35801cc0906220948v22a13e2fxfcae52d51e69c310@mail.gmail.com \
    --to=lada.podivin@gmail.com \
    --cc=Sylvain.Cote@verint.com \
    --cc=linuxppc-dev@lists.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).