From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Sun Date: Thu, 19 Mar 2015 12:54:59 -0700 Subject: [U-Boot] [PATCH 17/28] armv8/fsl-lsch3: Enable system error aborts In-Reply-To: <1426794750.27998.139.camel@freescale.com> References: <1426783559-26610-1-git-send-email-yorksun@freescale.com> <1426783559-26610-17-git-send-email-yorksun@freescale.com> <20150319181433.GH10153@leverpostej> <1426794750.27998.139.camel@freescale.com> Message-ID: <550B2993.9060206@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 03/19/2015 12:52 PM, Scott Wood wrote: > On Thu, 2015-03-19 at 18:14 +0000, Mark Rutland wrote: >> On Thu, Mar 19, 2015 at 04:45:48PM +0000, York Sun wrote: >>> From: Scott Wood >>> >>> This lets us see the problems (close to) when they happen, >>> rather than Linux hanging when it enables them prior to having a >>> working console. >> >> FYI, if the Linux driver for your UART supports earlycon, that should >> work since commit 7a9c43bed891d1f8 ("setup: Move unmask of async >> interrupts after possible earlycon setup"). > > I wrote this patch in the context of board bringup, where I was stuck > using an older kernel. In any case, when U-Boot causes a problem we > want to see it in U-Boot. > >> I hope that SError is masked again prior to entering Linux, as required >> by the boot protocol? > > Doesn't look like it based on grepping for daifset. > > Where is the boot protocol documented? Just for future reference -- I > agree that leaving this enabled during the handover would be a bad > thing. > >> Mark. >> >>> Signed-off-by: Scott Wood > > York, where's your signoff since you're the one submitting the patch? I am sending many patches in this set. Since I didn't contribute to this patch, I didn't add my signed-off-by. York