All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Marc Leeman <marc.leeman@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 83xx GPIO/EXT int in arch/powerpc/
Date: Tue, 5 Jun 2007 12:12:16 +0200	[thread overview]
Message-ID: <f2590a315e5c6d3ca3d376cf93adb06a@kernel.crashing.org> (raw)
In-Reply-To: <20070604211740.GN17456@chiana.homelinux.org>

>> pci1: pci@8000 {
>> 	...
>> 	my_pci_device@0 {
>> 		...
>> 		interrupts = <irq#, sense>;
>> 		interrupt-parent = <&ipic>;
>> 	}
>> }
>
> So I don't have to define the GPIO pins in pio-map in "vi) Pin
> configuration nodes" and already set in the U-Boot bootloader?

No, something in the firmware (or bootwrapper, bootloader)
obviously has to set up the GPIO as an external interrupt
source.

> I already tried hardcoding the EXT7 pin as assigned in the ppc arch
> (int 23); this would mean that, in the powerpc arch, the assignments of
> interrupts is different wrt to ppc?

I would hope the kernel isn't messing around with this
at all, and leave such low-level hardware configuration
to the firmware!


Segher

      parent reply	other threads:[~2007-06-05 10:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04  9:56 83xx GPIO/EXT int in arch/powerpc/ Marc Leeman
2007-06-04 19:25 ` Andy Fleming
2007-06-04 19:35   ` Segher Boessenkool
2007-06-04 21:17   ` Marc Leeman
2007-06-04 21:57     ` Andy Fleming
2007-06-05 10:13       ` Segher Boessenkool
2007-06-06  7:03         ` Benjamin Herrenschmidt
2007-06-06  9:47           ` Segher Boessenkool
2007-06-06 22:31             ` Benjamin Herrenschmidt
2007-06-07 12:55               ` Segher Boessenkool
2007-06-11 16:21                 ` Marc Leeman
2007-06-12 13:31                   ` Kumar Gala
2007-06-12 16:06                     ` Marc Leeman
2007-06-14 21:04                       ` Kumar Gala
2007-06-15  8:12                         ` Marc Leeman
2007-06-05 10:12     ` Segher Boessenkool [this message]

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=f2590a315e5c6d3ca3d376cf93adb06a@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=marc.leeman@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.