From: Aaro Koskinen <aaro.koskinen@iki.fi> Date: 2016-08-23 20:37:19
Hi,
gpio-leds fails to probe on OCTEON with v4.8-rc3 and when using
arch/mips/boot/dts/cavium-octeon/dlink_dsr-1000n.dts. Leds still
worked with v4.7.
I bisected this to:
commit 15cc2ed6dcf91a8658e084be4e140147161819d7
Author: Jon Hunter [off-list ref]
Date: Mon Jun 20 14:49:18 2016 +0100
of/irq: Mark initialised interrupt controllers as populated
I have no idea how this is related to gpio-leds, except that on OCTEON
DTBs the gpio node is also interrupt controller...
Any ideas?
A.
From: Steven J. Hill <hidden> Date: 2016-08-24 20:18:12
On 08/23/2016 03:36 PM, Aaro Koskinen wrote:
Hi,
gpio-leds fails to probe on OCTEON with v4.8-rc3 and when using
arch/mips/boot/dts/cavium-octeon/dlink_dsr-1000n.dts. Leds still
worked with v4.7.
I bisected this to:
commit 15cc2ed6dcf91a8658e084be4e140147161819d7
Author: Jon Hunter [off-list ref]
Date: Mon Jun 20 14:49:18 2016 +0100
of/irq: Mark initialised interrupt controllers as populated
I have no idea how this is related to gpio-leds, except that on OCTEON
DTBs the gpio node is also interrupt controller...
Hey Aaro.
It is actually two patches that cause the breakage. The other is:
commit e55aeb6ba4e8cc3549bff1e75ea1d029324bce21
of/irq: Mark interrupt controllers as populated before initialisation
I needed to revert both of these in order to get MMC working on our 71xx and 78xx boards. For our MMC, I got error messages from the MMC core of "Invalid POWER GPIO" until I applied the second patch. I will have a fix worthy of upstreaming today which will be posted today.
Steve
From: Aaro Koskinen <aaro.koskinen@iki.fi> Date: 2016-08-25 18:27:06
Hi,
On Wed, Aug 24, 2016 at 11:42:00AM -0500, Steven J. Hill wrote:
It is actually two patches that cause the breakage. The other is:
commit e55aeb6ba4e8cc3549bff1e75ea1d029324bce21
of/irq: Mark interrupt controllers as populated before initialisation
I needed to revert both of these in order to get MMC working on our 71xx and
78xx boards. For our MMC, I got error messages from the MMC core of "Invalid
POWER GPIO" until I applied the second patch. I will have a fix worthy of
upstreaming today which will be posted today.
On Wed, Aug 24, 2016 at 11:42:00AM -0500, Steven J. Hill wrote:
quoted
It is actually two patches that cause the breakage. The other is:
commit e55aeb6ba4e8cc3549bff1e75ea1d029324bce21
of/irq: Mark interrupt controllers as populated before initialisation
I needed to revert both of these in order to get MMC working on our 71xx and
78xx boards. For our MMC, I got error messages from the MMC core of "Invalid
POWER GPIO" until I applied the second patch. I will have a fix worthy of
upstreaming today which will be posted today.
@@ -1618,6 +1618,7 @@ static int __init octeon_irq_init_gpio(pr_warn("Cannot allocate memory for GPIO irq_domain.\n");return-ENOMEM;}+of_node_clear_flag(gpio_node,OF_POPULATED);return0;}
This afaics wasn't merged and the discussion looks stalled. Was this
issue discussed elsewhere or even fixed in between? Just asking, because
this issue is on the list of regressions for 4.8.
Ciao, Thorsten
From: Aaro Koskinen <aaro.koskinen@iki.fi> Date: 2016-09-11 22:14:17
Hi,
On Sun, Sep 11, 2016 at 02:41:39PM +0200, Thorsten Leemhuis wrote:
Hi! On 25.08.2016 20:24, Aaro Koskinen wrote:
quoted
On Wed, Aug 24, 2016 at 11:42:00AM -0500, Steven J. Hill wrote:
quoted
It is actually two patches that cause the breakage. The other is:
commit e55aeb6ba4e8cc3549bff1e75ea1d029324bce21
of/irq: Mark interrupt controllers as populated before initialisation
I needed to revert both of these in order to get MMC working on our 71xx and
78xx boards. For our MMC, I got error messages from the MMC core of "Invalid
POWER GPIO" until I applied the second patch. I will have a fix worthy of
upstreaming today which will be posted today.
@@ -1618,6 +1618,7 @@ static int __init octeon_irq_init_gpio(pr_warn("Cannot allocate memory for GPIO irq_domain.\n");return-ENOMEM;}+of_node_clear_flag(gpio_node,OF_POPULATED);return0;}
This afaics wasn't merged and the discussion looks stalled. Was this
issue discussed elsewhere or even fixed in between? Just asking, because
this issue is on the list of regressions for 4.8.