Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 03 11月, 2014 1 次提交
    • S
      s390/pci: improve irq number check for msix · b19148f6
      由 Sebastian Ott 提交于 
      s390s arch_setup_msi_irqs function ensures that we don't return with
more irqs than the PCI architecture allows and that a single PCI
function doesn't consume more irqs than the kernel is configured for.

At least the last check doesn't help much and should take the sum of
all irqs into account. Since that's already done by irq_alloc_desc
we can remove this check.

As for the first check we should use the value provided by the
firmware which can be less than what the PCI architecture allows.
Signed-off-by: NSebastian Ott <sebott@linux.vnet.ibm.com>
Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      b19148f6
  3. 22 7月, 2014 1 次提交
  5. 16 7月, 2014 1 次提交
    • Y
      s390/MSI: Use standard mask and unmask funtions · 8fb878c5
      由 Yijing Wang 提交于 
      MSI irqchip in s390 has its own mask and unmask MSI irq
functions, zpci_enable_irq() and zpci_disable_irq().
They mask and unmask MSI irq in standard ways, no arch
special. MSI driver provides two global standard functions
mask_msi_irq() and unmask_msi_irq(). Local zpci_enable_irq()
and zpci_disable_irq() are almost the same as the standard
two. the difference is local mask/unmask functions
read the mask status before mask and unmask everytime.
Then change the value and rewrite to hardware. In standard
functions, save the mask status after mask and unmask msi
irq, and use the cached status to change the mask status.
When we mask or unmask a MSI irq, we always cache its
mask status except we know need not to cache it, like in
pci_msi_shutdown. So use the standard functions to replace
the local is safe.
Signed-off-by: NYijing Wang <wangyijing@huawei.com>
[sebott: fixed inverted function pointers]
Signed-off-by: NSebastian Ott <sebott@linux.vnet.ibm.com>
Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      8fb878c5
  7. 23 5月, 2014 1 次提交
  9. 20 5月, 2014 1 次提交
  11. 16 5月, 2014 1 次提交
  13. 20 3月, 2014 1 次提交
    • B
      s390/PCI: Use generic pci_enable_resources() · d7533232
      由 Bjorn Helgaas 提交于 
      The generic pci_enable_resources() does essentially the same thing as the
code in the s390 version of pcibios_enable_device().

There are differences, but I don't think any of them are a problem.  The
generic code:

  - Checks everything up to PCI_NUM_RESOURCES, not PCI_BAR_COUNT (6), so
    we'll now check the ROM resource, IOV resources, and bridge windows.

  - Checks for res->flags & IORESOURCE_UNSET.  The s390 code never sets
    IORESOURCE_UNSET, so this isn't a problem.

  - Checks res->parent.  The s390 pcibios_add_device() calls
    pci_claim_resource() on all BARs (except ROM, IOV, and bridge windows)
    so this isn't a problem either.
Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
Acked-by: NSebastian Ott <sebott@linux.vnet.ibm.com>
      d7533232
  15. 21 12月, 2013 2 次提交
  17. 16 12月, 2013 2 次提交
  19. 15 11月, 2013 2 次提交
  21. 24 10月, 2013 3 次提交
  23. 30 8月, 2013 5 次提交
  25. 22 8月, 2013 3 次提交
  27. 27 6月, 2013 4 次提交
  29. 10 6月, 2013 1 次提交
  31. 26 4月, 2013 1 次提交
  33. 17 4月, 2013 9 次提交
  35. 14 2月, 2013 1 次提交