irqchip: crossbar: Introduce ti, max-crossbar-sources to identify valid crossbar...
authorNishanth Menon <nm@ti.com>
Thu, 26 Jun 2014 07:10:31 +0000 (12:40 +0530)
committerJason Cooper <jason@lakedaemon.net>
Mon, 30 Jun 2014 19:20:49 +0000 (19:20 +0000)
commit2f7d2fb71dd0c14f9c0fe66f2ed7b4685fa745e2
tree41e0a9ae3da65a99c8913fb321c0e20faa063a22
parent8b09a45dc12f83f2312a47f0f0087ec4004ebacc
irqchip: crossbar: Introduce ti, max-crossbar-sources to identify valid crossbar mapping

Currently we attempt to map any crossbar value to an IRQ, however,
this is not correct from hardware perspective. There is a max crossbar
event number upto which hardware supports. So describe the same in
device tree using 'ti,max-crossbar-sources' property and use it to
validate requests.

[ jac - remove MAX_SOURCES from binding doc, use integer because we
shouldn't put implementation details in the binding docs ]

Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Sricharan R <r.sricharan@ti.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Link: https://lkml.kernel.org/r/1403766634-18543-14-git-send-email-r.sricharan@ti.com
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Documentation/devicetree/bindings/arm/omap/crossbar.txt
drivers/irqchip/irq-crossbar.c