On 9/19/07, S. Fricke <[EMAIL PROTECTED]> wrote:
> OK, my dts is now:
>
> / {
> /* ... */
> [EMAIL PROTECTED] {
> /* ... */
> [EMAIL PROTECTED] {
> interrupt-parent = <500>;
> interrupts = <1 2 2>;
> };
>
Hello,
> > Can u give me an example with a single IRQ of a configuration-node for a
> > dts?
>
> [EMAIL PROTECTED] {
> interrupts = <1 2 3>;
> interrupt-parent = <&mpc5200_pic>;
> };
Ahh - oh weh - so simple! Thank you!
> The interrupts property matches the size of the #interrup
Grant Likely wrote:
>
> No, they are explicitly numbered. Are you looking at the 5200 or the
> 5200B user manual?
MPC5200B User's Manual, Rev. 1.3 (MPC5200BUM.pdf)
> In my copy, on page 7-17, I see this:
Ah! 7-20 here. Do we have different revisions of the manual, perhaps? :)
PSa0 in
> p
On 9/14/07, Matt Sealey <[EMAIL PROTECTED]> wrote:
> Grant Likely wrote:
> > On 9/14/07, Matt Sealey <[EMAIL PROTECTED]> wrote:
> >> sparse, irq_of_find_and_map isn't much help). Maybe I am just not
> >> looking in the right place but not being an MPC52xx PIC Expert I
> >> wouldn't even know where
Grant Likely wrote:
> On 9/14/07, Matt Sealey <[EMAIL PROTECTED]> wrote:
>> sparse, irq_of_find_and_map isn't much help). Maybe I am just not
>> looking in the right place but not being an MPC52xx PIC Expert I
>> wouldn't even know where to start...
>
> The l2 irq numbers map directly to the inter
On 9/14/07, Matt Sealey <[EMAIL PROTECTED]> wrote:
> Grant!
>
> I have a newbie question which I never had properly answered. On the
> MPC52xx and specifically regarding the device tree, how are interrupt
> numbers assigned?
>
> On Efika (and in the DT docs) it's basically the X Y Z where X is the
Grant!
I have a newbie question which I never had properly answered. On the
MPC52xx and specifically regarding the device tree, how are interrupt
numbers assigned?
On Efika (and in the DT docs) it's basically the X Y Z where X is the
type (critical, main, peripheral, sdma), Y is the number of the
On 9/12/07, S. Fricke <[EMAIL PROTECTED]> wrote:
> Hello,
>
> > > I have looked up "kernel/irq/manage.c". "-ENOSYS" is returned on function
> > > "setup_irq" because the used irq(MPC52xx_IRQ2) is the same as no_irq_chip.
> > >
> > > THE MPC52xx_IRQ2 is a excerpt from "include/ppc/mpc52xx.h" (per co
Hello,
> > I have looked up "kernel/irq/manage.c". "-ENOSYS" is returned on function
> > "setup_irq" because the used irq(MPC52xx_IRQ2) is the same as no_irq_chip.
> >
> > THE MPC52xx_IRQ2 is a excerpt from "include/ppc/mpc52xx.h" (per copy
> > paste), but mpc52xx is (now) a powerpc-arch. What is
On 9/11/07, S. Fricke <[EMAIL PROTECTED]> wrote:
> Hello,
>
> > >[...]
> > > intr = mpc52xx_find_and_map("mpc52xx-pic");
> > > if(!intr) {
> > > panic(__FILE__ ": mpc52xx-pic - MAP failed");
> > > }
> > >
> > > set_irq_chip(MPC52xx_IRQ2, &my_irq_chip);
> >
> > You probably d
Hello,
> >[...]
> > intr = mpc52xx_find_and_map("mpc52xx-pic");
> > if(!intr) {
> > panic(__FILE__ ": mpc52xx-pic - MAP failed");
> > }
> >
> > set_irq_chip(MPC52xx_IRQ2, &my_irq_chip);
>
> You probably don't want to do this (unless you are cascading IRQs to
> custom exter
On 9/11/07, S. Fricke <[EMAIL PROTECTED]> wrote:
>
> Dear Linux-enthusiasts,
>
> I'm still at the same problem.
>
> I have now implemented a irq_chip for the hardwired IRQ2. Now I have:
>
>
> --==>
> volatile static struct mpc52xx_intr __iomem *intr;
> unsigned long flags;
> static DEFINE_SPINLOCK(
Dear Linux-enthusiasts,
I'm still at the same problem.
I have now implemented a irq_chip for the hardwired IRQ2. Now I have:
--==>
volatile static struct mpc52xx_intr __iomem *intr;
unsigned long flags;
static DEFINE_SPINLOCK(my_irq_controller_lock);
/*
* HELPER-Function
*/
static inline vo
Hello all.
What are the steps to configure an MPC500B-Board to react on an IRQ (2)?
I have written a test-driver with this code-snippets, but the prozessor
hangs when loading the driver.
my __init-function looks like:
static int __init mod_init( void )
{
volatile static struct mpc52xx_intr
14 matches
Mail list logo
