All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
To: u-boot@lists.denx.de
Subject: [PATCH v1 1/3] common: ns3: add error logging support
Date: Thu, 20 Aug 2020 20:42:56 +0530	[thread overview]
Message-ID: <CAHO=5PH0VnJC4kvQUnSkr3JECB8G1ooa0D35Ui6PXYn0yFPT6g@mail.gmail.com> (raw)
In-Reply-To: <20200814195238.GY20605@bill-the-cat>

Hi Tom,


On Sat, Aug 15, 2020 at 1:22 AM Tom Rini <trini@konsulko.com> wrote:
>
> On Sun, May 17, 2020 at 02:02:55PM +0530, Rayagonda Kokatanur wrote:
>
> > From: Sheetal Tigadoli <sheetal.tigadoli@broadcom.com>
> >
> > 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 <sheetal.tigadoli@broadcom.com>
> > Signed-off-by: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
>
> 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!

Rebased the patch and sent a v2 patch.

Thanks,
Rayagonda

>
> --
> Tom

  reply	other threads:[~2020-08-20 15:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17  8:32 [PATCH v1 0/3] add elog support for broadcom NS3 soc Rayagonda Kokatanur
2020-05-17  8:32 ` [PATCH v1 1/3] common: ns3: add error logging support Rayagonda Kokatanur
2020-05-25 17:03   ` Simon Glass
2020-08-14 19:52   ` Tom Rini
2020-08-20 15:12     ` Rayagonda Kokatanur [this message]
2020-05-17  8:32 ` [PATCH v1 2/3] board: ns3: kconfig: extend board kconfig with specific commands Rayagonda Kokatanur
2020-05-25 17:03   ` Simon Glass
2020-05-17  8:32 ` [PATCH v1 3/3] cmd: bcm: add broadcom error log setup command Rayagonda Kokatanur
2020-05-25 17:03   ` Simon Glass

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHO=5PH0VnJC4kvQUnSkr3JECB8G1ooa0D35Ui6PXYn0yFPT6g@mail.gmail.com' \
    --to=rayagonda.kokatanur@broadcom.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.