From mboxrd@z Thu Jan 1 00:00:00 1970 From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi) Date: Fri, 3 Feb 2017 16:40:32 +0000 Subject: [PATCH v8 00/15] ACPI platform MSI support and its example mbigen In-Reply-To: <6eb61900-640d-fd7f-7e7f-9deced1ec71e@codeaurora.org> References: <1484744105-53140-1-git-send-email-guohanjun@huawei.com> <45d4de34-cfd2-06af-93c2-e721bd80ab43@codeaurora.org> <8687cb39-bffe-8f4a-76aa-a4d4ed61d30e@arm.com> <6eb61900-640d-fd7f-7e7f-9deced1ec71e@codeaurora.org> Message-ID: <20170203164032.GA31093@red-moon> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Feb 03, 2017 at 10:57:44AM -0500, Sinan Kaya wrote: > On 2/3/2017 10:49 AM, Marc Zyngier wrote: > >> Patches 13-15 are specific for MBIGEN. 00-12 are for the base functionality. > > Is that to support SMMUv3's own MSI generation? It would be helpful if > > you explained why you want this code to be merged beforehand, > > potentially without any in-tree user. > > Sure, I'm more interested in supporting MSI on my HIDMA code rather than > MSI on SMMUv3. > > HIDMA MSI patches were merged November 2016. > > https://github.com/torvalds/linux/commits/master/drivers/dma/qcom/hidma.c > > Commits on Nov 3, 2016 > @vinodkoul > dmaengine: qcom_hidma: add MSI support for interrupts ? > Sinan Kaya committed with vinodkoul on Oct 21, 2016 > > I tested the first 12 patches of this series against HIDMA and provided > my tested-by. Ok, we should have split this series before then. Now, if: (1) Marc is ok with patches [4-7,10,12] (2) Your HIDMA MSI does not depend on Agustin patch series to work (3) Rafael is ok with a pull request at -rc7 (ie I won't be able to send it before then since I want to test it) I will send a pull request to Rafael for patches [1-12] on Monday. If any of (1)-(2)-(3) does not hold it is going to be v4.12, a single driver is not the end of the world (and this will give us time to add support for SMMUv3 MSI that this series can't handle). Thanks, Lorenzo