linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: suravee.suthikulpanit@amd.com
Cc: liviu.dudau@arm.com, lorenzo.pieralisi@arm.com,
	will.deacon@arm.com, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Yijing Wang <wangyijing@huawei.com>
Subject: Re: [PATCH V2 0/2] PCI: generic: Assiging msi-controller to PCI hostbridge
Date: Thu, 13 Nov 2014 11:09:59 -0700	[thread overview]
Message-ID: <20141113180959.GR5064@google.com> (raw)
In-Reply-To: <1415733454-24322-1-git-send-email-suravee.suthikulpanit@amd.com>

[+cc Yijing]

On Tue, Nov 11, 2014 at 01:17:32PM -0600, suravee.suthikulpanit@amd.com wrote:
> From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
> 
> This patch set introduces a new callback function to allow PCI host drivers
> to specify MSI controller to be used for the child buses / devices.

Hi Suravee, 

As Srikanth mentioned, there's a series of MSI-related stuff from Yijing.
I recently put them on my pci/msi branch, and they overlap a bit with
what you're doing here.

So I'll drop these for now.  Maybe there's a way you can accomplish what
you need by implementing pcibios_msi_controller(), which Yijing added?

Also note that "msi-controller" is already being used in device tree (see
Documentation/devicetree/bindings/interrupt-controller/marvell), so maybe
you can do the name.

Bjorn

> This is reabased from:
>     git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/host-generic
> 
> Changes from V1:
>     - Adding "msi-parent" device tree binding in documentation.
>     - Rebase the patch to get rid of artifacts from other precursor patch
>       accidently applied to the developement tree. This should now apply cleanly
>       to the pci/host-generic branch.
> 
> Suravee Suthikulpanit (2):
>   PCI: Add new pci_ops for setting MSI parent for PCI bus
>   PCI: generic: Add set_msi_parent callback
> 
>  Documentation/devicetree/bindings/pci/host-generic-pci.txt |  3 +++
>  drivers/pci/host/pci-host-generic.c                        | 13 +++++++++++++
>  drivers/pci/probe.c                                        |  3 +++
>  include/linux/pci.h                                        |  1 +
>  4 files changed, 20 insertions(+)
> 
> -- 
> 1.9.3
> 

  parent reply	other threads:[~2014-11-13 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 19:17 [PATCH V2 0/2] PCI: generic: Assiging msi-controller to PCI hostbridge suravee.suthikulpanit
2014-11-11 19:17 ` [PATCH V2 1/2] PCI: Add new pci_ops for setting MSI parent for PCI bus suravee.suthikulpanit
2014-11-11 19:17 ` [PATCH V2 2/2] PCI: generic: Add msi_parent DT binding suravee.suthikulpanit
2014-11-12  6:56   ` Srikanth Thokala
2014-11-12  7:09     ` Srikanth Thokala
2014-11-12 11:37       ` Suravee Suthikulpanit
2014-11-12 11:36     ` Suravee Suthikulpanit
2014-11-13 18:09 ` Bjorn Helgaas [this message]
2014-11-14  1:19   ` [PATCH V2 0/2] PCI: generic: Assiging msi-controller to PCI hostbridge Yijing Wang

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=20141113180959.GR5064@google.com \
    --to=bhelgaas@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=wangyijing@huawei.com \
    --cc=will.deacon@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).