From: Tom Rini Date: Fri, 14 Aug 2020 15:52:38 -0400 Subject: [PATCH v1 1/3] common: ns3: add error logging support In-Reply-To: <20200517083257.22191-2-rayagonda.kokatanur@broadcom.com> References: <20200517083257.22191-1-rayagonda.kokatanur@broadcom.com> <20200517083257.22191-2-rayagonda.kokatanur@broadcom.com> Message-ID: <20200814195238.GY20605@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sun, May 17, 2020 at 02:02:55PM +0530, Rayagonda Kokatanur wrote: > From: Sheetal Tigadoli > > Add error logging support in uboot for ns3 platform. > > We log the bootup msgs from all bootstages(BL2, BL31, BL33, and Linux) > on to DDR. When a watchdog is triggered from any of the bootstages, > CRMU copies these logs to QSPI error logging space. > > Later when doing the post-mortem analysis, we parse the QSPI error > log space. > > Signed-off-by: Sheetal Tigadoli > Signed-off-by: Rayagonda Kokatanur This, and the series that starts with "cmd: bcm: add nitro boot command" seem to conflict. Can you please resubmit any further outstanding patches? Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: