Linux Media Controller development
 help / color / mirror / Atom feed
From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	<linux-media@vger.kernel.org>,
	<linux-renesas-soc@vger.kernel.org>
Cc: Michael Rodin <mrodin@de.adit-jv.com>,
	Koji Matsuoka <koji.matsuoka.xm@renesas.com>,
	Eugen Friedrich <efriedrich@de.adit-jv.com>,
	Eugeniu Rosca <erosca@de.adit-jv.com>,
	Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [RFC PATCH v2] media: renesas: vsp1: Add VSPD underrun detection & tracing
Date: Wed, 8 Jun 2022 13:45:35 +0200	[thread overview]
Message-ID: <20220608114535.GA29244@lxhi-065> (raw)
In-Reply-To: <1651584010-10156-1-git-send-email-erosca@de.adit-jv.com>

Dear Laurent,
Dear Kieran,
Dear community,

On Di, Mai 03, 2022 at 03:20:10 +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>
> Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>
> ---

I apologize for another friendly reminder, but is there any chance
to get a bit of attention from your side regarding this patch,
which is intended to make our life easier in production?

I hope the RFC tag does not convey the lack of confidence, importance
and/or time spent for implementation and testing on our side.

This v2 version fixed all review comments and issues which popped up
during internal testing, so I am very hopeful and looking forward to
your precious feedback.

We have also made aware Renesas Japan that this patch is important to
us, hoping that potentially there is another communication bridge
between them and Renesas OSS community.

Best regards,
Eugeniu Rosca

  reply	other threads:[~2022-06-08 11:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 13:20 [RFC PATCH v2] media: renesas: vsp1: Add VSPD underrun detection & tracing Eugeniu Rosca
2022-06-08 11:45 ` Eugeniu Rosca [this message]
2022-06-26 18:46 ` Laurent Pinchart
2022-06-28 19:05   ` Eugeniu Rosca
2022-06-28 19:50     ` Laurent Pinchart
2022-06-28 20:08       ` Geert Uytterhoeven
2022-06-28 20:11         ` Laurent Pinchart
2022-06-29  9:09           ` Eugeniu Rosca
2022-06-29 10:35           ` Kieran Bingham
2022-06-29 11:36             ` Laurent Pinchart

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=20220608114535.GA29244@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