linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 02/11] pci: use weak functions for MSI arch-specific functions
Date: Thu, 20 Jun 2013 20:57:08 +0200	[thread overview]
Message-ID: <20130620185707.GA8888@mithrandir> (raw)
In-Reply-To: <1371660979-21588-3-git-send-email-thomas.petazzoni@free-electrons.com>

On Wed, Jun 19, 2013 at 06:56:10PM +0200, Thomas Petazzoni wrote:
[...]
> diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
> index 2c10752..4bc0c8f 100644
> --- a/drivers/pci/msi.c
> +++ b/drivers/pci/msi.c
> @@ -30,19 +30,35 @@ static int pci_msi_enable = 1;
>  
>  /* Arch hooks */
>  
> -#ifndef arch_msi_check_device
> -int arch_msi_check_device(struct pci_dev *dev, int nvec, int type)
> +int default_setup_msi_irq(struct pci_dev *dev, struct msi_desc *desc)
> +{
> +	return -EINVAL;
> +}
> +
> +int __weak arch_setup_msi_irq(struct pci_dev *dev, struct msi_desc *desc)
> +{
> +	return default_setup_msi_irq(dev, desc);
> +}
> +
> +void default_teardown_msi_irq(unsigned int irq)
> +{
> +}
> +
> +void __weak arch_teardown_msi_irq(unsigned int irq)
> +{
> +	return default_teardown_msi_irq(irq);
> +}
> +
> +int default_msi_check_device(struct pci_dev *dev, int nvec, int type)
>  {
>  	return 0;
>  }
> -#endif

I don't think keeping the default_*() for these three is necessary,
given that they don't do anything and therefore no architecture is
likely to call them when overriding.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130620/d0f26728/attachment.sig>

  reply	other threads:[~2013-06-20 18:57 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 [this message]
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
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=20130620185707.GA8888@mithrandir \
    --to=thierry.reding@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).