[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140822050737.GD11381@nazgul.tnic>
Date: Fri, 22 Aug 2014 07:07:37 +0200
From: Borislav Petkov <bp@...en8.de>
To: Pranith Kumar <bobby.prani@...il.com>,
Grant Erickson <gerickson@...vations.com>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
Doug Thompson <dougthompson@...ssion.com>,
Mauro Carvalho Chehab <m.chehab@...sung.com>,
"open list:LINUX FOR POWERPC..." <linuxppc-dev@...ts.ozlabs.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:EDAC-CORE" <linux-edac@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] powerpc: edac: Fix build error
On Thu, Aug 21, 2014 at 10:19:51PM -0400, Pranith Kumar wrote:
> Fix the following build error:
>
> drivers/edac/ppc4xx_edac.c: In function 'mfsdram':
> drivers/edac/ppc4xx_edac.c:249: error: implicit declaration of function
> '__mfdcri'
> drivers/edac/ppc4xx_edac.c: In function 'mtsdram':
> drivers/edac/ppc4xx_edac.c:266: error: implicit declaration of function
> '__mtdcri'
> drivers/edac/ppc4xx_edac.c:269: warning: 'return' with a value, in function
> returning void
> drivers/edac/ppc4xx_edac.c: In function 'ppc4xx_edac_init_csrows':
> drivers/edac/ppc4xx_edac.c:924: warning: initialization from incompatible
> pointer type
> drivers/edac/ppc4xx_edac.c:977: error: request for member 'dimm' in something
> not a structure or union
> drivers/edac/ppc4xx_edac.c: In function 'ppc4xx_edac_map_dcrs':
> drivers/edac/ppc4xx_edac.c:1209: warning: passing argument 1 of 'dcr_map_mmio'
> discards qualifiers from pointer target type
>
> This driver depends on PPC_DCR_NATIVE to be set for the relevant headers to be
> included. Also if PPC_DCR_MMIO=n the build fails. So make PPC_DCR depend on both
> these options.
>
> This is compile tested only.
This driver has been carried through the years from misc people after
its initial drop in 2009. And frankly, I'd prefer if someone with the
hardware could actually test it before we break it any further.
Alternatively, if it is obsolete and no one uses it, we could very well
delete it instead. Initial commit talks about the hw it supports:
dba7a77c0e40 ("edac: new ppc4xx driver module")
So it would be good if we got some opinions from the PPC crowd. Who are
on CC.
(leaving in the rest for context).
>
> Signed-off-by: Pranith Kumar <bobby.prani@...il.com>
> CC: Andrew Morton <akpm@...ux-foundation.org>
> ---
> arch/powerpc/Kconfig | 6 +++---
> drivers/edac/ppc4xx_edac.c | 8 ++++----
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 4bc7b62..9b90c1c 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -233,15 +233,15 @@ config ARCH_SUSPEND_POSSIBLE
>
> config PPC_DCR_NATIVE
> bool
> - default n
> + default y
>
> config PPC_DCR_MMIO
> bool
> - default n
> + default y
>
> config PPC_DCR
> bool
> - depends on PPC_DCR_NATIVE || PPC_DCR_MMIO
> + depends on PPC_DCR_NATIVE && PPC_DCR_MMIO
> default y
>
> config PPC_OF_PLATFORM_PCI
> diff --git a/drivers/edac/ppc4xx_edac.c b/drivers/edac/ppc4xx_edac.c
> index ef6b7e0..8725b73 100644
> --- a/drivers/edac/ppc4xx_edac.c
> +++ b/drivers/edac/ppc4xx_edac.c
> @@ -246,8 +246,8 @@ static const char * const ppc4xx_plb_masters[9] = {
> static inline u32
> mfsdram(const dcr_host_t *dcr_host, unsigned int idcr_n)
> {
> - return __mfdcri(dcr_host->base + SDRAM_DCR_ADDR_OFFSET,
> - dcr_host->base + SDRAM_DCR_DATA_OFFSET,
> + return __mfdcri(dcr_host->host.native.base + SDRAM_DCR_ADDR_OFFSET,
> + dcr_host->host.native.base + SDRAM_DCR_DATA_OFFSET,
> idcr_n);
> }
>
> @@ -263,8 +263,8 @@ mfsdram(const dcr_host_t *dcr_host, unsigned int idcr_n)
> static inline void
> mtsdram(const dcr_host_t *dcr_host, unsigned int idcr_n, u32 value)
> {
> - return __mtdcri(dcr_host->base + SDRAM_DCR_ADDR_OFFSET,
> - dcr_host->base + SDRAM_DCR_DATA_OFFSET,
> + return __mtdcri(dcr_host->host.native.base + SDRAM_DCR_ADDR_OFFSET,
> + dcr_host->host.native.base + SDRAM_DCR_DATA_OFFSET,
> idcr_n,
> value);
> }
> --
> 1.9.1
>
>
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists