RE: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-30 Thread bharat.bhus...@freescale.com
65777 > > > Cc: Greg Kroah-Hartman; linuxppc-...@lists.ozlabs.org; linux- > > > ker...@vger.kernel.org > > > Subject: Re: [RESEND PATCH] memory: Freescale CoreNet Coherency > > > Fabric error reporting driver > > > > > > On Wed, 2014-06-04 at 12:04 -05

Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-30 Thread Scott Wood
linux- > > ker...@vger.kernel.org > > Subject: Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error > > reporting driver > > > > On Wed, 2014-06-04 at 12:04 -0500, Bhushan Bharat-R65777 wrote: > > > > > > > -Original Message-

Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-30 Thread Scott Wood
: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver On Wed, 2014-06-04 at 12:04 -0500, Bhushan Bharat-R65777 wrote: -Original Message- From: Wood Scott-B07421 Sent: Wednesday, June 04, 2014 10:12 PM To: Bhushan Bharat-R65777 Cc: Greg

RE: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-30 Thread bharat.bhus...@freescale.com
Subject: Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver On Wed, 2014-06-04 at 12:04 -0500, Bhushan Bharat-R65777 wrote: -Original Message- From: Wood Scott-B07421 Sent: Wednesday, June 04, 2014 10:12 PM To: Bhushan Bharat

RE: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-29 Thread bharat.bhus...@freescale.com
65777 > > > Cc: Greg Kroah-Hartman; linuxppc-...@lists.ozlabs.org; linux- > > > ker...@vger.kernel.org > > > Subject: Re: [RESEND PATCH] memory: Freescale CoreNet Coherency > > > Fabric error reporting driver > > > > > > On Wed, 2014-06-04 at 03:

RE: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-29 Thread bharat.bhus...@freescale.com
Subject: Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver On Wed, 2014-06-04 at 03:17 -0500, Bhushan Bharat-R65777 wrote: +static int ccf_remove(struct platform_device *pdev) { + struct ccf_private *ccf = dev_get_drvdata(pdev-dev

Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-04 Thread Scott Wood
linux- > > ker...@vger.kernel.org > > Subject: Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error > > reporting driver > > > > On Wed, 2014-06-04 at 03:17 -0500, Bhushan Bharat-R65777 wrote: > > > > +static int ccf_remove(struct platform_dev

RE: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-04 Thread bharat.bhus...@freescale.com
> -Original Message- > From: Wood Scott-B07421 > Sent: Wednesday, June 04, 2014 10:12 PM > To: Bhushan Bharat-R65777 > Cc: Greg Kroah-Hartman; linuxppc-...@lists.ozlabs.org; linux- > ker...@vger.kernel.org > Subject: Re: [RESEND PATCH] memory: Freescale CoreNet C

Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-04 Thread Scott Wood
On Wed, 2014-06-04 at 03:17 -0500, Bhushan Bharat-R65777 wrote: > > +struct ccf_err_regs { > > + u32 errdet; /* 0x00 Error Detect Register */ > > + /* 0x04 Error Enable (ccf1)/Disable (ccf2) Register */ > > + u32 errdis; > > + /* 0x08 Error Interrupt Enable Register (ccf2 only)

RE: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-04 Thread bharat.bhus...@freescale.com
rnel.org > Subject: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error > reporting driver > > The CoreNet Coherency Fabric is part of the memory subsystem on some Freescale > QorIQ chips. It can report coherency violations (e.g. > due to misusing memory that is mapped

RE: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-04 Thread bharat.bhus...@freescale.com
PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver The CoreNet Coherency Fabric is part of the memory subsystem on some Freescale QorIQ chips. It can report coherency violations (e.g. due to misusing memory that is mapped noncoherent) as well as transactions that do

Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-04 Thread Scott Wood
On Wed, 2014-06-04 at 03:17 -0500, Bhushan Bharat-R65777 wrote: +struct ccf_err_regs { + u32 errdet; /* 0x00 Error Detect Register */ + /* 0x04 Error Enable (ccf1)/Disable (ccf2) Register */ + u32 errdis; + /* 0x08 Error Interrupt Enable Register (ccf2 only) */ +

RE: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-04 Thread bharat.bhus...@freescale.com
-Original Message- From: Wood Scott-B07421 Sent: Wednesday, June 04, 2014 10:12 PM To: Bhushan Bharat-R65777 Cc: Greg Kroah-Hartman; linuxppc-...@lists.ozlabs.org; linux- ker...@vger.kernel.org Subject: Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting

Re: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-06-04 Thread Scott Wood
: [RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver On Wed, 2014-06-04 at 03:17 -0500, Bhushan Bharat-R65777 wrote: +static int ccf_remove(struct platform_device *pdev) { + struct ccf_private *ccf = dev_get_drvdata(pdev-dev); + + switch

[RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-05-30 Thread Scott Wood
The CoreNet Coherency Fabric is part of the memory subsystem on some Freescale QorIQ chips. It can report coherency violations (e.g. due to misusing memory that is mapped noncoherent) as well as transactions that do not hit any local access window, or which hit a local access window with an

[RESEND PATCH] memory: Freescale CoreNet Coherency Fabric error reporting driver

2014-05-30 Thread Scott Wood
The CoreNet Coherency Fabric is part of the memory subsystem on some Freescale QorIQ chips. It can report coherency violations (e.g. due to misusing memory that is mapped noncoherent) as well as transactions that do not hit any local access window, or which hit a local access window with an