linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sébastien Chrétien" <sebastien.chretien.enseirb@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: irq
Date: Wed, 3 Sep 2008 17:03:46 +0200	[thread overview]
Message-ID: <319b0ac50809030803p6d659468wd7d2425224653374@mail.gmail.com> (raw)
In-Reply-To: <48BEA106.9090307@selcomgroup.com>

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

The failure referes to setup_irq :
desc->chip == &no_irq_chip is true

What is irq_desc and how can I initialize it ?


setup_irq(unsigned int irq, struct irqaction *new)
{
    struct irq_desc *desc = irq_desc + irq;
    struct irqaction *old, **p;
    const char *old_name = NULL;
    unsigned long flags;
    int shared = 0;

    if (irq >= NR_IRQS)
        return -EINVAL;

    printk("desc\n");
    if (desc->chip == &no_irq_chip)
        return -ENOSYS;
    printk("desc2\n");

2008/9/3, Daniele Bosi <d.bosi@selcomgroup.com>:
>
> Try to set some flag into the third parameter of the request_irq()
> function like:
>
> SA_SHIRQ                Interrupt is shared
>
> SA_INTERRUPT            Disable local interrupts while processing
>
> SA_SAMPLE_RANDOM        The interrupt can be used for entropy
>
> otherwise try to use the function install_irq_handler()
>
>
> bye Daniele
>
>
>
> Sébastien Chrétien ha scritto:
>
> > Hello,
> >
> > I am trying to register a function writh IRQ :
> >
> > static irqreturn_t uart_test (int irq , void *dev_id)
> > {
> >     printk("/!\\ Interruption : tx_empty\n");
> >        return IRQ_HANDLED;
> > }
> >
> >     req=request_irq(0x18,uart_test,NULL,"uart_test",NULL);
> >     printk("Initialisation IRQ UART : %d \n", req);
> >
> > When I boot linux ppc, the req value is -38.
> > What is wrong ?
>
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Linuxppc-dev mailing list
> > Linuxppc-dev@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
> --
>
>
> ------------------------------------------------------------------------
>
>
>   Daniele Bosi
>
> *DIGITEK S.p.A.*
>
> Via L. Romagnoli 24,
> 41033 Concordia sulla Secchia
> Modena (MO), Italy
>
> *Tel*: +39-(0)53556942 Fax. +39-(0)53554550
>
> *Web:    * http://www.digitek.it
>
> *Mail to:* d.bosi@selcomgroup.com <mailto:d.bosi@selcomgroup.com>
>
>

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

  reply	other threads:[~2008-09-03 15:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 14:15 irq Sébastien Chrétien
2008-09-03 14:36 ` irq Daniele Bosi
2008-09-03 15:03   ` Sébastien Chrétien [this message]
2008-09-03 16:05     ` irq M B
2008-09-03 16:36       ` irq Sébastien Chrétien
2008-09-03 17:08         ` irq Scott Wood
2008-09-03 21:02           ` irq Sébastien Chrétien
2008-09-03 21:03             ` irq Scott Wood
2008-09-04  3:02             ` irq Benjamin Herrenschmidt
2008-09-04  8:27               ` irq Sébastien Chrétien
2008-09-04 13:23                 ` irq Sébastien Chrétien
2008-09-04 14:18                   ` irq Scott Wood

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=319b0ac50809030803p6d659468wd7d2425224653374@mail.gmail.com \
    --to=sebastien.chretien.enseirb@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).