[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaNfFqzN0nYPrXd8ZVOFur6W2iEUSM_KErH6eKoiJ7vDQ@mail.gmail.com>
Date: Thu, 25 Jul 2013 15:19:32 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Grant Likely <grant.likely@...aro.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Guennadi Liakhovetski <g.liakhovetski@....de>
Subject: Re: How to create IRQ mappings in a GPIO driver that doesn't control
its IRQ domain ?
On Thu, Jul 25, 2013 at 11:45 AM, Laurent Pinchart
<laurent.pinchart@...asonboard.com> wrote:
> The two devices are independent, so there's no real parent/child relationship.
> However, as Grant proposed, I could list all the interrupts associated with
> GPIOs in the GPIO controller DT node. I would then just call
> irq_of_parse_and_map() in the .to_irq() handler to magically translate the
> GPIO number to a mapped IRQ number.
That works even if the device tree will need a comment or two
to explain what is going on.
I suggested a similar solution for the OMAP crossbar mux
that is discussed in another thread, so I'm happy with this
approach.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists