Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753116AbbKPRYq (ORCPT ); Mon, 16 Nov 2015 12:24:46 -0500 Received: from www.linutronix.de ([62.245.132.108]:42045 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752280AbbKPRYo (ORCPT ); Mon, 16 Nov 2015 12:24:44 -0500 Date: Mon, 16 Nov 2015 18:24:03 +0100 (CET) From: Thomas Gleixner To: Qais Yousef cc: linux-kernel@vger.kernel.org, jason@lakedaemon.net, marc.zyngier@arm.com, jiang.liu@linux.intel.com, ralf@linux-mips.org, linux-mips@linux-mips.org Subject: Re: [PATCH 10/14] irqchip/mips-gic: Add a IPI hierarchy domain In-Reply-To: <5644AC66.2070508@imgtec.com> Message-ID: References: <1446549181-31788-1-git-send-email-qais.yousef@imgtec.com> <1446549181-31788-11-git-send-email-qais.yousef@imgtec.com> <5644AC66.2070508@imgtec.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1587 Lines: 40 On Thu, 12 Nov 2015, Qais Yousef wrote: > Issues I'm seeing: > > - Device domain would be identical to GIC domain and it would defer > everything to the parent domain except for the extra level of indirection. No? It's not identical. It's a subset of the GIC domain and it has different semantics than the IPI domain. > - The race condition I mentioned in my earlier email where we must be told > what hwirqs are available because we can't guarantee there's no real device > connected to it which could interfere with the operation. We have always to > work on a pre reserved set defined by the system. Currently GIC hard codes > this set, but I'll be making it a DT property in the future. We do that better now as we really don't want to start over when it turns out that the DT property imposes other issues on it. > - If we remove the mapping, how can a coprocessor drivers find out the > reverse mapping to pass the hwirq to the firmware so that it can send and > listen on the correct hwirqs? I have to say my current patches missed dealing > with this problem. Now I have something to test my rproc driver on I came to > realise I haven't added the function to do the reverse mapping. int ipi_get_hw_irq(int irq) { struct irq_data *d = irq_get_irq_data(irq); return d ? irqd_to_hwirq(d); } Hmm? Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/