linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@bootlin.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/6] PCI: aardvark: misc fixes and improvements
Date: Fri,  6 Apr 2018 16:55:30 +0200	[thread overview]
Message-ID: <20180406145536.19637-1-thomas.petazzoni@bootlin.com> (raw)

Bjorn, Lorenzo,

This patch series brings a number of improvements to the aardvark
PCIe.

Changes since v3:

 - Introduced advk_pcie_valid_device() late in the series, so that the
   patch fixing the logic in the PCIe configuration space read/write
   function does not depend on it. This is needed as we don't want the
   advk_pcie_valid_device() addition to go to stable.

Changes since v2:

 - Rebased on v4.16-rc7

 - Dropped the patches disabling L0S and aligning the MPS between RC
   and EP, since we are working on a different solution, implementing
   a proper root port. Therefore, this patch series only has the
   (hopefully) non-controversial changes.

 - Add a patch (PATCH 1) that factorizes the logic to decide if the
   target of a configuration space access is a valid device or not
   into a advk_pcie_valid_device() helper, and adjust PATCH 2
   accordingly.

 - Drop unused PCIE_BDF macro in PATCH 3.

Best regards,

Thomas Petazzoni



Evan Wang (2):
  PCI: aardvark: Fix PCIe Max Read Request Size setting
  PCI: aardvark: Remove PCIe outbound window configuration

Thomas Petazzoni (1):
  PCI: aardvark: Introduce an advk_pcie_valid_device() helper

Victor Gu (3):
  PCI: aardvark: Fix logic in advk_pcie_{rd,wr}_conf()
  PCI: aardvark: Set PIO_ADDR_LS correctly in advk_pcie_rd_conf()
  PCI: aardvark: Use ISR1 instead of ISR0 interrupt in legacy irq mode

 drivers/pci/host/pci-aardvark.c | 117 ++++++++++++++--------------------------
 1 file changed, 39 insertions(+), 78 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-04-06 14:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 14:55 Thomas Petazzoni [this message]
2018-04-06 14:55 ` [PATCH v4 1/6] PCI: aardvark: Fix logic in advk_pcie_{rd,wr}_conf() Thomas Petazzoni
2018-04-06 14:55 ` [PATCH v4 2/6] PCI: aardvark: Set PIO_ADDR_LS correctly in advk_pcie_rd_conf() Thomas Petazzoni
2018-04-06 14:55 ` [PATCH v4 3/6] PCI: aardvark: Use ISR1 instead of ISR0 interrupt in legacy irq mode Thomas Petazzoni
2018-04-06 14:55 ` [PATCH v4 4/6] PCI: aardvark: Fix PCIe Max Read Request Size setting Thomas Petazzoni
2018-04-06 14:55 ` [PATCH v4 5/6] PCI: aardvark: Introduce an advk_pcie_valid_device() helper Thomas Petazzoni
2018-06-27 16:51   ` Lorenzo Pieralisi
2018-06-27 17:18     ` Lorenzo Pieralisi
2018-06-27 18:52       ` Thomas Petazzoni
2018-04-06 14:55 ` [PATCH v4 6/6] PCI: aardvark: Remove PCIe outbound window configuration Thomas Petazzoni
2018-04-09 16:23 ` [PATCH v4 0/6] PCI: aardvark: misc fixes and improvements Lorenzo Pieralisi
2018-04-09 18:54   ` Thomas Petazzoni
2018-04-18 13:02     ` Lorenzo Pieralisi
2018-04-18 13:49       ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2018-03-29  8:39 Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180406145536.19637-1-thomas.petazzoni@bootlin.com \
    --to=thomas.petazzoni@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).