From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: "Marek Behún" <kabel@kernel.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, pali@kernel.org
Subject: Re: [PATCH 00/13] PCI: aardvark controller fixes
Date: Mon, 4 Oct 2021 10:53:51 +0100 [thread overview]
Message-ID: <20211004095351.GB22827@lpieralisi> (raw)
In-Reply-To: <20211001195856.10081-1-kabel@kernel.org>
On Fri, Oct 01, 2021 at 09:58:43PM +0200, Marek Behún wrote:
> Hi Lorenzo,
>
> this series fixes some issues with the Aardvark PCIe controller driver.
>
> Most of them are small changes. Patch 11 has a rather long commit message
> since it explains how the bugs were introduced from multiple misleading
> names and comments of some registers.
>
> We have another 56 fixes for aardvark, but last time nobody wanted to
> review such a large series, so we are now trying in smaller batches.
>
> It would be great if you could find time to review, since we would like
> this to land in 5.16. Preferably we would like to send another batch for
> 5.16, but we will see how fast this one goes
>
> Marek & Pali
OK, so what's the overlap between this series and:
https://patchwork.kernel.org/user/todo/linux-pci/?series=506773
https://patchwork.kernel.org/user/todo/linux-pci/?series=507035
I need to keep track of reviews in the series above and make
sure they are reflected into *this* series if some of the
patches overlap or they are a rework.
Please let me know, thank you.
Lorenzo
> Marek Behún (2):
> PCI: aardvark: Don't spam about PIO Response Status
> PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
>
> Pali Rohár (11):
> PCI: Add PCI_EXP_DEVCTL_PAYLOAD_* macros
> PCI: aardvark: Fix PCIe Max Payload Size setting
> PCI: aardvark: Fix preserving PCI_EXP_RTCTL_CRSSVE flag on emulated
> bridge
> PCI: aardvark: Fix configuring Reference clock
> PCI: aardvark: Do not clear status bits of masked interrupts
> PCI: aardvark: Do not unmask unused interrupts
> PCI: aardvark: Implement re-issuing config requests on CRS response
> PCI: aardvark: Simplify initialization of rootcap on virtual bridge
> PCI: aardvark: Fix link training
> PCI: aardvark: Fix checking for link up via LTSSM state
> PCI: aardvark: Fix reporting Data Link Layer Link Active
>
> drivers/pci/controller/pci-aardvark.c | 364 +++++++++++++++-----------
> include/uapi/linux/pci_regs.h | 6 +
> 2 files changed, 212 insertions(+), 158 deletions(-)
>
> --
> 2.32.0
>
next prev parent reply other threads:[~2021-10-04 9:53 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 19:58 [PATCH 00/13] PCI: aardvark controller fixes Marek Behún
2021-10-01 19:58 ` [PATCH 01/13] PCI: Add PCI_EXP_DEVCTL_PAYLOAD_* macros Marek Behún
2021-10-02 16:05 ` Bjorn Helgaas
2021-10-04 8:43 ` Lorenzo Pieralisi
2021-10-04 9:32 ` Marek Behún
2021-10-04 9:35 ` Lorenzo Pieralisi
2021-10-01 19:58 ` [PATCH 02/13] PCI: aardvark: Fix PCIe Max Payload Size setting Marek Behún
2021-10-03 17:44 ` Marek Behún
2021-10-01 19:58 ` [PATCH 03/13] PCI: aardvark: Don't spam about PIO Response Status Marek Behún
2021-10-01 19:58 ` [PATCH 04/13] PCI: aardvark: Fix preserving PCI_EXP_RTCTL_CRSSVE flag on emulated bridge Marek Behún
2021-10-01 19:58 ` [PATCH 05/13] PCI: aardvark: Fix configuring Reference clock Marek Behún
2021-10-01 19:58 ` [PATCH 06/13] PCI: aardvark: Do not clear status bits of masked interrupts Marek Behún
2021-10-04 14:06 ` Lorenzo Pieralisi
2021-10-04 15:18 ` Marek Behún
2021-10-04 15:31 ` Marc Zyngier
2021-10-05 12:13 ` Marek Behún
2021-10-05 12:42 ` Marc Zyngier
2021-10-05 13:15 ` Pali Rohár
2021-10-05 15:42 ` Marc Zyngier
2021-10-05 18:48 ` Pali Rohár
2021-10-05 16:04 ` Lorenzo Pieralisi
2021-10-01 19:58 ` [PATCH 07/13] PCI: aardvark: Do not unmask unused interrupts Marek Behún
2021-10-01 19:58 ` [PATCH 08/13] PCI: aardvark: Deduplicate code in advk_pcie_rd_conf() Marek Behún
2021-10-01 19:58 ` [PATCH 09/13] PCI: aardvark: Implement re-issuing config requests on CRS response Marek Behún
2021-10-02 16:35 ` Bjorn Helgaas
2021-10-04 7:21 ` Marek Behún
2021-10-04 8:53 ` Lorenzo Pieralisi
2021-10-04 10:19 ` Marek Behún
2021-10-05 19:28 ` Bjorn Helgaas
2021-10-05 22:45 ` Marek Behún
2021-10-11 18:15 ` Usage of PCBIOS_* macros (Was: Re: [PATCH 09/13] PCI: aardvark: Implement re-issuing config requests on CRS response) Pali Rohár
2021-10-11 20:58 ` Bjorn Helgaas
2021-10-06 16:29 ` [PATCH 09/13] PCI: aardvark: Implement re-issuing config requests on CRS response Lorenzo Pieralisi
2021-10-06 20:13 ` Bjorn Helgaas
2021-10-07 11:51 ` Lorenzo Pieralisi
2021-10-07 12:36 ` Marek Behún
2021-10-07 19:25 ` Bjorn Helgaas
2021-10-01 19:58 ` [PATCH 10/13] PCI: aardvark: Simplify initialization of rootcap on virtual bridge Marek Behún
2021-10-04 9:44 ` Lorenzo Pieralisi
2021-10-04 9:56 ` Marek Behún
2021-10-04 10:10 ` Lorenzo Pieralisi
2021-10-01 19:58 ` [PATCH 11/13] PCI: aardvark: Fix link training Marek Behún
2021-10-01 19:58 ` [PATCH 12/13] PCI: aardvark: Fix checking for link up via LTSSM state Marek Behún
2021-10-04 13:35 ` Lorenzo Pieralisi
2021-10-01 19:58 ` [PATCH 13/13] PCI: aardvark: Fix reporting Data Link Layer Link Active Marek Behún
2021-10-04 9:53 ` Lorenzo Pieralisi [this message]
2021-10-04 10:40 ` [PATCH 00/13] PCI: aardvark controller fixes Marek Behún
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=20211004095351.GB22827@lpieralisi \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=kabel@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pali@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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).