genirq: Add IRQ 0 to domain debug file
Subsystems (2)
PATCH 1/1 genirq: Add IRQ 0 to domain debug file
Currently irq_domain_mapping debugfs file dumps IRQ information starting from IRQ 1. IRQ 0 is missing from that file. Add it to have the complete picture of IRQ/domains mappings.
--- kernel/irq/irqdomain.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/irq/irqdomain.c +1 -1
@@ -585,7 +585,7 @@ static int virq_debug_show(struct seq_file *m, void *private)"chip name" , (int )(2 *sizeof (void *) +2 ),"chip data" , "active", "type", "domain"); -for (i =1 ; i < nr_irqs; i++) { +for (i =0 ; i < nr_irqs; i++) { desc =irq_to_desc (i);if (!desc)continue ;
Signature · 1 line
2.1.1
Quoted 3 lines · Dmitry Eremin-Solenikov
Currently
irq_domain_mappingdebugfs file dumps IRQ information starting from IRQ 1. IRQ 0 is missing from that file. Add it to have the complete picture of IRQ/domains mappings.
Hi Dmitry,
For most irqdomain interfaces, they treat irq0 as invalid
interrupt. But on x86, it's possible to use irq0 for timer. It causes may confusion when enabling irqdomain for x86.
Regards!
Gerry
Quoted 20 lines
Signed-off-by Dmitry Eremin-Solenikov <[email protected]>--- kernel/irq/irqdomain.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)kernel/irq/irqdomain.c +1
-1@@ -585,7 +585,7 @@ static int virq_debug_show(struct seq_file *m, void *private)"chip name" , (int )(2 *sizeof (void *) +2 ),"chip data" , "active", "type", "domain"); -for (i =1 ; i < nr_irqs; i++) { +for (i =0 ; i < nr_irqs; i++) { desc =irq_to_desc (i);if (!desc)continue ;
Hello,
2014-11-15 16:01 GMT+03:00 Jiang Liu <[email protected]>:
Quoted 8 lines · Dmitry Eremin-Solenikov
Quoted 3 lines
Currently
irq_domain_mappingdebugfs file dumps IRQ information starting from IRQ 1. IRQ 0 is missing from that file. Add it to have the complete picture of IRQ/domains mappings.Hi Dmitry,
For most irqdomain interfaces, they treat irq0 as invalid
interrupt. But on x86, it's possible to use irq0 for timer. It causes may confusion when enabling irqdomain for x86.
I encountered with this issue when enabling IRQ domains support for one of ARM sub-architectures.
Signature · 2 lines
With best wishes Dmitry