Thread (58 messages) 58 messages, 6 authors, 2016-10-09

RE: [PATCH v5 3/3] pci:aer: add support aer interrupt with none MSI/MSI-X/INTx mode

From: Po Liu <hidden>
Date: 2016-09-21 11:27:58
Also in: linux-arm-kernel, linux-pci, lkml

Hi Shawn,

 -----Original Message-----
 From: Shawn Guo [mailto:shawnguo@kernel.org]
 Sent: Tuesday, September 20, 2016 8:39 PM
 To: Po Liu
 Cc: linux-pci@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
 linux-kernel@vger.kernel.org; devicetree@vger.kernel.org; Roy Zang; Arnd
 Bergmann; Marc Zyngier; Stuart Yoder; Leo Li; M.H. Lian; Murali
 Karicheri; Bjorn Helgaas; Mingkai Hu
 Subject: Re: [PATCH v5 3/3] pci:aer: add support aer interrupt with none
 MSI/MSI-X/INTx mode
 
 On Sun, Sep 18, 2016 at 03:37:27AM +0000, Po Liu wrote:
 > Hi Shawn,
 >
 >
 > >  -----Original Message-----
 > >  From: Shawn Guo [mailto:shawnguo@kernel.org]
 > >  Sent: Sunday, September 18, 2016 8:52 AM
 > >  To: Po Liu
 > >  Cc: linux-pci@vger.kernel.org;
 > > linux-arm-kernel@lists.infradead.org;
 > >  linux-kernel@vger.kernel.org; devicetree@vger.kernel.org; Roy Zang;
 > > Arnd  Bergmann; Marc Zyngier; Stuart Yoder; Leo Li; M.H. Lian;
 > > Murali  Karicheri; Bjorn Helgaas; Mingkai Hu
 > >  Subject: Re: [PATCH v5 3/3] pci:aer: add support aer interrupt with
 > > none  MSI/MSI-X/INTx mode
 > >
 > >  On Tue, Sep 13, 2016 at 12:40:59PM +0800, Po Liu wrote:
 > >  > On some platforms, root port doesn't support MSI/MSI-X/INTx in RC
 mode.
 > >  > When chip support the aer interrupt with none MSI/MSI-X/INTx
 > > mode,  > maybe there is interrupt line for aer pme etc. Search the
 > > interrupt  > number in the fdt file. Then fixup the dev->irq with it.
 > >  >
 > >  > Signed-off-by: Po Liu [off-list ref]
 > >
 > >  Will the new kernel work with existing/old DTB?  I'm trying to
 > > understand the dependency between driver and DTS changes.
 >
 > Yes, We've never use name 'intr' before. So we remove it is ok.
 > 'aer' is a dts name for researching it's true interrupt number by
 kernel. This patch is first time to use name 'aer'. So it must be
 compatible with existing/old DTB.
 
 Does that mean driver and DTS changes can go through separate trees, i.e.
 PCI and arm-soc, without introducing regressions on either tree?
 Or does the patch series needs to go in as a whole?
Should be as a whole. The driver base on the dts. Or else, the driver would not found the 'aer' point.
Thanks!

Po
 
 Shawn
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help