You need to sign in or sign up before continuing.
  1. 09 1月, 2016 1 次提交
  2. 06 1月, 2016 1 次提交
  3. 10 12月, 2015 2 次提交
  4. 09 12月, 2015 1 次提交
  5. 08 12月, 2015 2 次提交
  6. 26 11月, 2015 1 次提交
  7. 03 11月, 2015 5 次提交
  8. 26 10月, 2015 1 次提交
  9. 24 10月, 2015 1 次提交
  10. 22 10月, 2015 1 次提交
  11. 16 10月, 2015 1 次提交
    • M
      Docs: dt: Add PCI MSI map bindings · b531566e
      Mark Rutland 提交于
      Currently msi-parent is used by a few bindings to describe the
      relationship between a PCI root complex and a single MSI controller, but
      this property does not have a generic binding document.
      
      Additionally, msi-parent is insufficient to describe more complex
      relationships between MSI controllers and devices under a root complex,
      where devices may be able to target multiple MSI controllers, or where
      MSI controllers use (non-probeable) sideband information to distinguish
      devices.
      
      This patch adds a generic binding for mapping PCI devices to MSI
      controllers. This document covers msi-parent, and a new msi-map property
      (specific to PCI*) which may be used to map devices (identified by their
      Requester ID) to sideband data for each MSI controller that they may
      target.
      Acked-by: NMarc Zyngier <marc.zyngier@arm.com>
      Acked-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NMark Rutland <mark.rutland@arm.com>
      Signed-off-by: NDavid Daney <david.daney@cavium.com>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      b531566e
  12. 10 10月, 2015 1 次提交
  13. 26 9月, 2015 1 次提交
  14. 25 9月, 2015 1 次提交
  15. 12 8月, 2015 1 次提交
  16. 06 6月, 2015 1 次提交
    • D
      PCI: xgene: Add APM X-Gene v1 PCIe MSI/MSIX termination driver · dcd19de3
      Duc Dang 提交于
      APM X-Gene v1 SoC supports its own implementation of MSI, which is not
      compliant to GIC V2M specification for MSI Termination.
      
      There is a single MSI block in X-Gene v1 SOC which serves all 5 PCIe ports.
      This MSI block supports 2048 MSI termination ports coalesced into 16
      physical HW IRQ lines and shared across all 5 PCIe ports.
      
      As there are only 16 HW IRQs to serve 2048 MSI vectors, to support
      set_affinity correctly for each MSI vectors, the 16 HW IRQs are statically
      allocated to 8 X-Gene v1 cores (2 HW IRQs for each cores).  To steer MSI
      interrupt to target CPU, MSI vector is moved around these HW IRQs lines.
      With this approach, the total MSI vectors this driver supports is reduced
      to 256.
      
      [bhelgaas: squash doc, driver, maintainer update]
      Signed-off-by: NDuc Dang <dhdang@apm.com>
      Signed-off-by: NTanmay Inamdar <tinamdar@apm.com>
      Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
      Reviewed-by: NMarc Zyngier <marc.zyngier@arm.com>
      dcd19de3
  17. 28 5月, 2015 1 次提交
  18. 09 4月, 2015 1 次提交
  19. 04 2月, 2015 1 次提交
    • P
      Documentation: DT bindings: add more Tegra chip compatible strings · 193c9d23
      Paul Walmsley 提交于
      Align compatible strings for several IP blocks present on Tegra chips
      with the latest doctrine from the DT maintainers:
      
      http://marc.info/?l=devicetree&m=142255654213019&w=2
      
      The primary objective here is to avoid checkpatch warnings, per:
      
      http://marc.info/?l=linux-tegra&m=142201349727836&w=2
      
      DT binding text files have been updated for the following IP blocks:
      
      - PCIe
      - SOR
      - SoC timers
      - AHB "gizmo"
      - APB_MISC
      - pinmux control
      - UART
      - PWM
      - I2C
      - SPI
      - RTC
      - PMC
      - eFuse
      - AHCI
      - HDA
      - XUSB_PADCTRL
      - SDHCI
      - SOC_THERM
      - AHUB
      - I2S
      - EHCI
      - USB PHY
      
      N.B. The nvidia,tegra20-timer compatible string is removed from the
      nvidia,tegra30-timer.txt documentation file because it's already
      mentioned in the nvidia,tegra20-timer.txt documentation file.
      
      This second version takes into account the following requests from
      Rob Herring <robherring2@gmail.com>:
      
      - Per-IP block patches have been combined into a single patch
      
      - Explicit documentation about which compatible strings are actually
        matched by the driver has been removed.  In its place is implicit
        documentation that loosely follows Rob's prescribed format:
      
        "Must contain '"nvidia,<chip>-pcie", "nvidia,tegra20-pcie"' where
         <chip> is tegra30, tegra132, ..." [...]  "You should attempt to
         document known values of <chip> if you use it"
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Alexandre Courbot <gnurou@gmail.com>
      Cc: Dylan Reid <dgreid@chromium.org>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Hans de Goede <hdegoede@redhat.com>
      Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
      Cc: Jingchang Lu <jingchang.lu@freescale.com>
      Cc: John Crispin <blogic@openwrt.org>
      Cc: Kumar Gala <galak@codeaurora.org>
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Mikko Perttunen <mperttunen@nvidia.com>
      Cc: Murali Karicheri <m-karicheri2@ti.com>
      Cc: Paul Walmsley <pwalmsley@nvidia.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Peter De Schrijver <pdeschrijver@nvidia.com>
      Cc: Peter Hurley <peter@hurleysoftware.com>
      Cc: Sean Paul <seanpaul@chromium.org>
      Cc: Stephen Warren <swarren@wwwdotorg.org>
      Cc: Takashi Iwai <tiwai@suse.de>
      Cc: Tejun Heo <tj@kernel.org>
      Cc: "Terje Bergström" <tbergstrom@nvidia.com>
      Cc: Thierry Reding <thierry.reding@gmail.com>
      Cc: Tuomas Tynkkynen <ttynkkynen@nvidia.com>
      Cc: Wolfram Sang <wsa@the-dreams.de>
      Cc: Zhang Rui <rui.zhang@intel.com>
      Cc: dri-devel@lists.freedesktop.org
      Cc: linux-i2c@vger.kernel.org
      Cc: linux-kernel@vger.kernel.org
      Cc: linux-pci@vger.kernel.org
      Cc: linux-pm@vger.kernel.org
      Cc: linux-pwm@vger.kernel.org
      Cc: linux-tegra@vger.kernel.org
      Acked-by: NEduardo Valentin <edubezval@gmail.com>
      Signed-off-by: NRob Herring <robh@kernel.org>
      193c9d23
  20. 29 1月, 2015 1 次提交
  21. 14 11月, 2014 2 次提交
  22. 02 10月, 2014 1 次提交
  23. 17 9月, 2014 3 次提交
  24. 16 9月, 2014 1 次提交
  25. 05 9月, 2014 2 次提交
    • L
      PCI: designware: Parse bus-range property from devicetree · 4f2ebe00
      Lucas Stach 提交于
      This allows to explicitly specify the covered bus numbers in the
      devicetree, which will come in handy once we see a SoC with more than one
      PCIe host controller instance.
      
      Previously the driver relied on the behavior of pci_scan_root_bus() to fill
      in a range of 0x00-0xff if no valid range was found.  We fall back to the
      same range if no valid DT entry was found to keep backwards compatibility,
      but now do it explicitly.
      
      [bhelgaas: use %pR in error message to avoid duplication]
      Signed-off-by: NLucas Stach <l.stach@pengutronix.de>
      Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
      Reviewed-by: NPratyush Anand <pratyush.anand@st.com>
      Acked-by: NMohit Kumar <mohit.kumar@st.com>
      4f2ebe00
    • M
      PCI: keystone: Add TI Keystone PCIe driver · 0c4ffcfe
      Murali Karicheri 提交于
      The Keystone PCIe controller is based on v3.65 version of the Designware
      h/w.  Main differences are:
      
          1. No ATU support
          2. Legacy and MSI IRQ functions are implemented in application register
             space
          3. MSI interrupts are multiplexed over 8 IRQ lines to the Host side.
      
      All of the application register space handing code is organized into
      pci-keystone-dw.c and the functions are called from pci-keystone.c to
      implement PCI controller driver.  Also add necessary DT documentation and
      update the MAINTAINERS file for the driver.
      
      [bhelgaas: spelling and whitespace fixes]
      Signed-off-by: NMurali Karicheri <m-karicheri2@ti.com>
      Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
      Acked-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      CC: Russell King <linux@arm.linux.org.uk>
      CC: Grant Likely <grant.likely@linaro.org>
      CC: Rob Herring <robh+dt@kernel.org>
      CC: Mohit Kumar <mohit.kumar@st.com>
      CC: Pratyush Anand <pratyush.anand@st.com>
      CC: Jingoo Han <jg1.han@samsung.com>
      CC: Richard Zhu <r65037@freescale.com>
      CC: Kishon Vijay Abraham I <kishon@ti.com>
      CC: Marek Vasut <marex@denx.de>
      CC: Arnd Bergmann <arnd@arndb.de>
      CC: Pawel Moll <pawel.moll@arm.com>
      CC: Mark Rutland <mark.rutland@arm.com>
      CC: Ian Campbell <ijc+devicetree@hellion.org.uk>
      CC: Kumar Gala <galak@codeaurora.org>
      CC: Randy Dunlap <rdunlap@infradead.org>
      CC: Grant Likely <grant.likely@linaro.org>
      0c4ffcfe
  26. 04 9月, 2014 2 次提交
    • S
      PCI: xilinx: Add Xilinx AXI PCIe Host Bridge IP driver · 8961def5
      Srikanth Thokala 提交于
      This is the driver for Xilinx AXI PCIe Host Bridge Soft IP.
      
      [bhelgaas: minor whitespace fixes]
      Signed-off-by: NSrikanth Thokala <sthokal@xilinx.com>
      Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      8961def5
    • A
      powerpc: fsl_pci: Add forced PCI Agent enumeration · 00406e87
      Aaron Sierra 提交于
      The following commit prevents the MPC8548E on the XPedite5200 PrPMC
      module from enumerating its PCI/PCI-X bus:
      
          powerpc/fsl-pci: use 'Header Type' to identify PCIE mode
      
      The previous patch prevents any Freescale PCI-X bridge from enumerating
      the bus, if it is hardware strapped into Agent mode.
      
      In PCI-X, the Host is responsible for driving the PCI-X initialization
      pattern to devices on the bus, so that they know whether to operate in
      conventional PCI or PCI-X mode as well as what the bus timing will be.
      For a PCI-X PrPMC, the pattern is driven by the mezzanine carrier it is
      installed onto. Therefore, PrPMCs are PCI-X Agents, but one per system
      may still enumerate the bus.
      
      This patch causes the device node of any PCI/PCI-X bridge strapped into
      Agent mode to be checked for the fsl,pci-agent-force-enum property. If
      the property is present in the node, the bridge will be allowed to
      enumerate the bus.
      
      Cc: Minghuan Lian <Minghuan.Lian@freescale.com>
      Signed-off-by: NAaron Sierra <asierra@xes-inc.com>
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      00406e87
  27. 26 8月, 2014 1 次提交
  28. 23 7月, 2014 2 次提交