Re: [PATCH v2] of_pci_irq: Silence bogus "of_irq_parse_pci() failed ..." messages.

2015-09-09 Thread David Daney
On 09/09/2015 10:44 AM, Frank Rowand wrote: Second attempt at this reply. The first reply was mangled. On 9/8/2015 11:28 AM, David Daney wrote: From: David Daney It is perfectly legitimate for a PCI device to have an PCI_INTERRUPT_PIN value of zero. This happens if the device doesn't use in

Re: [PATCH v2] of_pci_irq: Silence bogus "of_irq_parse_pci() failed ..." messages.

2015-09-09 Thread Frank Rowand
Second attempt at this reply. The first reply was mangled. On 9/8/2015 11:28 AM, David Daney wrote: > From: David Daney > > It is perfectly legitimate for a PCI device to have an > PCI_INTERRUPT_PIN value of zero. This happens if the device doesn't > use interrupts, or on PCIe devices, where o

Re: [PATCH v2] of_pci_irq: Silence bogus "of_irq_parse_pci() failed ..." messages.

2015-09-09 Thread Frank Rowand
On 9/8/2015 11:28 AM, David Daney wrote: > From: David Daney > > It is perfectly legitimate for a PCI device to have an > PCI_INTERRUPT_PIN value of zero. This happens if the device doesn't > use interrupts, or on PCIe devices, where only MSI/MSI-X are > supported. > > Silence the annoy

[PATCH v2] of_pci_irq: Silence bogus "of_irq_parse_pci() failed ..." messages.

2015-09-08 Thread David Daney
From: David Daney It is perfectly legitimate for a PCI device to have an PCI_INTERRUPT_PIN value of zero. This happens if the device doesn't use interrupts, or on PCIe devices, where only MSI/MSI-X are supported. Silence the annoying "of_irq_parse_pci() failed with rc=-19" error messages by mov