Lines Matching full:interrupts

116 interrupts.
117 Most device drivers are always going to be executing low-level interrupts.
124 When executing high-level interrupts, the thread may only execute a limited
792 The same is true for other things like interrupts, event notifications,
1202 Interrupts are a central part of the role of device drivers and one of
1204 Interrupts come in different types: fixed, MSI, and MSI-X.
1207 For example, MSI and MSI-X interrupts are generally specific to PCI and
1210 needs to do is to discover what type of interrupts it supports with
1213 MSI-X, then MSI, and finally fixed interrupts, and try to allocate
1214 interrupts.
1216 Drivers first need to know how many interrupts that they require.
1219 To discover the number of interrupts available, the driver should call
1221 If there are sufficient interrupts, it can proceed to actually
1222 allocate the interrupts with
1224 When allocating interrupts, callers need to check to see how many
1225 interrupts the system actually gave them.
1256 require that all interrupts in a group be enabled and disabled at the
1261 Once that is called, interrupts that are generated by a device will be
1269 to manage, set up, and acknowledge interrupts.
1271 masking interrupts and are generally what should be used if there are
1272 times that you need to separately enable or disable interrupts such as
1275 When unwinding interrupts, one needs to work in the reverse order here.
1284 Only after that is done is it safe to then free the interrupts with a