public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 2/6] PCI: tegra: use new OF interrupt mapping when possible
Date: Fri, 7 Mar 2014 01:25:28 +0100	[thread overview]
Message-ID: <201403070125.28582.arnd@arndb.de> (raw)
In-Reply-To: <1394127555.4582.1.camel@weser.hi.pengutronix.de>

On Thursday 06 March 2014, Lucas Stach wrote:
> Am Donnerstag, den 06.03.2014, 10:36 -0700 schrieb Stephen Warren:
> > On 03/05/2014 06:25 AM, Lucas Stach wrote:
> > > This is the recommended method of doing the IRQ
> > > mapping. For old devicetrees we fall back to the
> > > previous practice.
> > 
> > Tested-by: Stephen Warren <swarren@nvidia•com>
> > 
> > I tested both with and without patch 1/6, and the PCIe-based NIC on
> > Beaver worked fine either way. Without patch 1/6, I do see:
> > 
> > pci 0000:00:01.0: of_irq_parse_pci() failed with rc=-22
> > 
> > ... but that seems reasonable given that the DT that of_irq_parse_pci()
> > parses is missing, and did correctly trigger the fallback path, so
> > everything still worked.
> 
> Yes, this should be normal. It spits this error for old DTs, but keeps
> doing the right thing. I'm not sure if we should downgrade this to info
> or dbg.

No, I think printing an error like this is appropriate: it is an incentive
to update the dts files, but doesn't look too urgent as long as everything
still works.

	Arnd

  reply	other threads:[~2014-03-07  0:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 13:25 [PATCH v2 0/6] PCI irq mapping fixes and cleanups Lucas Stach
2014-03-05 13:25 ` [PATCH v2 1/6] ARM: dts: tegra: add PCIe interrupt mapping properties Lucas Stach
2014-03-05 21:55   ` Stephen Warren
2014-03-06  9:33     ` Lucas Stach
2014-03-06 17:41   ` Stephen Warren
2014-03-05 13:25 ` [PATCH v2 2/6] PCI: tegra: use new OF interrupt mapping when possible Lucas Stach
2014-03-06 17:36   ` Stephen Warren
2014-03-06 17:39     ` Lucas Stach
2014-03-07  0:25       ` Arnd Bergmann [this message]
2014-03-07  3:31         ` Jingoo Han
2014-04-11 17:40       ` Srikanth Thokala
2014-04-11 20:41         ` Jason Gunthorpe
2014-04-14 10:56           ` Srikanth Thokala
2014-04-04 16:55   ` Bjorn Helgaas
2014-04-15 10:07     ` Lucas Stach
2014-04-15 18:30       ` Bjorn Helgaas
2014-04-16  8:20         ` Lucas Stach
2014-04-16 16:29           ` Bjorn Helgaas
2014-03-05 13:25 ` [PATCH v2 3/6] PCI: rcar: " Lucas Stach
2014-03-06  4:12   ` Simon Horman
2014-04-04 17:01   ` Bjorn Helgaas
2014-04-07  9:30     ` [PATCH v2 rebased] " Lucas Stach
2014-03-05 13:25 ` [PATCH v2 4/6] ARM: dts: exynos5440: fix PCIe interrupt mapping Lucas Stach
2014-03-06  2:38   ` Jingoo Han
2014-03-05 13:25 ` [PATCH v2 5/6] ARM: dts: imx6: add PCIe interrupt mapping properties Lucas Stach
2014-03-10  3:09   ` Shawn Guo
2014-03-05 13:25 ` [PATCH v2 6/6] PCI: designware: use new OF interrupt mapping when possible Lucas Stach
2014-03-05 18:42   ` Jason Gunthorpe
2014-04-04 17:03     ` Bjorn Helgaas
2014-04-04 17:05       ` Bjorn Helgaas
2014-04-07  8:38         ` Lucas Stach
2014-04-07  9:13           ` Jingoo Han
2014-03-06  2:47   ` Jingoo Han
2014-03-06 15:33     ` Marek Vasut
2014-03-13 17:41       ` Tim Harvey
2014-03-28 15:47 ` [PATCH v2 0/6] PCI irq mapping fixes and cleanups Lucas Stach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201403070125.28582.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox