linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alan Mikhak <alan.mikhak@sifive.com>
To: ard.biesheuvel@linaro.org
Cc: Joao.Pinto@synopsys.com, graeme.gregory@linaro.org,
	marc.zyngier@arm.com, jingoohan1@gmail.com,
	leif.lindholm@linaro.org, linux-pci@vger.kernel.org,
	bhelgaas@google.com, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] pci: designware: add separate driver for the MSI part of the RC
Date: Fri, 14 Feb 2020 16:54:25 -0800	[thread overview]
Message-ID: <1581728065-5862-1-git-send-email-alan.mikhak@sifive.com> (raw)
In-Reply-To: <20170821192907.8695-3-ard.biesheuvel@linaro.org>

Hi..

What is the right approach for adding MSI support for the generic
Linux PCI host driver?

I came across this patch which seems to address a similar
situation. It seems to have been dropped in v3 of the patchset
with the explanation "drop MSI patch [for now], since it
turns out we may not need it".

[PATCH 2/3] pci: designware: add separate driver for the MSI part of the RC
https://lore.kernel.org/linux-pci/20170821192907.8695-3-ard.biesheuvel@linaro.org/

[PATCH v2 2/3] pci: designware: add separate driver for the MSI part of the RC
https://lore.kernel.org/linux-pci/20170824184321.19432-3-ard.biesheuvel@linaro.org/

[PATCH v3 0/2] pci: add support for firmware initialized designware RCs
https://lore.kernel.org/linux-pci/20170828180437.2646-1-ard.biesheuvel@linaro.org/


Regards,
Alan Mikhak

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-02-15  0:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 19:29 [PATCH 0/3] pci: add support for firmware initialized designware RCs Ard Biesheuvel
2017-08-21 19:29 ` [PATCH 1/3] pci: designware: add driver for DWC controller in ECAM shift mode Ard Biesheuvel
2017-08-24 16:24   ` kbuild test robot
2017-08-24 16:25   ` kbuild test robot
2017-08-21 19:29 ` [PATCH 2/3] pci: designware: add separate driver for the MSI part of the RC Ard Biesheuvel
2017-08-24 16:42   ` Bjorn Helgaas
2017-08-24 16:43     ` Ard Biesheuvel
2017-08-24 16:48   ` Robin Murphy
2017-08-24 16:50     ` Ard Biesheuvel
2020-02-15  0:54   ` Alan Mikhak [this message]
2020-02-15  9:35     ` Ard Biesheuvel
2020-02-15 10:36       ` Marc Zyngier
2020-02-18 19:09         ` Alan Mikhak
2020-02-19  8:11           ` Marc Zyngier
2020-02-19  8:17             ` Ard Biesheuvel
2020-02-19 20:24               ` Alan Mikhak
2020-02-19 21:06                 ` Ard Biesheuvel
2020-02-19 21:35                   ` Alan Mikhak
2017-08-21 19:29 ` [PATCH 3/3] dt-bindings: designware: add binding for Designware PCIe in ECAM mode Ard Biesheuvel
2017-08-24 16:46 ` [PATCH 0/3] pci: add support for firmware initialized designware RCs Bjorn Helgaas
2017-08-31 19:21   ` Ard Biesheuvel

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=1581728065-5862-1-git-send-email-alan.mikhak@sifive.com \
    --to=alan.mikhak@sifive.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=graeme.gregory@linaro.org \
    --cc=jingoohan1@gmail.com \
    --cc=leif.lindholm@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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).