Summary of Linux Device Drivers (6): 2. Share the interrupt number

Cu homepage comment fh265> blog, Weibo, album, personal center, friend message [exit] Comment

Announcement: remembering that the Dennis Ritchie event is about to kick off! Xiao Bai's blog-improve yourself and share others

Xiaoyun.blog.chinaunix.net

Good women can not share. Good technologies must be shared! Home Page | blog directory | album | blog circle | about me | message personal information diytvgy Weibo Forum sends a note to greet and add friends

• Blog access: 74424
• Number of blog posts: 42
• Blog credit: 687
• Blog grade: Lieutenant Colonel
• Popularity: 4
• Registration Time: 18:55:26

Document category all blog posts (42)Linux Kernel related knowledge (1) gossip (3) Linux kernel and Device Driver (34) ubuntu (2) unclassified blog (2) subscribe to my blog

Friend

• Tekkama

• Little Abbe

• Luozhiy

• Knivo

• Embedtek

• Sillybo

• Wang2kk

• Embedded in Kai

• Send_li

• Cu Guan fangbo

• Songtao

• Lxhhust

Recent visits

• Fh265
  1 hour ago

• Shenhai
  October 30

• A275532
  October 14

• Knivo
  October 13

• 
  October 13

• Lxr215
  October 10

• Luozhiy
  October 9

• Chafe
  October 8

• Mournju
  October 7

• Zotozo
  October 7

• High_way
  October 7

• Wangxin
  October 4

Font size: Big medium small blog Linux Device Driver Summary (6): 2. Share interrupt number ()
Category: 6 interruptions

Summary of Linux Device Drivers (6): 2. Share the interrupt number

Bytes

The previous section describes how to call the request_irq () interface to match the interrupt number with the interrupt processing function. However, sometimes, if the interrupt of the buttons on the Development Board has been interrupted by another driver registration, and now I want to register the interrupt again, in this case, an interrupt number corresponds to more than one interrupt function. Note: This is different from the shared interrupt on the hardware. It means that when an interrupt signal comes, multiple interrupt handlers can be called upon the arrival of an interrupt based on the operating system, it has nothing to do with hardware.

The following describes the error code.

Bytes