linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Zhu <hongxing.zhu@nxp.com>
To: "Z.q. Hou" <zhiqiang.hou@nxp.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	Bjorn Helgaas <helgaas@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"gustavo.pimentel@synopsys.com" <gustavo.pimentel@synopsys.com>
Subject: RE: [PATCH] PCI: dwc: Added link up check in map_bus of dw_child_pcie_ops
Date: Thu, 22 Oct 2020 06:20:18 +0000	[thread overview]
Message-ID: <VI1PR04MB5853E16DDAC5A382779F63F38C1D0@VI1PR04MB5853.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <HE1PR0402MB3371B927C5704F0C77E0EDB9841C0@HE1PR0402MB3371.eurprd04.prod.outlook.com>

> -----Original Message-----
> From: Z.q. Hou <zhiqiang.hou@nxp.com>
> Sent: Wednesday, October 21, 2020 4:48 PM
> To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>; Richard Zhu
> <hongxing.zhu@nxp.com>
> Cc: Kishon Vijay Abraham I <kishon@ti.com>; Bjorn Helgaas
> <helgaas@kernel.org>; linux-kernel@vger.kernel.org; linux-pci@vger.kernel.org;
> robh@kernel.org; bhelgaas@google.com; gustavo.pimentel@synopsys.com
> Subject: RE: [PATCH] PCI: dwc: Added link up check in map_bus of
> dw_child_pcie_ops
> 
> Hi Lorenzo and Richard,
> 
> > -----Original Message-----
> > From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > Sent: 2020年10月20日 17:55
> > To: Z.q. Hou <zhiqiang.hou@nxp.com>
> > Cc: Kishon Vijay Abraham I <kishon@ti.com>; Bjorn Helgaas
> > <helgaas@kernel.org>; linux-kernel@vger.kernel.org;
> > linux-pci@vger.kernel.org; robh@kernel.org; bhelgaas@google.com;
> > gustavo.pimentel@synopsys.com
> > Subject: Re: [PATCH] PCI: dwc: Added link up check in map_bus of
> > dw_child_pcie_ops
> >
> > On Tue, Oct 20, 2020 at 02:13:13AM +0000, Z.q. Hou wrote:
> >
> > [...]
> >
> > > > > For NXP Layerscape platforms (the ls1028a and ls2088a are also
> > > > > NXP
> > > > Layerscape platform), as the error response to AXI/AHB was
> > > > enabled, it will get UR error and trigger SError on AXI bus when
> > > > it accesses a non-existent BDF on a link down bus. I'm not clear
> > > > about how it happens on dra7xxx and imx6, since they doesn't
> > > > enable the error
> > response to AXI/AHB.
> > > >
> > > > That's exactly the case with DRA7xx as the error response is
> > > > enabled by default in the platform integration.
> > >
> > > Got feedback from the imx6 owner that imx6 like the dra7xx has the
> > > error response enabled by default.  Now it's clear that the problem
> > > on all these platforms is the same.
> >
> > On IMX6, enabled by default and read-only ? Or it can be changed ?
> 
> The AXI/AHB Bridge Slave Error Response Register is a common register of DWC IP,
> so I think it should be writeable. Richard, can you help to confirm?
> 
This register is writable, but only some bits of this reg can be wrote.

Best Regards
Richard Zhu

> > What's the plan for layerscape on this matter ?
> 
> I trend to change it back to the default error response behavior so that won't
> cause any error on CFG access, and have sent out the patch.
> And for the link up check before CFG accesses, in the DWC databoot (4.40a), it
> requires link up check before generating CFG requests, so need Gustavo help to
> make sure the reason of this requirement, any potential impact without the link
> up check.
> 
> Thanks,
> Zhiqiang
> >
> > Lorenzo

  reply	other threads:[~2020-10-22  6:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16  5:41 [PATCH] PCI: dwc: Added link up check in map_bus of dw_child_pcie_ops Zhiqiang Hou
2020-09-16 20:28 ` Rob Herring
2020-09-18 11:02   ` Z.q. Hou
2020-09-18 11:14     ` Michael Walle
2020-09-21 14:48       ` Z.q. Hou
2020-09-18 12:47     ` Bjorn Helgaas
2020-09-21 16:31       ` Z.q. Hou
2020-09-18 15:27     ` Rob Herring
2020-09-24  4:24       ` Z.q. Hou
2020-09-28  9:39         ` Lorenzo Pieralisi
2020-09-29  4:05           ` Z.q. Hou
2020-09-29 15:24             ` Gustavo Pimentel
2020-09-29 17:11               ` Rob Herring
2020-09-30 13:22                 ` Kishon Vijay Abraham I
2020-09-30 15:01                   ` Rob Herring
2020-10-01 13:32                     ` Kishon Vijay Abraham I
2020-10-01 16:46                       ` Michael Walle
2020-10-02  9:29                         ` Naresh Kamboju
2020-10-08 14:46                           ` Naresh Kamboju
2020-10-08 15:12                             ` Rob Herring
2020-10-08 16:51                               ` Naresh Kamboju
2020-10-08 15:08                       ` Lorenzo Pieralisi
2020-10-12 16:31                         ` Kishon Vijay Abraham I
2020-10-12  4:41                       ` Z.q. Hou
2020-10-19 16:13                         ` Lorenzo Pieralisi
2020-10-20  8:07                           ` Kishon Vijay Abraham I
2020-10-12  4:22                 ` Z.q. Hou
2020-10-20  9:48       ` Lorenzo Pieralisi
2020-10-13  9:15 ` Lorenzo Pieralisi
2020-10-14 11:13 ` Lorenzo Pieralisi
2020-10-14 12:37   ` Rob Herring
2020-10-15 22:47 ` Bjorn Helgaas
2020-10-16 11:59   ` Lorenzo Pieralisi
2020-10-19  5:24   ` Z.q. Hou
2020-10-19  5:41     ` Kishon Vijay Abraham I
2020-10-20  2:13       ` Z.q. Hou
2020-10-20  9:12         ` Lorenzo Pieralisi
2020-10-20  9:55         ` Lorenzo Pieralisi
2020-10-21  8:47           ` Z.q. Hou
2020-10-22  6:20             ` Richard Zhu [this message]
2020-10-19 16:26   ` Lorenzo Pieralisi
2020-10-20 10:19   ` Lorenzo Pieralisi

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=VI1PR04MB5853E16DDAC5A382779F63F38C1D0@VI1PR04MB5853.eurprd04.prod.outlook.com \
    --to=hongxing.zhu@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=helgaas@kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=robh@kernel.org \
    --cc=zhiqiang.hou@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).