From: Murali Karicheri <m-karicheri2@ti.com>
To: Joao Pinto <Joao.Pinto@synopsys.com>, <kishon@ti.com>,
<bhelgaas@google.com>, <jingoohan1@gmail.com>,
<marc.zyngier@arm.com>
Cc: <linux-pci@vger.kernel.org>
Subject: Re: [RFC] pci: adding new interrupt api to pcie-designware
Date: Mon, 15 May 2017 10:01:12 -0400 [thread overview]
Message-ID: <5919B4A8.2060604@ti.com> (raw)
In-Reply-To: <de48ca7f-149c-9c64-85b0-7e9fa66920cb@synopsys.com>
On 05/15/2017 07:13 AM, Joao Pinto wrote:
>
> Hi Murali,
>
> Às 5:21 PM de 5/12/2017, Murali Karicheri escreveu:
>> On 05/09/2017 08:33 AM, Joao Pinto wrote:
>>> This is a proposal for the update of the interrupt API in pcie-designware.
>>>
>>> *SoC specific drivers*
>>> All SoC specific drivers that use the common infrastructure (pci-qcom,
>>> pci-artpec6, pci-exynos, pci-imx6) were updated to be compatible.
>>> Other SoC specific drivers like pci-dra7, pci-armada8k, pci-hisi, pci-spear13xx
>>> and pci-layerscape will also work fine.
>>>
>>> *Work still to be done - need some inputs*
>>> The pci-keystone driver is the one that I would appreciate some opinions, since
>>> it uses the "old" dw_pcie_msi_chip. I think we have 3 options:
>>>
>>> a) Keep the old API + new API in pcie-designware just for pci-keystone to use
>>> the dw_pcie_msi_chip structure
>>> b) Move the old API from pcie-designware to pci-keystone for it to use the
>>> dw_pcie_msi_chip structure
>>> c) Adapt pci-keystone to use the new API also
>>>
>>> *Tests*
>>> I made tests with a PCI 4.80 Core IP, using pcie-designware-plat driver.
>>> I used an MSI-only Endpoint and a MSI/MSIX Endpoint and the APi adapted very
>>> well to the situation.
>>>
>>> Signed-off-by: Joao Pinto <jpinto@synopsys.com>
>>> ---
>>> drivers/pci/dwc/pci-exynos.c | 18 --
>>> drivers/pci/dwc/pci-imx6.c | 18 --
>>> drivers/pci/dwc/pcie-artpec6.c | 18 --
>>> drivers/pci/dwc/pcie-designware-host.c | 342 +++++++++++++++++----------------
>>> drivers/pci/dwc/pcie-designware-plat.c | 15 --
>>> drivers/pci/dwc/pcie-designware.h | 6 +-
>>> drivers/pci/dwc/pcie-qcom.c | 15 --
>>> 7 files changed, 179 insertions(+), 253 deletions(-)
>
> [...]
>
>>
>> What do you see the challenge in porting the PCI-Keystone driver to the new
>> interrupt API (option c)? I haven't had a chance to review your patches and recent
>> changes in Linux kernel for PCI as we are currently using v4.9 kernel for
>> our platforms. One key difference in the PCI Core used in Keystone SoC is that
>> the MSI is not implemented using standard registers as in newer PCI Designware
>> core. It uses application register space for MSI interrupts. Given that
>> is the case, do you see any issue in porting the driver to the new API?
>>
>> I should be able to test your patch on Keystone.
>>
>
> I don't see any issue in porting it, and I have sent a RFC patch-set in Friday
> including the porting of the keystone SoC driver. If you could test it with the
> new API it would be great, just to have a sanity check.
>
> A v2 of the RFC will be sent soon, so I would suggest for you to wait until v2
> is available, that way you could test with the latest.
>
> Thanks for the help,
> Joao
>
Ok. Will do
--
Murali Karicheri
Linux Kernel, Keystone
prev parent reply other threads:[~2017-05-15 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 12:33 [RFC] pci: adding new interrupt api to pcie-designware Joao Pinto
2017-05-10 17:00 ` Marc Zyngier
2017-05-11 9:17 ` Joao Pinto
2017-05-11 10:05 ` Marc Zyngier
2017-05-12 16:05 ` Murali Karicheri
2017-05-12 16:11 ` Marc Zyngier
2017-05-12 16:21 ` Murali Karicheri
2017-05-15 11:13 ` Joao Pinto
2017-05-15 14:01 ` Murali Karicheri [this message]
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=5919B4A8.2060604@ti.com \
--to=m-karicheri2@ti.com \
--cc=Joao.Pinto@synopsys.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=kishon@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.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).