Groups > linux.kernel > #1661985

[REGRESSION next] gpio-keys broken with commit 2233bf7a92e7 ("gpio: mvebu: switch to regmap for register access")

From	Ralph Sennhauser <ralph.sennhauser@gmail.com>
Newsgroups	linux.kernel
Subject	[REGRESSION next] gpio-keys broken with commit 2233bf7a92e7 ("gpio: mvebu: switch to regmap for register access")
Date	2017-06-09 09:00 +0200
Message-ID	<tQm3N-6AA-17@gated-at.bofh.it> (permalink)
Organization	none

Show all headers | View raw

Hi Thomas,

Commit 2233bf7a92e7 ("gpio: mvebu: switch to regmap for register
access") in next-20170607 breaks gpio-keys on an armada-385 (Linksys
WRT3200ACM), noticed due to missing /dev/input/event0 and the below
dmesg output.

  # dmesg -l 0,1,2,3
  [    2.421130] genirq: Setting trigger mode 3 for irq 49 failed (mvebu_gpio_irq_set_type+0x0/0x168)
  [    2.429953] gpio-keys gpio-keys: Unable to claim irq 49; error -22


After reverting the offending commit all works again.

Ralph

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

[REGRESSION next] gpio-keys broken with commit 2233bf7a92e7 ("gpio:  mvebu: switch to regmap for register access") Ralph Sennhauser <ralph.sennhauser@gmail.com> - 2017-06-09 09:00 +0200
  Re: [REGRESSION next] gpio-keys broken with commit 2233bf7a92e7 ("gpio: mvebu: switch to regmap for register access") Gregory CLEMENT <gregory.clement@free-electrons.com> - 2017-06-09 12:20 +0200

csiph-web