summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorBenjamin Rood <benjaminjrood@gmail.com>2015-10-30 10:53:31 -0400
committerMartin K. Petersen <martin.petersen@oracle.com>2015-11-02 23:41:13 -0500
commitc913df3f3d6f7f5e5ed845e2786b0fc98a41482f (patch)
tree77853d04ac0b614607ba052bc6f037d4db16bda9 /lib
parentb650a8806e1ba0315fbeda8b45c9e53d73abbb6f (diff)
downloadop-kernel-dev-c913df3f3d6f7f5e5ed845e2786b0fc98a41482f.zip
op-kernel-dev-c913df3f3d6f7f5e5ed845e2786b0fc98a41482f.tar.gz
pm80xx: avoid a panic if MSI(X) interrupts are disabled
If MSI(X) interrupts are disabled via the kernel command line (pci=nomsi), the pm8001 driver will kernel panic because it does not detect that MSI interrupts are disabled and will soldier on and attempt to configure MSI interrupts anyways. This leads to a kernel panic, most likely because a required data structure is not available down the line. Using the pci_msi_enabled() function in order to detect if MSI interrupts are enabled before configuring them resolves this issue and avoids a kernel panic when the module is loaded. Additionally, the irq_vector structure must be initialized when legacy interrupts are being used otherwise legacy interrupts will simply not function and result in another panic. Signed-off-by: Benjamin Rood <brood@attotech.com> Reviewed-by: Jack Wang <jinpu.wang@profitbricks.com> Reviewed-by: Hannes Reinecke <hare@suse.de> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud