From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: <linux-media@vger.kernel.org>, <linux-renesas-soc@vger.kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Koji Matsuoka <koji.matsuoka.xm@renesas.com>,
Michael Rodin <mrodin@de.adit-jv.com>,
Eugen Friedrich <efriedrich@de.adit-jv.com>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [RFC] media: renesas: vsp1: Add VSPD underrun detection & tracing
Date: Tue, 3 May 2022 15:27:36 +0200 [thread overview]
Message-ID: <20220503132736.GA10237@lxhi-065> (raw)
In-Reply-To: <1650962227-14281-1-git-send-email-erosca@de.adit-jv.com>
On Di, Apr 26, 2022 at 10:37:07 +0200, Eugeniu Rosca wrote:
> A barely noticeable (especially if hardly reproducible) display flicker
> may not be the biggest concern in the development environment. However,
> an automotive OEM will not only notice it, but will also be haunted by
> its phenomenon/nature till it is understood in the greatest detail and
> ultimately eradicated, to avoid impairing user experience.
>
> Troubleshooting the above without the right tools becomes a nightmare.
>
> Since VSPD underruns may indeed cause [1] display flicker, we believe
> that having a minimal/lightweight support for detecting and logging
> such events would be extremely beneficial. Obviously, this only applies
> to VSP2 modules having an interface to DU (i.e. not mem2mem).
>
> This implementation is heavily inspired by Koji Matsuoka's work [2-3],
> but has been refactored to hopefully become production/mainline-friendly
> (the original feature is intended for the development environment only).
>
> [1] https://lore.kernel.org/linux-renesas-soc/20220421161259.GA2660@lxhi-065
> [2] https://github.com/renesas-rcar/linux-bsp/commit/3469001c3098
> ("v4l: vsp1: Add underrun hung-up workaround")
> [3] https://github.com/renesas-rcar/linux-bsp/commit/12ea79975a10
> ("v4l: vsp1: Add underrun debug messege option")
>
> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>
> Cc: Koji Matsuoka <koji.matsuoka.xm@renesas.com>
Superseded by https://lore.kernel.org/linux-renesas-soc/1651584010-10156-1-git-send-email-erosca@de.adit-jv.com
Best regards,
Eugeniu
next prev parent reply other threads:[~2022-05-03 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 8:37 [RFC] media: renesas: vsp1: Add VSPD underrun detection & tracing Eugeniu Rosca
2022-05-03 13:27 ` Eugeniu Rosca [this message]
2022-05-11 11:12 ` Eugeniu Rosca
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=20220503132736.GA10237@lxhi-065 \
--to=erosca@de.adit-jv.com \
--cc=efriedrich@de.adit-jv.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=koji.matsuoka.xm@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mrodin@de.adit-jv.com \
--cc=roscaeugeniu@gmail.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