From: Scott Wood <oss@buserror.net>
To: linuxppc-dev@lists.ozlabs.org
Cc: Yangbo Lu <yangbo.lu@nxp.com>,
linux-mmc@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Scott Wood <oss@buserror.net>
Subject: [PATCH v11 5/5] powerpc/fsl-pci: Use fsl_guts_get_svr()
Date: Sat, 16 Jul 2016 21:50:22 -0500 [thread overview]
Message-ID: <1468723822-30457-6-git-send-email-oss@buserror.net> (raw)
In-Reply-To: <1468723822-30457-1-git-send-email-oss@buserror.net>
Establish an initial user of fsl_guts_get_svr(), so that the code gets
some test coverage until users outside arch/powerpc can get converted.
Signed-off-by: Scott Wood <oss@buserror.net>
---
arch/powerpc/Kconfig | 1 +
arch/powerpc/sysdev/fsl_pci.c | 6 +++++-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index fcfe533..765df81 100644
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
@@ -777,6 +777,7 @@ config FSL_PCI
bool
select PPC_INDIRECT_PCI
select PCI_QUIRKS
+ select FSL_GUTS
config FSL_PMC
bool
diff --git a/arch/powerpc/sysdev/fsl_pci.c b/arch/powerpc/sysdev/fsl_pci.c
index 0fd1895..9ba570cf 100644
--- a/arch/powerpc/sysdev/fsl_pci.c
+++ b/arch/powerpc/sysdev/fsl_pci.c
@@ -22,6 +22,7 @@
#include <linux/delay.h>
#include <linux/string.h>
#include <linux/fsl/edac.h>
+#include <linux/fsl/guts.h>
#include <linux/fsl/svr.h>
#include <linux/init.h>
#include <linux/interrupt.h>
@@ -529,7 +530,10 @@ int fsl_add_bridge(struct platform_device *pdev, int is_primary)
struct device_node *dev;
struct ccsr_pci __iomem *pci;
u16 temp;
- u32 svr = mfspr(SPRN_SVR);
+ u32 svr;
+
+ fsl_guts_init();
+ svr = fsl_guts_get_svr();
dev = pdev->dev.of_node;
--
2.7.4
prev parent reply other threads:[~2016-07-17 2:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 2:50 [PATCH v11 0/5] soc: fsl: Add initial guts driver Scott Wood
2016-07-17 2:50 ` [PATCH v11 1/5] dt: bindings: update Freescale DCFG compatible Scott Wood
2016-07-17 2:50 ` [PATCH v11 3/5] soc: fsl: add GUTS driver for QorIQ platforms Scott Wood
[not found] ` <1468723822-30457-1-git-send-email-oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
2016-07-17 2:50 ` [PATCH v11 2/5] dt: bindings: move guts devicetree doc out of powerpc directory Scott Wood
2016-07-17 2:50 ` [PATCH v11 4/5] powerpc/fsl: move mpc85xx.h to include/linux/fsl Scott Wood
2016-07-20 11:24 ` Arnd Bergmann
2016-07-20 18:31 ` Scott Wood
2016-07-20 20:35 ` Arnd Bergmann
2016-07-21 10:26 ` Michael Ellerman
2016-07-21 16:45 ` Scott Wood
[not found] ` <1469119526.25630.42.camel-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
2016-07-21 18:34 ` Arnd Bergmann
2016-07-25 6:12 ` Yangbo Lu
2016-07-27 0:38 ` Scott Wood
2016-08-02 5:57 ` Yangbo Lu
2016-08-02 21:40 ` Scott Wood
[not found] ` <1470174043.25630.233.camel-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
2016-08-03 3:33 ` Yangbo Lu
2016-07-17 2:50 ` Scott Wood [this message]
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=1468723822-30457-6-git-send-email-oss@buserror.net \
--to=oss@buserror.net \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=yangbo.lu@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).