linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ludovic Desroches" <ludovic.desroches@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Using GPIO
Date: Fri, 6 Jun 2008 09:51:37 +0200	[thread overview]
Message-ID: <388e90610806060051w6826b028h464cd5bc321f75fe@mail.gmail.com> (raw)

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

Hi,

I am also trying to use Xilinx GPIO driver on my board but I encounter some
problems. I thought they will be resolved with this information but it
doesn't.

I use GPIO driver as built-in but during kernel boot but I don't see log
about it contrary to Xemac driver for instance. First I wanted to create my
gpio driver normally without using Xilinx one, with ioremap and writel/readl
but I didn't write anything in the register, I don't know why. Then I tried
to use Xilinx GPIO driver but I don't know why I don't hit xgpio_probe,
xgpio_init returns 0 so it's OK.

Do you have any idea ?

Thanks

Ludovic Desroches


> arch/ppc/syslib/virtex_devices.c:
>
> >* // 0 is LEDS_4BIT, 1 is LEDS_POSITIONS, 2 is PUSH_BUTTONS_POSITION
> *>* #define XPAR_GPIO(num) { \
> *>*    .name = "xilinx_gpio", \
> *>*    .id = num, \
> *>*    .num_resources = 2, \
> *That was a 2.
> If anybody wants to make a patch out of those few lines of code, I couldn't
> figure out how to do this with git... But I will use a more general GPIO
> approach as soon as I can put my hands on our custom card.
>
> >*    .resource = (struct resource[]) { \
> *>*        { \
> *>*            .start = XPAR_GPIO_##num##_BASEADDR, \
> *>*            .end = XPAR_GPIO_##num##_HIGHADDR, \
> *>*            .flags = IORESOURCE_MEM, \
> *>*        }, \
> *>*        { \
> *>*            .start = XPAR_INTC_0_GPIO_##num##_VEC_ID, \
> *>*            .flags = IORESOURCE_IRQ, \
> *>*        }, \
> *>*    }, \
> *>* }
> *>* [...]
> *>*      /* GPIO instances */
> *>* #if defined(XPAR_GPIO_0_BASEADDR)
> *>*      XPAR_GPIO(0),
> *>* #endif
> *>* #if defined(XPAR_GPIO_1_BASEADDR)
> *>*      XPAR_GPIO(1),
> *>* #endif
> *>* #if defined(XPAR_GPIO_2_BASEADDR)
> *>*      XPAR_GPIO(2),
> *>* #endif
> *
>
>

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

             reply	other threads:[~2008-06-06  7:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06  7:51 Ludovic Desroches [this message]
2008-06-06 16:09 ` Using GPIO Guillaume Dargaud
  -- strict thread matches above, loose matches on Subject: below --
2008-05-19 15:23 Guillaume Dargaud
2008-05-15 16:35 Guillaume Dargaud
2008-05-15 18:39 ` John Bonesio
2008-05-15 18:56   ` Stephen Neuendorffer
2008-05-16  8:15   ` Guillaume Dargaud
2008-05-16 16:17     ` John Linn
2008-05-19 11:56       ` Guillaume Dargaud
2008-05-19 13:42         ` Josh Boyer

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=388e90610806060051w6826b028h464cd5bc321f75fe@mail.gmail.com \
    --to=ludovic.desroches@gmail.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;
as well as URLs for NNTP newsgroup(s).