[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5245625.0MITzPXo6V@wuerfel>
Date: Wed, 30 Mar 2016 12:10:29 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Roberto Fichera <kernel@...no-soft.it>,
Tim Harvey <tharvey@...eworks.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Richard Zhu <Richard.Zhu@...escale.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Krzysztof Hałasa <khalasa@...p.pl>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Petr Štetiar <ynezz@...e.cz>,
Fabio Estevam <festevam@...il.com>,
Lucas Stach <l.stach@...gutronix.de>
Subject: Re: [PATCH] i.MX6 PCIe: Fix imx6_pcie_deassert_core_reset() polarity
On Wednesday 30 March 2016 10:00:33 Roberto Fichera wrote:
> >
> > Check your XIO2001 routing and insure the following for proper IRQ mapping:
> > Slot12: IDSEL A28: socket INTA = XIO2001 INTA
> > Slot13: IDSEL A29: socket INTA = XIO2001 INTB
> > Slot14: IDSEL A30: socket INTA = XIO2001 INTC
> > Slot15: IDSEL A31: socket INTA = XIO2001 INTD
>
> After crosschecking with our hardware designer the PCB IRQ mapping is the following:
>
> J2 : IDSEL A16: => Device 0 : socket INTA = XIO2001 INTA
> J3 : IDSEL A18: => Device 2 : socket INTA = XIO2001 INTA* **(This should be INTC)*
> J11: IDSEL A20: => Device 4 : socket INTA = XIO2001 INTA
>
> The interrupt routing for J3 is wrong. The XIO2001 driver may expect Device 2 to interrupt on INTC - but it will
> interrupt on INTA.
What does your interrupt-map property look like then? Note that you
have to override both map and map-mask in this case.
Arnd
Powered by blists - more mailing lists