genirq: __irq_set_trigger: change pr_warning to pr_debug

Commit 0c5d1eb77a8be917b638344a22afe1398236482b (genirq: record trigger
type) caused powerpc platforms that had no set_type() function in their
struct irq_chip to spew out warnings about "No set_type function for
IRQ...". This warning isn't necessarily justified though because the
generic powerpc platform code calls set_irq_type() (which in turn calls
__irq_set_trigger) with information from the device tree to establish
the interrupt mappings, regardless of whether the PIC can actually set
a type.

A platform's irq_chip might not have a set_type function for a variety
of reasons, for example: the platform may have the type essentially
hard-coded, or as in the case for Cell interrupts are just messages
past around that have no real concept of type, or the platform
could even have a virtual PIC as on the PS3.

Signed-off-by: Mark Nelson <markn@au1.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>

authored by Mark Nelson and committed by Ingo Molnar 3ff68a6a f131e243

+1 -1
+1 -1
kernel/irq/manage.c
··· 365 * IRQF_TRIGGER_* but the PIC does not support multiple 366 * flow-types? 367 */ 368 - pr_warning("No set_type function for IRQ %d (%s)\n", irq, 369 chip ? (chip->name ? : "unknown") : "unknown"); 370 return 0; 371 }
··· 365 * IRQF_TRIGGER_* but the PIC does not support multiple 366 * flow-types? 367 */ 368 + pr_debug("No set_type function for IRQ %d (%s)\n", irq, 369 chip ? (chip->name ? : "unknown") : "unknown"); 370 return 0; 371 }