From: Jiri Slaby <jirislaby@gmail.com>
To: Chris Rutherford <chrismrutherford@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ldd irq problem
Date: Fri, 30 Nov 2007 11:31:29 +0100 [thread overview]
Message-ID: <474FE681.9080101@gmail.com> (raw)
In-Reply-To: <40dfeece0711300128s731b3227xaa0b5982193e4b12@mail.gmail.com>
On 11/30/2007 10:28 AM, Chris Rutherford wrote:
> Helo lkml,
>
> I'm trying to write a LDD but I have got a bug. Any ideas what i
> might be doing wrong?
>
> ret = request_irq(12, handler, SA_INTERRUPT | SA_SHIRQ, "sha1
> handler", DEVICE_NAME);
> printk (KERN_INFO "req irq %d \n", ret);
> enable_irq(12);
enable_irq is opposite of disable_irq(_nosync), you don't need to call it in
probe function and in most cases you don't need it at all.
regards,
--
Jiri Slaby (jirislaby@gmail.com)
Faculty of Informatics, Masaryk University
next prev parent reply other threads:[~2007-11-30 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40dfeece0711291447m2efa4f40i5c2c22a4273ecbc0@mail.gmail.com>
2007-11-30 9:28 ` ldd irq problem Chris Rutherford
2007-11-30 10:31 ` Jiri Slaby [this message]
2007-11-30 17:39 ` Chris Rutherford
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=474FE681.9080101@gmail.com \
--to=jirislaby@gmail.com \
--cc=chrismrutherford@googlemail.com \
--cc=linux-kernel@vger.kernel.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).