From: Thierry Reding <thierry.reding@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Maen Suleiman <maen@marvell.com>,
Lior Amsalem <alior@marvell.com>
Subject: Re: [PATCHv3 10/11] arm: mvebu: indicate that this platform supports MSI
Date: Fri, 21 Jun 2013 12:28:54 +0200 [thread overview]
Message-ID: <20130621102853.GH12441@manwe> (raw)
In-Reply-To: <1371660979-21588-11-git-send-email-thomas.petazzoni@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On Wed, Jun 19, 2013 at 06:56:18PM +0200, Thomas Petazzoni wrote:
> Now that all the pieces are in place, we can adjust the
> mach-mvebu/Kconfig file to indicate that this platform supports MSIs.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> arch/arm/mach-mvebu/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
> index 9eb63d7..36951b1 100644
> --- a/arch/arm/mach-mvebu/Kconfig
> +++ b/arch/arm/mach-mvebu/Kconfig
> @@ -15,6 +15,7 @@ config ARCH_MVEBU
> select ARCH_REQUIRE_GPIOLIB
> select MIGHT_HAVE_PCI
> select PCI_QUIRKS if PCI
> + select ARCH_SUPPORTS_MSI if PCI
I think we can get rid of ARCH_SUPPORTS_MSI now. I actually wrote a
patch once to do that but haven't posted it yet. The reason is that
the new weak functions do the right thing if MSI isn't supported by
some architecture or platform.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-21 10:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 16:56 [PATCHv3 00/11] MSI support for Marvell EBU PCIe driver Thomas Petazzoni
2013-06-19 16:56 ` [PATCHv3 01/11] irqdomain: add irq_alloc_mapping() function Thomas Petazzoni
2013-06-21 7:19 ` Thomas Petazzoni
2013-06-19 16:56 ` [PATCHv3 02/11] pci: use weak functions for MSI arch-specific functions Thomas Petazzoni
2013-06-20 18:57 ` Thierry Reding
2013-06-21 6:33 ` Thomas Petazzoni
2013-06-25 1:52 ` Bjorn Helgaas
2013-06-25 9:55 ` Thomas Petazzoni
2013-06-25 16:20 ` Bjorn Helgaas
2013-06-25 16:44 ` Thomas Petazzoni
2013-06-25 16:54 ` Bjorn Helgaas
2013-06-19 16:56 ` [PATCHv3 03/11] PCI: Introduce new MSI chip infrastructure Thomas Petazzoni
2013-06-19 16:56 ` [PATCHv3 04/11] of: pci: add registry of MSI chips Thomas Petazzoni
2013-06-21 7:20 ` Thomas Petazzoni
2013-06-21 10:16 ` Thierry Reding
2013-06-19 16:56 ` [PATCHv3 05/11] irqchip: armada-370-xp: properly request resources Thomas Petazzoni
2013-06-21 7:22 ` Thomas Petazzoni
2013-06-19 16:56 ` [PATCHv3 06/11] irqchip: armada-370-xp: implement MSI support Thomas Petazzoni
2013-06-19 16:56 ` [PATCHv3 07/11] arm: pci: add ->add_bus() and ->remove_bus() hooks to hw_pci Thomas Petazzoni
2013-06-21 7:23 ` Thomas Petazzoni
2013-06-21 10:23 ` Thierry Reding
2013-06-19 16:56 ` [PATCHv3 08/11] arm: mvebu: the MPIC now provides MSI controller features Thomas Petazzoni
2013-06-21 10:24 ` Thierry Reding
2013-06-19 16:56 ` [PATCHv3 09/11] pci: mvebu: add support for MSI Thomas Petazzoni
2013-06-21 10:25 ` Thierry Reding
2013-06-25 21:20 ` Bjorn Helgaas
2013-06-19 16:56 ` [PATCHv3 10/11] arm: mvebu: indicate that this platform supports MSI Thomas Petazzoni
2013-06-21 10:28 ` Thierry Reding [this message]
2013-06-19 16:56 ` [PATCHv3 11/11] arm: mvebu: link PCIe controllers to the MSI controller Thomas Petazzoni
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=20130621102853.GH12441@manwe \
--to=thierry.reding@gmail.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=grant.likely@secretlab.ca \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=maen@marvell.com \
--cc=rob.herring@calxeda.com \
--cc=tglx@linutronix.de \
--cc=thomas.petazzoni@free-electrons.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).