linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Interrupt handling triggered by GPIO-input on 405EP?
Date: Tue, 18 May 2004 16:55:42 +0200	[thread overview]
Message-ID: <40AA23EE.9080105@egholm-nielsen.dk> (raw)
In-Reply-To: <80908CC5B2C9DB47AAF8C77892FCB44315F780@lion.vector.com.pl>

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

Hi Andriy,

>> I've done some initial coding with the ibmgpio driver with my
>> PPC405EP (PPChamelon) board, and inspired by the
>> "gpio_test.c"-application, I've succeeded in turning on some
>> attached LEDs on some of the ports
> can you please share code for manipulating LEDs on PPChameleon? I'm
> using the same board and it would be fine to have such possibility.
I've attached my source-file for turning on LEDs (indirectly) connected
to GPIO-pins 11,13 and 15 on the PPChamelon board.
First of all I created the /dev/gpio device by the command:

mknod /dev/gpio c 10 185

and then you can open and close the pins as you like. :o)

// Martin

[-- Attachment #2: gpio_test.c --]
[-- Type: text/plain, Size: 836 bytes --]

#include <stdio.h>
#include <fcntl.h>
#include <errno.h>
#include <string.h>

#include <linux/types.h>
#include <linux/ioctl.h>

#include <linux/ibm_ocp_gpio.h>

#define GPIO_DEV "/dev/gpio"

int main(int argc, char *argv[])
{
	/* Open the device */
	int fd = open("/dev/gpio", O_RDWR);

	struct ibm_gpio_ioctl_data gpio_ioctl;
	int result;
	int command;

	if(fd==-1) {
		fprintf(stderr,"Unable to open /dev/gpio\n");
		exit(1);
	}

	gpio_ioctl.device=0;

	/* Set IRQ4 pin (GPIO0_21) high - turn on LED */
	gpio_ioctl.mask=0x00000400;
	gpio_ioctl.data=0x00000400;
	ioctl(fd,IBMGPIO_OUT,(void *)&gpio_ioctl);

	/* Sleep 1 second */
	sleep(1);

	/* Set IRQ3-5 pin (GPIO0_20-GPIO0_22) high - turn on LEDs */
	gpio_ioctl.mask=0x00000E00;
	gpio_ioctl.data=0x00000E00;
	ioctl(fd,IBMGPIO_OUT,(void *)&gpio_ioctl);

	close( fd );

	return 0;
}

       reply	other threads:[~2004-05-18 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <80908CC5B2C9DB47AAF8C77892FCB44315F780@lion.vector.com.pl>
2004-05-18 14:55 ` Martin Egholm Nielsen [this message]
2004-05-18 12:29 Interrupt handling triggered by GPIO-input on 405EP? Martin Egholm Nielsen
     [not found] ` <008a01c43ce1$9a65fda0$0301a8c0@chuck2>
2004-05-18 15:01   ` Martin Egholm Nielsen

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=40AA23EE.9080105@egholm-nielsen.dk \
    --to=martin@egholm-nielsen.dk \
    --cc=linuxppc-embedded@lists.linuxppc.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).