From: Philipp Ittershagen <lists@gate-nine.de>
To: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Getting the IRQ number (Was: Basic driver devel questions ?)
Date: Wed, 01 Dec 2010 19:29:53 +0100 [thread overview]
Message-ID: <4CF69421.10206@gate-nine.de> (raw)
In-Reply-To: <201012011735.58769.dargaud@lpsc.in2p3.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/01/2010 05:35 PM, Guillaume Dargaud wrote:
> Now how do I connect the dots between the hardware definitions from the dts and
> my driver ?
You can get the interrupt number from the dt by calling
irq_of_parse_and_map(). Be sure to pass the node of your device to this
function.
Then you have to request the interrupt by calling request_irq. This is
where you specify the interrupt handler.
> But first I'm not sure where to find the IRQ in there, and also I'm not sure if
> reading the filesystem from a module is allowed.
Why do you want to read the file system?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkz2lCEACgkQCG4q0RxCsY4GpgCgiQFRhiF7jjhUdZcUBc4Y5ScJ
E0AAn0VxcCaVexepjrah64ZSS+Xhbed8
=h97e
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-12-01 18:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 10:15 Basic driver devel questions ? Guillaume Dargaud
2010-12-01 12:19 ` Michael Ellerman
2010-12-01 16:35 ` Getting the IRQ number (Was: Basic driver devel questions ?) Guillaume Dargaud
2010-12-01 18:29 ` Philipp Ittershagen [this message]
2010-12-01 18:41 ` Scott Wood
2010-12-02 15:36 ` Guillaume Dargaud
2010-12-02 16:17 ` Timur Tabi
2010-12-02 17:47 ` Guillaume Dargaud
2010-12-02 20:22 ` Benjamin Herrenschmidt
2010-12-03 14:58 ` Guillaume Dargaud
2010-12-03 15:37 ` Martyn Welch
2010-12-06 5:29 ` Michael Ellerman
2010-12-06 6:35 ` Jeremy Kerr
2010-12-06 11:56 ` Michael Ellerman
2010-12-06 9:58 ` Guillaume Dargaud
2010-12-06 12:07 ` Michael Ellerman
2010-12-06 14:44 ` Guillaume Dargaud
2010-12-06 14:47 ` David Laight
2010-12-08 1:03 ` Michael Ellerman
2010-12-08 10:18 ` Guillaume Dargaud
2010-12-08 13:45 ` Michael Ellerman
2010-12-08 15:52 ` Guillaume Dargaud
2010-12-09 0:22 ` Michael Ellerman
2010-12-10 16:21 ` Guillaume Dargaud
2010-12-12 21:46 ` Michael Ellerman
2010-12-08 19:20 ` Joachim Förster
2010-12-06 12:17 ` David Laight
2010-12-07 12:46 ` Guillaume Dargaud
2010-12-08 0:50 ` Michael Ellerman
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=4CF69421.10206@gate-nine.de \
--to=lists@gate-nine.de \
--cc=dargaud@lpsc.in2p3.fr \
--cc=linuxppc-dev@lists.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).