On Thu, 12 Sep 2013, Thomas Gleixner wrote:
> On Thu, 12 Sep 2013, Felipe Balbi wrote:
>
> > On Thu, Sep 12, 2013 at 09:09:08PM +0530, Sricharan R wrote:
> > > +unsigned int crossbar_request_irq(struct irq_data *d)
> > > +{
> > > + int cb_no = d->hwirq;
> > > + int virq = allocate_free_irq(cb_no);
> > > + void *irq = &cb->crossbar_map[cb_no].hwirq;
> > > + int err;
> > > +
> > > + err = request_threaded_irq(virq, crossbar_irq, NULL,
> > > + 0, "CROSSBAR", irq);
> >
> > this is wrong, why don't you just set crossbar up as a chained handler.
>
> That's just a detail, which does not solve the underlying problem of
> the crossbar -> GIC mapping.
And actually the thing is the other way round:
GIC distributes to crossbar, so the underlying GIC irq would be the
chained handler.
Still does not solve the setup/request_irq issue.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
