From: sarkar@g.clemson.edu (Subhra S. Sarkar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: On creation of irq_desc and irq_data.
Date: Fri, 21 Jun 2013 02:49:21 +0000 (UTC) [thread overview]
Message-ID: <loom.20130621T035346-400@post.gmane.org> (raw)
In-Reply-To: CAM2a4uw5akKiQJXH3QKdyWoR1Y=4FkD=4dR1z56GJbM7eZ6DrQ@mail.gmail.com
mind entropy <mindentropy <at> gmail.com> writes:
>
> > Hi,
> >
> > I am reading through mini2440 code. I am going through the init_irq
> > (http://lxr.free-electrons.com/source/arch/arm/mach-s3c24xx/mach-
mini2440.c#L689)
> > code. In it (http://lxr.free-electrons.com/source/arch/arm/mach-
s3c24xx/irq.c#L446)
> > there is irq_domain_add_legacy(..) which references irq_desc and
> > irq_data. I am not sure where these descriptors are created? In the
> > irq_domain_add_legacy there is a lookup for irq_data from the number.
> > Could someone tell where these descriptors are created?
> >
> > Thanks.
>
> I think it is statically created here
> https://github.com/torvalds/linux/blob/master/kernel/irq/irqdesc.c#L243
> and the initialization happens in early_irq_init(..) here
> https://github.com/torvalds/linux/blob/master/kernel/irq/irqdesc.c#L251.
>
> Please correct me if I am wrong.
>
> Thanks.
>
Within the function definition for irq_domain_add_legacy (), a pointer to
the structure irq_data is obtained [$KERN_HOME/kernel/irq/irqdomain.c, L:
232] by returning from function irq_get_irq_data()
[$KERN_HOME/kernel/irq/chip.c, L: 147]. Function irq_get_irq_data() in turn
retrieves the pointer to corresponding irq_desc structure from array of the
same type in $KERN_HOME/kernel/irq/irqdesc.c, L: 243. So, you're correct,
IMHO.
~Sarkar
next prev parent reply other threads:[~2013-06-21 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 18:15 On creation of irq_desc and irq_data mind entropy
2013-06-21 2:49 ` Subhra S. Sarkar [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-20 10:39 mind entropy
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=loom.20130621T035346-400@post.gmane.org \
--to=sarkar@g.clemson.edu \
--cc=kernelnewbies@lists.kernelnewbies.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).