public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Matthias Fend <matthias.fend@emfend.at>
Cc: Rui Miguel Silva <rmfrfs@gmail.com>,
	Martin Kepplinger <martink@posteo.de>,
	Purism Kernel Team <kernel@puri.sm>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	linux-media@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: imx-mipi-csis: avoid logging while holding spinlock
Date: Mon, 29 Jul 2024 12:32:59 +0300	[thread overview]
Message-ID: <20240729093259.GB2320@pendragon.ideasonboard.com> (raw)
In-Reply-To: <3e38bf09-734d-4cbf-a0a5-b01cd1998037@emfend.at>

On Fri, Jul 26, 2024 at 02:16:07PM +0200, Matthias Fend wrote:
> Hi Laurent,
> 
> Am 26.07.2024 um 12:42 schrieb Laurent Pinchart:
> > Hi Matthias,
> > 
> > Thank you for the patch.
> > 
> > On Tue, Jul 23, 2024 at 08:09:08AM +0200, Matthias Fend wrote:
> >> Refactor mipi_csis_log_counters() to prevent calling dev_info() while
> >> IRQs are disabled. This reduces crucial IRQs off time to a bare minimum.
> > 
> > Should we add
> > 
> > Cc: stable@vger.kernel.org
> > 
> > to get this backported to stable kernels ?
> 
> Hard for me to tell. Since this problem only occurs when you explicitly 
> trigger the debug output from this driver, it probably only affects very 
> few end users. So I'm not sure if a backport would be worth it.

I slept over it and decided not to Cc stable.

> >> Signed-off-by: Matthias Fend <matthias.fend@emfend.at>
> >> ---
> >>   drivers/media/platform/nxp/imx-mipi-csis.c | 9 ++++++---
> >>   1 file changed, 6 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/media/platform/nxp/imx-mipi-csis.c b/drivers/media/platform/nxp/imx-mipi-csis.c
> >> index f49b06978f14..0c34d316ed29 100644
> >> --- a/drivers/media/platform/nxp/imx-mipi-csis.c
> >> +++ b/drivers/media/platform/nxp/imx-mipi-csis.c
> >> @@ -857,18 +857,21 @@ static void mipi_csis_log_counters(struct mipi_csis_device *csis, bool non_error
> >>   {
> >>   	unsigned int num_events = non_errors ? MIPI_CSIS_NUM_EVENTS
> >>   				: MIPI_CSIS_NUM_EVENTS - 8;
> >> +	unsigned int counters[MIPI_CSIS_NUM_EVENTS];
> >>   	unsigned long flags;
> >>   	unsigned int i;
> >>   
> >>   	spin_lock_irqsave(&csis->slock, flags);
> >> +	for (i = 0; i < num_events; ++i)
> >> +		counters[i] =  csis->events[i].counter;
> >> +	spin_unlock_irqrestore(&csis->slock, flags);
> >>   
> >>   	for (i = 0; i < num_events; ++i) {
> >> -		if (csis->events[i].counter > 0 || csis->debug.enable)
> >> +		if (counters[i] > 0 || csis->debug.enable)
> >>   			dev_info(csis->dev, "%s events: %d\n",
> >>   				 csis->events[i].name,
> >> -				 csis->events[i].counter);
> >> +				 counters[i]);
> > 
> > The last two lines now fit in a single line. No need for a v2, I'll
> > rewrap the code myself, and add the Cc line if you think that's a good
> > idea.
> 
> Thanks! Regarding Cc, I would like to leave it up to you; you have the 
> necessary experience and overview to judge that.
> 
> ~Matthias
> 
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > 
> >>   	}
> >> -	spin_unlock_irqrestore(&csis->slock, flags);
> >>   }
> >>   
> >>   static int mipi_csis_dump_regs(struct mipi_csis_device *csis)

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2024-07-29  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23  6:09 [PATCH] media: imx-mipi-csis: avoid logging while holding spinlock Matthias Fend
2024-07-25 15:21 ` Rui Miguel Silva
2024-07-26 10:42 ` Laurent Pinchart
2024-07-26 12:16   ` Matthias Fend
2024-07-29  9:32     ` Laurent Pinchart [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=20240729093259.GB2320@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=kernel@puri.sm \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=martink@posteo.de \
    --cc=matthias.fend@emfend.at \
    --cc=mchehab@kernel.org \
    --cc=rmfrfs@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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