From: "Sébastien Chrétien" <sebastien.chretien.enseirb@gmail.com>
To: M B <super.firetwister@googlemail.com>
Cc: "Sébastien Chrétien" <sebastien.chretien.enseirb@gmail.com>,
linuxppc-dev@ozlabs.org
Subject: Re: irq
Date: Wed, 03 Sep 2008 18:36:39 +0200 [thread overview]
Message-ID: <48BEBD17.1030705@gmail.com> (raw)
In-Reply-To: <6a6049b80809030905u561043ecr1438d20aebf5598d@mail.gmail.com>
Ok I will try irq_create_mapping tomorrow.
When have I to use this function ?
I am using a MPC7448.
M B a écrit :
> Hi,
>
> this seems to be the same problem I had, when registering an irq with UIO.
>
> On Wed, Sep 3, 2008 at 5:03 PM, Sébastien Chrétien
> <sebastien.chretien.enseirb@gmail.com> wrote:
>
>> The failure referes to setup_irq :
>> desc->chip == &no_irq_chip is true
>>
>> What is irq_desc and how can I initialize it ?
>>
>
> I did use irq_create_mapping, to initialize this struct. However I
> have no idea if this was right. It seemed to work at first, but I'm
> encountering problems now, however I don't know if they come from the
> kernel, or UIO interrupt handler. I did this for some test, but irqs
> are something you want to be sure they work correctly.
>
> So maybee someone could clarify this as we already raise this issue.
>
> What processor are you using Sebastien? My one is a 405EP
>
> Best Regards
>
> Markus
>
>
>
next prev parent reply other threads:[~2008-09-03 16:37 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 ` irq Sébastien Chrétien
2008-09-03 16:05 ` irq M B
2008-09-03 16:36 ` Sébastien Chrétien [this message]
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=48BEBD17.1030705@gmail.com \
--to=sebastien.chretien.enseirb@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=super.firetwister@googlemail.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 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).