From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shengzhou Liu Date: Tue, 24 May 2016 05:15:35 +0000 Subject: [U-Boot] [PATCH] driver/ddr/fsl: Force enabling parity for A-009803 In-Reply-To: <574322B7.1030508@nxp.com> References: <1463731546-15232-1-git-send-email-Shengzhou.Liu@nxp.com> <573F2D49.9050102@nxp.com> <574322B7.1030508@nxp.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de > -----Original Message----- > From: York Sun [mailto:york.sun at nxp.com] > Sent: Monday, May 23, 2016 11:33 PM > To: Shengzhou Liu ; u-boot at lists.denx.de > Subject: Re: [PATCH] driver/ddr/fsl: Force enabling parity for A-009803 > Shengzhou, > > My point is you should force ap=1. Do you mean if ERRATUM_A009803 is > enabled, users are forced to use address parity? That doesn't sound right. > We have been running UDIMM without address parity for a long time. > > York > York, My understanding is that ERRATUM_A009803 may still happen whatever ap_en is enabled or disabled. To apply the workaround of A009803, it requires ap_en is enabled. Is your understanding that if we disable ap_en, ERRATUM_A009803 will never happen? The CE document doesn't explain clearly this. In last mail, did you mean we should force ap_en = 0 in case of A-009803? Shengzhou