From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 00/15] ACPI platform MSI support and its example mbigen
Date: Fri, 3 Feb 2017 10:35:08 -0500 [thread overview]
Message-ID: <45d4de34-cfd2-06af-93c2-e721bd80ab43@codeaurora.org> (raw)
In-Reply-To: <fd106be9-836d-8d91-e57c-183ca56b4a49@arm.com>
On 2/3/2017 10:11 AM, Marc Zyngier wrote:
> On 03/02/17 14:50, Sinan Kaya wrote:
>> On 1/18/2017 7:54 AM, Hanjun Guo wrote:
>>> From: Hanjun Guo <hanjun.guo@linaro.org>
>>>
>>> With platform msi support landed in the kernel, and the introduction
>>> of IORT for GICv3 ITS (PCI MSI) and SMMU, the framework for platform msi
>>> is ready, this patch set add few patches to enable the ACPI platform
>>> msi support.
>>>
>>> For platform device connecting to ITS on arm platform, we have IORT
>>> table with the named componant node to describe the mappings of paltform
>>> device and ITS, so we can retrieve the dev id and find its parent
>>> irqdomain (ITS) from IORT table (simlar with the ACPI ITS support).
>>>
>>
>> I understand that there is a consensus on IORT/SMMUv3 specific pieces
>> of this series while there is some ongoing work on the MBIgen part in
>> due to dependency on Agustin's patch vs. ACPI definitions.
>>
>> Can we merge the IORT/SMMUv3 specific pieces to 4.11 so that the base
>> implementation comes in place?
>
> Sorry, but I may be missing something. Which IORT/SMMUv3 patches are we
> talking about? Do you have a pointer to a series?
>
I was talking about patches V8 00-12 of this particular one.
[PATCH v8 00/15] ACPI platform MSI support and its example mbigen
Patches 13-15 are specific for MBIGEN. 00-12 are for the base functionality.
> Thanks,
>
> M.
>
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-02-03 15:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 12:54 [PATCH v8 00/15] ACPI platform MSI support and its example mbigen Hanjun Guo
2017-01-18 12:54 ` [PATCH v8 01/15] ACPI: IORT: fix the indentation in iort_scan_node() Hanjun Guo
2017-01-18 12:54 ` [PATCH v8 02/15] ACPI: IORT: add missing comment for iort_dev_find_its_id() Hanjun Guo
2017-01-18 12:54 ` [PATCH v8 03/15] ACPI: IORT: minor cleanup for iort_match_node_callback() Hanjun Guo
2017-01-18 12:54 ` [PATCH v8 04/15] irqchip: gic-v3-its: keep the head file include in alphabetic order Hanjun Guo
2017-01-18 12:54 ` [PATCH v8 05/15] irqchip: gicv3-its: platform-msi: refactor its_pmsi_prepare() Hanjun Guo
2017-01-18 12:54 ` [PATCH v8 06/15] irqchip: gicv3-its: platform-msi: refactor its_pmsi_init() to prepare for ACPI Hanjun Guo
2017-01-18 12:54 ` [PATCH v8 07/15] irqchip: gicv3-its: platform-msi: scan MADT to create platform msi domain Hanjun Guo
2017-01-18 12:54 ` [PATCH v8 08/15] ACPI: IORT: rename iort_node_map_rid() to make it generic Hanjun Guo
2017-01-18 12:54 ` [PATCH v8 09/15] ACPI: IORT: introduce iort_node_map_platform_id() to retrieve dev id Hanjun Guo
2017-01-18 12:55 ` [PATCH v8 10/15] ACPI: platform-msi: retrieve dev id from IORT Hanjun Guo
2017-04-17 21:44 ` Sinan Kaya
2017-04-17 22:01 ` Sinan Kaya
2017-04-18 1:27 ` Hanjun Guo
2017-04-18 1:30 ` Sinan Kaya
2017-04-18 1:33 ` Hanjun Guo
2017-01-18 12:55 ` [PATCH v8 11/15] ACPI: platform: setup MSI domain for ACPI based platform device Hanjun Guo
2017-01-18 12:55 ` [PATCH v8 12/15] msi: platform: make platform_msi_create_device_domain() ACPI aware Hanjun Guo
2017-01-18 12:55 ` [PATCH v8 13/15] irqchip: mbigen: drop module owner Hanjun Guo
2017-01-18 12:55 ` [PATCH v8 14/15] irqchip: mbigen: introduce mbigen_of_create_domain() Hanjun Guo
2017-01-18 12:55 ` [PATCH v8 15/15] irqchip: mbigen: Add ACPI support Hanjun Guo
2017-02-03 2:27 ` Hanjun Guo
2017-02-03 14:50 ` [PATCH v8 00/15] ACPI platform MSI support and its example mbigen Sinan Kaya
2017-02-03 15:11 ` Marc Zyngier
2017-02-03 15:35 ` Sinan Kaya [this message]
2017-02-03 15:49 ` Marc Zyngier
2017-02-03 15:57 ` Sinan Kaya
2017-02-03 16:40 ` Lorenzo Pieralisi
2017-02-03 16:52 ` Sinan Kaya
2017-02-04 3:59 ` Hanjun Guo
2017-02-03 18:36 ` Lorenzo Pieralisi
2017-02-04 7:02 ` Hanjun Guo
2017-02-06 14:22 ` Lorenzo Pieralisi
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=45d4de34-cfd2-06af-93c2-e721bd80ab43@codeaurora.org \
--to=okaya@codeaurora.org \
--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).