1. 28 1月, 2016 1 次提交
  2. 07 1月, 2016 1 次提交
    • R
      PCI: iproc: Add iProc PCIe MSI support · 3bc2b234
      Ray Jui 提交于
      Add PCIe MSI support for both PAXB and PAXC interfaces on all iProc-based
      platforms.
      
      The iProc PCIe MSI support deploys an event queue-based implementation.
      Each event queue is serviced by a GIC interrupt and can support up to 64
      MSI vectors.  Host memory is allocated for the event queues, and each event
      queue consists of 64 word-sized entries.  MSI data is written to the lower
      16-bit of each entry, whereas the upper 16-bit of the entry is reserved for
      the controller for internal processing.
      
      Each event queue is tracked by a head pointer and tail pointer.  Head
      pointer indicates the next entry in the event queue to be processed by
      the driver and is updated by the driver after processing is done.
      The controller uses the tail pointer as the next MSI data insertion
      point.  The controller ensures MSI data is flushed to host memory before
      updating the tail pointer and then triggering the interrupt.
      
      MSI IRQ affinity is supported by evenly distributing the interrupts to each
      CPU core.  MSI vector is moved from one GIC interrupt to another in order
      to steer to the target CPU.
      
      Therefore, the actual number of supported MSI vectors is:
      
        M * 64 / N
      
      where M denotes the number of GIC interrupts (event queues), and N denotes
      the number of CPU cores.
      
      This iProc event queue-based MSI support should not be used with newer
      platforms with integrated MSI support in the GIC (e.g., giv2m or
      gicv3-its).
      
      [bhelgaas: fold in Kconfig fixes from Arnd Bergmann <arnd@arndb.de>]
      Signed-off-by: NRay Jui <rjui@broadcom.com>
      Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
      Reviewed-by: NAnup Patel <anup.patel@broadcom.com>
      Reviewed-by: NVikram Prakash <vikramp@broadcom.com>
      Reviewed-by: NScott Branden <sbranden@broadcom.com>
      Reviewed-by: NMarc Zyngier <marc.zyngier@arm.com>
      3bc2b234
  3. 08 12月, 2015 1 次提交
    • R
      PCI: iproc: Add PAXC interface support · 943ebae7
      Ray Jui 提交于
      Traditionally, all iProc PCIe root complexes use PAXB-based wrapper, with
      an integrated on-chip Serdes to support external endpoint devices.  On
      newer iProc platforms, a PAXC-based wrapper is introduced, for connection
      with internally emulated PCIe endpoint devices in the ASIC.
      
      Add support for PAXC-based iProc PCIe root complex in the iProc PCIe core
      driver.  This change factors out common logic between PAXB and PAXC, and
      uses tables to store register offsets that are different between PAXB and
      PAXC.  This allows the driver to be scaled to support subsequent PAXC
      revisions in the future.
      Signed-off-by: NRay Jui <rjui@broadcom.com>
      Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
      Reviewed-by: NScott Branden <sbranden@broadcom.com>
      943ebae7
  4. 01 12月, 2015 1 次提交
  5. 23 10月, 2015 1 次提交
  6. 16 10月, 2015 1 次提交
  7. 26 9月, 2015 3 次提交
  8. 30 7月, 2015 1 次提交
  9. 23 7月, 2015 1 次提交
    • R
      PCI: iproc: Add arm64 support · 8d9bfe37
      Ray Jui 提交于
      Add arm64 support to the iProc PCIe driver.
      
      Note that on arm32, bus->sysdata points to the arm32-specific pci_sys_data
      struct, and pci_sys_data.private_data contains the iproc_pcie pointer.
      For arm64, there's nothing corresponding to pci_sys_data, so we keep the
      iproc_pcie pointer directly in bus->sysdata.
      
      In addition, arm64 does IRQ mapping in pcibios_add_device(), so it doesn't
      need pci_fixup_irqs() as arm32 does.
      Signed-off-by: NRay Jui <rjui@broadcom.com>
      Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
      Reviewed-by: NScott Branden <sbranden@broadcom.com>
      8d9bfe37
  10. 15 7月, 2015 1 次提交
  11. 28 5月, 2015 1 次提交
  12. 20 5月, 2015 1 次提交
  13. 09 4月, 2015 1 次提交