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 04/11] of: pci: add registry of MSI chips
Date: Fri, 21 Jun 2013 12:16:41 +0200	[thread overview]
Message-ID: <20130621101640.GD12441@manwe> (raw)
In-Reply-To: <1371660979-21588-5-git-send-email-thomas.petazzoni@free-electrons.com>

On Wed, Jun 19, 2013 at 06:56:12PM +0200, Thomas Petazzoni wrote:
> This commit adds a very basic registry of msi_chip structures, so that
> an IRQ controller driver can register an msi_chip, and a PCIe host
> controller can find it, based on a 'struct device_node'.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
>  drivers/of/of_pci.c    | 22 ++++++++++++++++++++++
>  include/linux/msi.h    |  2 ++
>  include/linux/of_pci.h |  4 ++++
>  3 files changed, 28 insertions(+)
> 
> diff --git a/drivers/of/of_pci.c b/drivers/of/of_pci.c
> index 42c687a..ca12db8 100644
> --- a/drivers/of/of_pci.c
> +++ b/drivers/of/of_pci.c
> @@ -89,3 +89,25 @@ int of_pci_parse_bus_range(struct device_node *node, struct resource *res)
>  	return 0;
>  }
>  EXPORT_SYMBOL_GPL(of_pci_parse_bus_range);
> +
> +static LIST_HEAD(msi_chip_list);
> +static DEFINE_MUTEX(msi_chip_mutex);

Should all of this code perhaps be conditionalized by an #ifdef PCI_MSI?

> +
> +void of_msi_chip_add(struct msi_chip *chip)
> +{
> +	mutex_lock(&msi_chip_mutex);
> +	list_add(&chip->link, &msi_chip_list);
> +	mutex_unlock(&msi_chip_mutex);
> +}

Since eventually we may want to use these functions from modules, maybe
they should be exported?

Also isn't this missing an of_msi_chip_remove() counterpart?

> +struct msi_chip *of_msi_chip_find_by_node(struct device_node *of_node)

Most other functions of this type are named of_find_*_by_node(), so for
consistency it'd be better to call this of_find_msi_chip_by_node().

> +{
> +	struct msi_chip *c;
> +	list_for_each_entry(c, &msi_chip_list, link) {
> +		if (c->of_node == of_node &&
> +		    of_property_read_bool(c->of_node, "msi-controller"))

Perhaps it would be more efficient to put this check within the
of_msi_chip_add() function?

> diff --git a/include/linux/msi.h b/include/linux/msi.h
> index e3a137d..8b930c3 100644
> --- a/include/linux/msi.h
> +++ b/include/linux/msi.h
> @@ -74,6 +74,8 @@ void default_restore_msi_irqs(struct pci_dev *dev, int irq);
>  struct msi_chip {
>  	struct module *owner;
>  	struct device *dev;
> +	struct device_node *of_node;

I know there's no easier way to do this, but I think we need to find a
way to clean this up at some point. There's no point in storing the OF
node in two places.

> +	struct list_head link;

I'd prefer this to be named "list" for consistency.

> diff --git a/include/linux/of_pci.h b/include/linux/of_pci.h
> index 7a04826..6e88189 100644
> --- a/include/linux/of_pci.h
> +++ b/include/linux/of_pci.h
> @@ -2,6 +2,7 @@
>  #define __OF_PCI_H
>  
>  #include <linux/pci.h>
> +#include <linux/msi.h>
>  
>  struct pci_dev;
>  struct of_irq;
> @@ -13,4 +14,7 @@ struct device_node *of_pci_find_child_device(struct device_node *parent,
>  int of_pci_get_devfn(struct device_node *np);
>  int of_pci_parse_bus_range(struct device_node *node, struct resource *res);
>  
> +void of_msi_chip_add(struct msi_chip *chip);
> +struct msi_chip *of_msi_chip_find_by_node(struct device_node *of_node);

Since these will be exported and conditionalized on PCI_MSI as suggested
above, maybe they should get a dummy implementation if (!OF || !PCI_MSI)
so that drivers don't have to conditionally call them?

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/20130621/7f5bbf19/attachment.sig>

  parent reply	other threads:[~2013-06-21 10:16 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 [this message]
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=20130621101640.GD12441@manwe \
    --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).