From: Kishon Vijay Abraham I <kishon@ti.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Xiaowei Bao <xiaowei.bao@nxp.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Andrew Murray <andrew.murray@arm.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Jingoo Han <jingoohan1@gmail.com>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/4] Redesign MSI-X support in PCIe Endpoint Core
Date: Thu, 9 Jan 2020 15:49:17 +0530 [thread overview]
Message-ID: <a971c0b1-ed66-fd4c-5a1d-7aef9d410866@ti.com> (raw)
In-Reply-To: <20191211224636.GA122332@google.com>
Hi,
On 12/12/19 4:16 AM, Bjorn Helgaas wrote:
> On Wed, Dec 11, 2019 at 06:16:04PM +0530, Kishon Vijay Abraham I wrote:
>> Existing MSI-X support in Endpoint core has limitations:
>> 1) MSIX table (which is mapped to a BAR) is not allocated by
>> anyone. Ideally this should be allocated by endpoint
>> function driver.
>> 2) Endpoint controller can choose any random BARs for MSIX
>> table (irrespective of whether the endpoint function driver
>> has allocated memory for it or not)
>>
>> In order to avoid these limitations, pci_epc_set_msix() is
>> modified to include BAR Indicator register (BIR) configuration
>> and MSIX table offset as arguments. This series also fixed MSIX
>> support in dwc driver and add MSI-X support in Cadence PCIe driver.
>>
>> The previous version of Cadence EP MSI-X support is @ [1].
>> This series is created on top of [2]
>>
>> [1] -> https://patchwork.ozlabs.org/patch/971160/
>> [2] -> http://lore.kernel.org/r/20191209092147.22901-1-kishon@ti.com
>>
>> Alan Douglas (1):
>> PCI: cadence: Add MSI-X support to Endpoint driver
>>
>> Kishon Vijay Abraham I (3):
>> PCI: endpoint: Fix ->set_msix() to take BIR and offset as arguments
>> PCI: dwc: Fix dw_pcie_ep_raise_msix_irq() to get correct MSIX table
>> address
>> PCI: keystone: Add AM654 PCIe Endpoint to raise MSIX interrupt
>
> Trivial nits:
>
> - There's a mix of "MSI-X" and "MSIX" in the subjects, commit logs,
> and comments. I prefer "MSI-X" to match usage in the spec.
>
> - "Fixes:" tags need not include "commit". It doesn't *hurt*
> anything, but it takes up space that could be used for the
> subject.
>
> - Commit references typically use a 12-char SHA1. Again, doesn't
> hurt anything.
I'll fix all this in my next revision.
Xiaowei, Gustavo,
The issues we discussed in [1] should be fixed with this series. Can
you help test this in your platforms?
[1] -> https://lkml.org/lkml/2019/11/6/678
Thanks
Kishon
>
next prev parent reply other threads:[~2020-01-09 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 12:46 Kishon Vijay Abraham I
2019-12-11 12:46 ` [PATCH 1/4] PCI: endpoint: Fix ->set_msix() to take BIR and offset as arguments Kishon Vijay Abraham I
2019-12-11 12:46 ` [PATCH 2/4] PCI: dwc: Fix dw_pcie_ep_raise_msix_irq() to get correct MSIX table address Kishon Vijay Abraham I
2019-12-11 12:46 ` [PATCH 3/4] PCI: keystone: Allow AM654 PCIe Endpoint to raise MSIX interrupt Kishon Vijay Abraham I
2019-12-11 12:46 ` [PATCH 4/4] PCI: cadence: Add MSI-X support to Endpoint driver Kishon Vijay Abraham I
2020-01-23 22:10 ` Ramon Fried
2019-12-11 22:46 ` [PATCH 0/4] Redesign MSI-X support in PCIe Endpoint Core Bjorn Helgaas
2020-01-09 10:19 ` Kishon Vijay Abraham I [this message]
2020-01-09 10:20 ` Xiaowei Bao
2020-01-09 10:33 ` Gustavo Pimentel
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=a971c0b1-ed66-fd4c-5a1d-7aef9d410866@ti.com \
--to=kishon@ti.com \
--cc=andrew.murray@arm.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=helgaas@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=m-karicheri2@ti.com \
--cc=xiaowei.bao@nxp.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®