From: Wolfram Sang <hidden> Date: 2012-10-10 20:56:57
Currently, when booting MPC52xx based platforms, we get:
mpc52xx_irqhost_map: invalid irq: virq=16, l1=0, l2=3
irq: irq-16==>hwirq-0x3 mapping failed: -22
[WARNing skipped]
The warning is wrong since the mapping itself is valid. However, there is no
support for that type of IRQ currently. Print a proper warning and bind the irq
to a no_irq chip.
Signed-off-by: Wolfram Sang <redacted>
Cc: John Bonesio <redacted>
Cc: Anatolij Gustschin <agust@denx.de>
Cc: Grant Likely <redacted>
---
arch/powerpc/platforms/52xx/mpc52xx_pic.c | 5 +++++
1 file changed, 5 insertions(+)
From: Wolfram Sang <hidden> Date: 2012-10-11 09:19:25
Currently, when booting MPC52xx based platforms, we get:
mpc52xx_irqhost_map: invalid irq: virq=16, l1=0, l2=3
irq: irq-16==>hwirq-0x3 mapping failed: -22
[WARNing skipped]
The warning is wrong since the mapping itself is valid. However, there is no
support for that type of IRQ currently. Print a proper warning and bind the irq
to a no_irq chip.
Signed-off-by: Wolfram Sang <redacted>
Cc: John Bonesio <redacted>
Cc: Anatolij Gustschin <agust@denx.de>
Cc: Grant Likely <redacted>
---
Change since V1: drop the default state since all possibilities for l1 are now
covered in the switch-statement.
arch/powerpc/platforms/52xx/mpc52xx_pic.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
From: Wolfram Sang <hidden> Date: 2012-10-20 06:54:51
On Thu, Oct 11, 2012 at 11:19:15AM +0200, Wolfram Sang wrote:
Currently, when booting MPC52xx based platforms, we get:
mpc52xx_irqhost_map: invalid irq: virq=16, l1=0, l2=3
irq: irq-16==>hwirq-0x3 mapping failed: -22
[WARNing skipped]
The warning is wrong since the mapping itself is valid. However, there is no
support for that type of IRQ currently. Print a proper warning and bind the irq
to a no_irq chip.
Signed-off-by: Wolfram Sang <redacted>
Cc: John Bonesio <redacted>
Cc: Anatolij Gustschin <agust@denx.de>
Cc: Grant Likely <redacted>
Ping. I'd really like to get rid of the WARNing for all MPC52xx boards.
It looks pretty scary to people who don't know the issues behind it.
quoted hunk
---
Change since V1: drop the default state since all possibilities for l1 are now
covered in the switch-statement.
arch/powerpc/platforms/52xx/mpc52xx_pic.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
Hi,
On Thu, 11 Oct 2012 11:19:15 +0200
Wolfram Sang [off-list ref] wrote:
Currently, when booting MPC52xx based platforms, we get:
mpc52xx_irqhost_map: invalid irq: virq=16, l1=0, l2=3
irq: irq-16==>hwirq-0x3 mapping failed: -22
[WARNing skipped]
The warning is wrong since the mapping itself is valid. However, there is no
support for that type of IRQ currently. Print a proper warning and bind the irq
to a no_irq chip.
Signed-off-by: Wolfram Sang <redacted>
Cc: John Bonesio <redacted>
Cc: Anatolij Gustschin <agust@denx.de>
Cc: Grant Likely <redacted>
---
Change since V1: drop the default state since all possibilities for l1 are now
covered in the switch-statement.
arch/powerpc/platforms/52xx/mpc52xx_pic.c | 9 +++++----
From: Wolfram Sang <hidden> Date: 2012-11-03 14:26:22
quoted
Currently, when booting MPC52xx based platforms, we get:
mpc52xx_irqhost_map: invalid irq: virq=16, l1=0, l2=3
irq: irq-16==>hwirq-0x3 mapping failed: -22
[WARNing skipped]
The warning is wrong since the mapping itself is valid. However, there is no
support for that type of IRQ currently. Print a proper warning and bind the irq
to a no_irq chip.
Signed-off-by: Wolfram Sang <redacted>
applied, thanks!
Thanks, can we have that in 3.7. already?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
On Sat, 3 Nov 2012 15:26:15 +0100
Wolfram Sang [off-list ref] wrote:
quoted
quoted
Currently, when booting MPC52xx based platforms, we get:
mpc52xx_irqhost_map: invalid irq: virq=16, l1=0, l2=3
irq: irq-16==>hwirq-0x3 mapping failed: -22
[WARNing skipped]
The warning is wrong since the mapping itself is valid. However, there is no
support for that type of IRQ currently. Print a proper warning and bind the irq
to a no_irq chip.
Signed-off-by: Wolfram Sang <redacted>
applied, thanks!
Thanks, can we have that in 3.7. already?
I hope so, a pull request including this patch is pending.
Thanks,
Anatolij