On Thu, 08 Oct 2020 21:47:29 +0100,
Thomas Gleixner wrote:
>
> On Thu, Oct 08 2020 at 14:06, Marc Zyngier wrote:
> > On 2020-10-08 12:22, Thomas Gleixner wrote:
> > Here's what I have now, with the pmc driver calling
> > irq_domain_disconnect_hierarchy() at the right spots.
> >
> > static int
On Thu, Oct 08 2020 at 14:06, Marc Zyngier wrote:
> On 2020-10-08 12:22, Thomas Gleixner wrote:
> Here's what I have now, with the pmc driver calling
> irq_domain_disconnect_hierarchy() at the right spots.
>
> static int irq_domain_alloc_irq_data(struct irq_domain *domain,
> @@ -1362,11 +1442,16
On 2020-10-08 12:22, Thomas Gleixner wrote:
On Wed, Oct 07 2020 at 13:45, Marc Zyngier wrote:
+/**
+ * irq_domain_trim_hierarchy - Trim the uninitialized part of a irq
hierarchy
+ * @virq: IRQ number to trim where the hierarchy is to be trimmed
+ *
+ * Drop the partial irq_data hierarchy
On Wed, Oct 07 2020 at 13:45, Marc Zyngier wrote:
> +/**
> + * irq_domain_trim_hierarchy - Trim the uninitialized part of a irq hierarchy
> + * @virq:IRQ number to trim where the hierarchy is to be trimmed
> + *
> + * Drop the partial irq_data hierarchy from the level where the
> + *
It appears that some HW is ugly enough that not all the interrupts
connected to a particular interrupt controller end up with the same
hierarchy depth (some of them are terminated early). This leaves
the irqchip hacker with only two choices, both equally bad:
- create discrete domain chains, one
5 matches
Mail list logo