From: Vijay Nikam <vijay.t.nikam@gmail.com>
To: linuxppc-dev@ozlabs.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Interrupt sense value in device tree
Date: Tue, 24 Feb 2009 11:53:50 +0530 [thread overview]
Message-ID: <f234e2140902232223u799159feufcc237710dd62866@mail.gmail.com> (raw)
Hello,
I created a device node for gpio-controller for evaluation board
mpc83313erdb. I created the dtb and loaded on target.
But in dts at interrupts = <74 0x2> I set sense as Edge (sense== 2:
Edge, high-to-low change), when I load the driver module and checked
the entry in /proc/interrupts it shows the sense as 'Level' i.e. 8
(sense == 8: Level, low assertion) as follows;
74: 1 IPIC Level gpio
Following is gpio-controller device tree node;
gpio-controller@c00 {
#gpio-cells = <2>;
compatible = "fsl,mpc8313-gpio", "fsl,mpc8349-gpio";
reg = <0xc00 0x100>;
interrupts = <74 0x2>;
interrupt-parent = <&ipic>;
gpio-controller;
};
Could anyone please tell what could be the reason ? ? ? Am I missing
something ? ? ?
Kindly please acknowledge ... thank you ...
Kind Regards,
Vijay Nikam
##################### Start ############################
cat /proc/interrupts
CPU0
16: 162 IPIC Level serial
19: 43 IPIC Level i2c-mpc
20: 1 IPIC Level i2c-mpc
22: 2 IPIC Edge phy_interrupt
32: 0 IPIC Level enet_error
33: 765 IPIC Level enet_rx
34: 3 IPIC Level enet_tx
35: 0 IPIC Level enet_error
36: 0 IPIC Level enet_rx
37: 15 IPIC Level enet_tx
38: 0 IPIC Edge ehci_hcd:usb1
72: 0 IPIC Level gtm timer
74: 1 IPIC Level gpio
77: 51451 IPIC Level fsl-elbc
80: 0 IPIC Level pmc
BAD: 0
###################### END ############################
next reply other threads:[~2009-02-24 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 6:23 Vijay Nikam [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-24 4:19 Interrupt sense value in device tree Vijay Nikam
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=f234e2140902232223u799159feufcc237710dd62866@mail.gmail.com \
--to=vijay.t.nikam@gmail.com \
--cc=benh@kernel.crashing.org \
--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).