From: Sicelo <absicsz@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] bus: omap_l3_smx: identify timeout source before rebooting
Date: Mon, 31 Jul 2023 10:05:11 +0200 [thread overview]
Message-ID: <ZMdrN7IqJsASyifi@tp440p.steeds.sam> (raw)
In-Reply-To: <20230731052904.GB5194@atomide.com>
Hi,
On Mon, Jul 31, 2023 at 08:29:04AM +0300, Tony Lindgren wrote:
> * Sicelo A. Mhlongo <absicsz@gmail.com> [230730 20:23]:
> > Identify and print the error source before rebooting the board due to an l3
> > application timeout error, by delaying the BUG_ON. This is helpful when
> > debugging, e.g. via serial.
>
> Makes sense to try to show some information, but please see the question
> below.
>
> > diff --git a/drivers/bus/omap_l3_smx.c b/drivers/bus/omap_l3_smx.c
> > index bb1606f5ce2d..70f4903d5468 100644
> > --- a/drivers/bus/omap_l3_smx.c
> > +++ b/drivers/bus/omap_l3_smx.c
> > @@ -170,11 +170,9 @@ static irqreturn_t omap3_l3_app_irq(int irq, void *_l3)
> > status = omap3_l3_readll(l3->rt, L3_SI_FLAG_STATUS_0);
> > /*
> > * if we have a timeout error, there's nothing we can
> > - * do besides rebooting the board. So let's BUG on any
> > - * of such errors and handle the others. timeout error
> > - * is severe and not expected to occur.
> > + * do besides rebooting the board after identifying the
> > + * error source.
> > */
> > - BUG_ON(status & L3_STATUS_0_TIMEOUT_MASK);
> > } else {
> > status = omap3_l3_readll(l3->rt, L3_SI_FLAG_STATUS_1);
> > /* No timeout error for debug sources */
> > @@ -190,6 +188,12 @@ static irqreturn_t omap3_l3_app_irq(int irq, void *_l3)
> > ret |= omap3_l3_block_irq(l3, error, error_addr);
> > }
> >
> > + /*
> > + * BUG on application timeout errors since they are severe and not
> > + * expected to occur.
> > + */
> > + BUG_ON(status & L3_STATUS_0_TIMEOUT_MASK);
>
> Aren't you now checking the bit for both L3_SI_FLAG_STATUS_0 and
> L3_SI_FLAG_STATUS_1 register values? I think it should be only for register
> L3_SI_FLAG_STATUS_0 value?
>
Ah, you are right. It should be:
`BUG_ON(!int_type && status & L3_STATUS_0_TIMEOUT_MASK);`
I'll send in a v2.
Thanks
Sicelo
prev parent reply other threads:[~2023-07-31 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 20:22 [PATCH] bus: omap_l3_smx: identify timeout source before rebooting Sicelo A. Mhlongo
2023-07-31 5:29 ` Tony Lindgren
2023-07-31 8:05 ` Sicelo [this message]
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=ZMdrN7IqJsASyifi@tp440p.steeds.sam \
--to=absicsz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).