From: Achal Verma <a-verma1@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Krzysztof Wilczy_ski <kw@linux.com>,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: <linux-omap@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Achal Verma <a-verma1@ti.com>
Subject: [PATCH 0/2] Advertise ARI related capabilities.
Date: Sun, 13 Aug 2023 02:14:53 +0530 [thread overview]
Message-ID: <20230812204455.479510-1-a-verma1@ti.com> (raw)
This series addresses the limitation and flaw which are occurring due to
ARI capability related bits not set correctly.
First patch addresses the issue of PCI_EXP_DEVCAP2_ARI being not set even
when J7 PCIe controller in RC mode supports ARI Forwarding.
Second patch related to the issue when PCIe controller is put in end point
mode, Next function field in ARI capability for last function stores
current_function+1 value, which is supposed to be zero to signal that
current function is the last one.
Achal Verma (1):
PCI: cadence: Advertise ARI Forwarding Supported
Jasko-EXT Wojciech (1):
PCI: cadence: Clear the ARI Capability Next Function Number of the
last function
drivers/pci/controller/cadence/pci-j721e.c | 4 ++++
.../pci/controller/cadence/pcie-cadence-ep.c | 14 +++++++++++++-
.../pci/controller/cadence/pcie-cadence-host.c | 7 +++++++
drivers/pci/controller/cadence/pcie-cadence.h | 18 ++++++++++++++++++
4 files changed, 42 insertions(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2023-08-12 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 20:44 Achal Verma [this message]
2023-08-12 20:44 ` [PATCH 1/2] PCI: cadence: Advertise ARI Forwarding Supported Achal Verma
2023-08-12 20:44 ` [PATCH 2/2] PCI: cadence: Clear the ARI Capability Next Function Number of the last function Achal Verma
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=20230812204455.479510-1-a-verma1@ti.com \
--to=a-verma1@ti.com \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®