linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: linuxppc-dev@ozlabs.org
Cc: Doug Thompson <dougthompson@xmission.com>,
	Dave Jiang <djiang@mvista.com>,
	bluesmoke-devel@lists.sourceforge.net
Subject: [PATCH 2/2] mpc85xx_edac: change to use new definitions for PCI EDAC regspace
Date: Thu, 22 Jul 2010 04:03:12 +0400	[thread overview]
Message-ID: <1279756992-29543-2-git-send-email-dbaryshkov@gmail.com> (raw)
In-Reply-To: <1279756992-29543-1-git-send-email-dbaryshkov@gmail.com>

Currently (as mpc8540-pci) devices are not created on of_platform bus,
mpc85xx_edac can't probe to them. Follow the change to dts trees to bind
not to the main mpc8540-pci node but to special mpc85xx-pci-error nodes,
present on soc bus.

Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
---
 drivers/edac/mpc85xx_edac.c |   18 +++++++++---------
 1 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/drivers/edac/mpc85xx_edac.c b/drivers/edac/mpc85xx_edac.c
index 52ca09b..d5a61b8 100644
--- a/drivers/edac/mpc85xx_edac.c
+++ b/drivers/edac/mpc85xx_edac.c
@@ -236,9 +236,6 @@ static int __devinit mpc85xx_pci_err_probe(struct of_device *op,
 		goto err;
 	}
 
-	/* we only need the error registers */
-	r.start += 0xe00;
-
 	if (!devm_request_mem_region(&op->dev, r.start, resource_size(&r),
 					pdata->name)) {
 		printk(KERN_ERR "%s: Error while requesting mem region\n",
@@ -328,12 +325,15 @@ static int mpc85xx_pci_err_remove(struct of_device *op)
 }
 
 static struct of_device_id mpc85xx_pci_err_of_match[] = {
-	{
-	 .compatible = "fsl,mpc8540-pcix",
-	 },
-	{
-	 .compatible = "fsl,mpc8540-pci",
-	},
+	{ .compatible = "fsl,mpc8536-pci-error", },
+	{ .compatible = "fsl,mpc8540-pci-error", },
+	{ .compatible = "fsl,mpc8541-pci-error", },
+	{ .compatible = "fsl,mpc8544-pci-error", },
+	{ .compatible = "fsl,mpc8548-pci-error", },
+	{ .compatible = "fsl,mpc8555-pci-error", },
+	{ .compatible = "fsl,mpc8560-pci-error", },
+	{ .compatible = "fsl,mpc8568-pci-error", },
+	{ .compatible = "fsl,mpc8572-pci-error", },
 	{},
 };
 
-- 
1.7.1

  reply	other threads:[~2010-07-22  0:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22  0:03 [PATCH 1/2] MPC85xx: add definitions for PCI error detection soc part Dmitry Eremin-Solenikov
2010-07-22  0:03 ` Dmitry Eremin-Solenikov [this message]
2010-07-22 15:38   ` [PATCH 2/2] mpc85xx_edac: change to use new definitions for PCI EDAC regspace Kumar Gala
2010-07-22 16:48     ` Dmitry Eremin-Solenikov
2010-07-22 18:25       ` Scott Wood
2010-07-22 18:40         ` Kumar Gala
2010-07-22 19:03           ` Dmitry Eremin-Solenikov
2010-07-22 19:15             ` Grant Likely
2010-07-22 19:25             ` Scott Wood
2010-07-22 19:10       ` Grant Likely
2010-07-24  0:20         ` Dmitry Eremin-Solenikov
2010-07-24  0:56           ` Grant Likely
2010-07-24 10:09             ` Dmitry Eremin-Solenikov
2010-07-22 15:19 ` [PATCH 1/2] MPC85xx: add definitions for PCI error detection soc part Peter Tyser
2010-07-22 16:56   ` Dmitry Eremin-Solenikov
2010-07-22 17:09     ` Peter Tyser

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=1279756992-29543-2-git-send-email-dbaryshkov@gmail.com \
    --to=dbaryshkov@gmail.com \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=djiang@mvista.com \
    --cc=dougthompson@xmission.com \
    --cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).