linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 14/15] PCI/MSI: pci-xgene-msi: Get rid of struct msi_controller
Date: Fri, 10 Jul 2015 09:43:52 +0100	[thread overview]
Message-ID: <559F85C8.7000403@arm.com> (raw)
In-Reply-To: <CADaLNDm9o8XH749ocy4eJO=1T_w0AAFa1UZJLiFGrgR=5Aqjcg@mail.gmail.com>

Hi Duc,

On 09/07/15 23:12, Duc Dang wrote:
> On Tue, Jul 7, 2015 at 10:18 AM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>> The XGene MSI driver only uses the msi_controller structure as
>> a way to match the host bridge  with its MSI HW, and thus the
>> msi_domain.
>>
>> But now that we can directly associate an msi_domain with a device,
>> there is no use keeping this msi_controller around.
>>
>> Just remove all traces of msi_controller from the driver.
>>
> Thanks, Marc.
> 
> I tested this patch set and it works on my APM X-Gene evaluation platform.

Ah, thanks! I did that as a side effort, but didn't have a chance to
test it (who the *&%^!! decided to mount this board in a 1U chassis
without an angle bracket for the PCIe bus? Seriously???).

> The xgene_pcie_msi_enable (in driver/pci/host/pci-xgene.c), which is
> used to get msi_controller for X-Gene PCIe port,
> also becomes unnecessary with this patch set. I will post a clean-up
> patch when your changes are accepted.

Yeah, I didn't want to touch too much of it without any testing.

> You can add my tested-by if you want:
> 
> Tested-by: Duc Dang <dhdang@apm.com>

Thanks a lot for that,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2015-07-10  8:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 17:17 [PATCH v3 00/15] Introducing per-device MSI domain Marc Zyngier
2015-07-07 17:17 ` [PATCH v3 01/15] genirq: irqdomain: Allow irq domain aliasing Marc Zyngier
2015-07-07 17:17 ` [PATCH v3 02/15] PCI: MSI: Register irq domain with specific token Marc Zyngier
2015-07-07 17:17 ` [PATCH v3 03/15] device core: Introduce per-device MSI domain pointer Marc Zyngier
2015-07-07 17:17 ` [PATCH v3 04/15] PCI/MSI: Add hooks to populate the msi_domain field Marc Zyngier
2015-07-07 17:17 ` [PATCH v3 05/15] PCI/MSI: of: Add support for OF-provided msi_domain Marc Zyngier
2015-07-07 17:17 ` [PATCH v3 06/15] PCI/MSI: of: Allow msi_domain lookup using the host bridge node Marc Zyngier
2015-07-07 17:17 ` [PATCH v3 07/15] PCI/MSI: Let pci_msi_get_domain use struct device's msi_domain Marc Zyngier
2015-07-07 17:17 ` [PATCH v3 08/15] platform: of: Assign MSI domain to platform device Marc Zyngier
2015-07-07 17:17 ` [PATCH v3 09/15] irqchip: gicv3-its: Split PCI/MSI code from the core ITS driver Marc Zyngier
2015-07-08 10:48   ` Thomas Gleixner
2015-07-08 11:02     ` Marc Zyngier
2015-07-07 17:18 ` [PATCH v3 10/15] irqchip: gicv3-its: Register irq domain with platform MSI token Marc Zyngier
2015-07-07 17:18 ` [PATCH v3 11/15] irqchip: GICv2m: Get rid of struct msi_controller Marc Zyngier
2015-07-07 17:18 ` [PATCH v3 12/15] irqchip: gicv3-its: " Marc Zyngier
2015-07-07 17:18 ` [PATCH v3 13/15] irqchip: gicv3-its: Make the PCI/MSI code standalone Marc Zyngier
2015-07-07 17:18 ` [PATCH v3 14/15] PCI/MSI: pci-xgene-msi: Get rid of struct msi_controller Marc Zyngier
2015-07-09 22:12   ` Duc Dang
2015-07-10  8:43     ` Marc Zyngier [this message]
2015-07-07 17:18 ` [PATCH v3 15/15] PCI/MSI: Drop domain field from msi_controller Marc Zyngier
2015-07-09 13:58 ` [PATCH v3 00/15] Introducing per-device MSI domain Lorenzo Pieralisi
2015-07-09 14:35   ` Marc Zyngier
2015-07-10 13:34     ` Lorenzo Pieralisi
2015-07-10 14:25       ` Marc Zyngier

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=559F85C8.7000403@arm.com \
    --to=marc.zyngier@arm.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).