wlcore: set irq_trigger in board files instead of hiding behind a quirk
The platform_quirk element in the platform data was used to change the way the IRQ is triggered. When set, the EDGE_IRQ quirk would change the irqflags used and treat edge trigger differently from the rest. Instead of hiding this irq flag setting behind the quirk, have the board files set the irq_trigger explicitly. This will allow us to use standard irq DT definitions later on. Signed-off-by: Luciano Coelho <luca@coelho.fi> [Eliad - rebase, add irq_trigger field and pass it, update board file changes] Signed-off-by: Eliad Peller <eliad@wizery.com> Tested-by: Nikita Kiryanov <nikita@compulab.co.il> Acked-by: Kalle Valo <kvalo@codeaurora.org> Acked-by: Sekhar Nori <nsekhar@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
This commit is contained in:

committed by
Tony Lindgren

parent
06e5801b8c
commit
6f921fab58
@@ -1385,8 +1385,8 @@ static const short da850_wl12xx_pins[] __initconst = {
|
||||
|
||||
static struct wl12xx_platform_data da850_wl12xx_wlan_data __initdata = {
|
||||
.irq = -1,
|
||||
.irq_trigger = IRQ_TYPE_EDGE_RISING,
|
||||
.board_ref_clock = WL12XX_REFCLOCK_38,
|
||||
.platform_quirks = WL12XX_PLATFORM_QUIRK_EDGE_IRQ,
|
||||
};
|
||||
|
||||
static __init int da850_wl12xx_init(void)
|
||||
|
Reference in New Issue
Block a user