LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shaohui Xie <Shaohui.Xie@freescale.com>
To: <linuxppc-dev@lists.ozlabs.org>
Cc: kumar.gala@freescale.com, "Kai.Jiang" <Kai.Jiang@freescale.com>,
	Shaohui Xie <Shaohui.Xie@freescale.com>
Subject: [PATCH 3/4] powerpc/85xx: Merge PCI/PCI Express error management registers
Date: Thu, 21 Jul 2011 18:29:55 +0800	[thread overview]
Message-ID: <1311244195-4418-1-git-send-email-Shaohui.Xie@freescale.com> (raw)

From: Kai.Jiang <Kai.Jiang@freescale.com>

There are some differences of register offset and definition between
pci and pcie error management registers. While, some other pci/pcie
error management registers are nearly the same.

Signed-off-by: Kai.Jiang <Kai.Jiang@freescale.com>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Shaohui Xie <Shaohui.Xie@freescale.com>
---
 arch/powerpc/sysdev/fsl_pci.h |   31 +++++++++++++++++++++++++------
 1 files changed, 25 insertions(+), 6 deletions(-)

difg --gite a/arch/powerpc/sysdev/fsl_pci.h b/arch/powerpc/sysdev/fsl_pci.h
index a39ed5c..60a76e9 100644
--- a/arch/powerpc/sysdev/fsl_pci.h
+++ b/arch/powerpc/sysdev/fsl_pci.h
@@ -74,13 +74,32 @@ struct ccsr_pci {
  */
 	struct pci_inbound_window_regs piw[4];
 
+/* Merge PCI/PCI Express error management registers */
 	__be32	pex_err_dr;		/* 0x.e00 - PCI/PCIE error detect register */
-	u8	res21[4];
-	__be32	pex_err_en;		/* 0x.e08 - PCI/PCIE error interrupt enable register */
-	u8	res22[4];
-	__be32	pex_err_disr;		/* 0x.e10 - PCI/PCIE error disable register */
-	u8	res23[12];
-	__be32	pex_err_cap_stat;	/* 0x.e20 - PCI/PCIE error capture status register */
+	__be32	pex_err_cap_dr;		/* 0x.e04 */
+					/* - PCI error capture disabled register */
+					/* - PCIE has no this register */
+	__be32	pex_err_en;		/* 0x.e08 */
+					/* - PCI/PCIE error interrupt enable register*/
+	__be32	pex_err_attrib;		/* 0x.e0c */
+					/* - PCI error attributes capture register */
+					/* - PCIE has no this register */
+	__be32	pex_err_disr;		/* 0x.e10 */
+					/* - PCI error address capture register */
+					/* - PCIE error disable register */
+	__be32	pex_err_ext_addr;	/* 0x.e14 */
+					/* - PCI error extended addr capture register*/
+					/* - PCIE has no this register */
+	__be32	pex_err_dl;		/* 0x.e18 */
+					/* - PCI error data low capture register */
+					/* - PCIE has no this register */
+	__be32	pex_err_dh;		/* 0x.e1c */
+					/* - PCI error data high capture register */
+					/* - PCIE has no this register */
+	__be32	pex_err_cap_stat;	/* 0x.e20 */
+					/* - PCI gasket timer register */
+					/* - PCIE error capture status register */
+
 	u8	res24[4];
 	__be32	pex_err_cap_r0;		/* 0x.e28 - PCIE error capture register 0 */
 	__be32	pex_err_cap_r1;		/* 0x.e2c - PCIE error capture register 0 */
-- 
1.6.4

             reply	other threads:[~2011-07-21 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 10:29 Shaohui Xie [this message]
2011-07-21 15:58 ` [PATCH 3/4] powerpc/85xx: Merge PCI/PCI Express error management registers Tabi Timur-B04825
2011-07-22  2:56   ` Xie Shaohui-B21989
2011-07-26  6:48 ` Xie Shaohui-B21989
2011-08-03  9:57 ` Xie Shaohui-B21989

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=1311244195-4418-1-git-send-email-Shaohui.Xie@freescale.com \
    --to=shaohui.xie@freescale.com \
    --cc=Kai.Jiang@freescale.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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