All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, linux-media@vger.kernel.org
Subject: Re: [ANN] Media Summit at ELCE Dublin: Request for Topics
Date: Tue, 24 May 2022 08:16:51 +0100	[thread overview]
Message-ID: <165337661126.402452.10107682065782670158@Monstersaurus> (raw)
In-Reply-To: <325cc388-6f65-0727-92ab-d9b87e7ade1c@xs4all.nl>

Hi Hans,

Quoting Hans Verkuil (2022-05-06 14:20:09)
> Hi all,
> 
> Since countries are opening up again and travel is (at least for now!) a lot easier,
> I am considering a media summit during the ELCE in Dublin (Sep 13-16).
> 
> See here for more details about the conference:
> 
> https://events.linuxfoundation.org/open-source-summit-europe/
> 
> Of course, this only makes sense if there is something to talk about. So please reply
> with any suggestions for topics!
> 
> Also please let me know if you would expect to be at such a media summit in person.
> If only a few people would be there, then there isn't much point to this.
> 
> 
> I have two topics:
> 
> 1) Discussion of the media subsystem development process: any bottlenecks, any ideas
>    for improvements?
> 
> 2) I can give a presentation on the work I've done in the CTA-861 standard (used by
>    HDMI) and the edid-decode utility.
> 
> I'd like to make a decision on whether or not it is worthwhile to do this in a week
> or two. If we wait too long it might be difficult to get a room for the summit.

I would like to bring up the 'fault tolerance' topic again if I can. I
raised this in the past when we first started hitting the issue on
Renesas platforms with multiple cameras in a single media graph, but now
I think it's become more critical with desktop / laptop devices that are
hitting the issue (i.e. the IPU3).

Summary of issue:

 - Multiple cameras that can function independently successfully, are
   prevented from functioning or fully probing by V4L2 if one component
   of another camera fails to load or probe.
  
   If Camera A has a VCM, and Camera B does not, Camera B will not be
   available at all if Camera A's VCM is not fully probed, even though
   Camera B can be fully functional and complete.

   Even if Camera A does not have the VCM probed, it may still function
   successfully (with a fixed focal position) - but our current
   implementation will mean that it will not even be available to
   capture images.

We talked about this quite a long time ago, and I believe the general
consensus was that we can have events on the media graph. But
unfortunately at the time, there was no development scheduled on that,
and it wasn't something I was able to continue at the time.

I'd like to bring it up to refresh the topic, and see if we can make
some progress as it's now affecting more general devices.

--
Kieran



> 
> Regards,
> 
>         Hans

  parent reply	other threads:[~2022-05-24  7:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 13:20 [ANN] Media Summit at ELCE Dublin: Request for Topics Hans Verkuil
2022-05-18 18:01 ` Nicolas Dufresne
2022-09-08  8:45   ` Hans Verkuil
2022-09-08  8:48     ` Hans Verkuil
2022-05-20  8:22 ` Jacopo Mondi
2022-05-24 10:51   ` Dave Stevenson
2022-06-15 12:37     ` Laurent Pinchart
2022-05-24  7:16 ` Kieran Bingham [this message]
2022-06-09 10:29 ` Ricardo Ribalda Delgado
2022-06-15 12:27   ` Laurent Pinchart
2022-06-16 18:45     ` Ricardo Ribalda Delgado
2022-06-16 18:49       ` Laurent Pinchart
2022-06-10 10:37 ` Laurent Pinchart
2022-06-16 18:10 ` Laurent Pinchart
2022-06-17  6:41 ` Hans Verkuil
2022-07-08 11:39   ` Hans Verkuil
2022-07-08 16:44     ` Hans Verkuil

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=165337661126.402452.10107682065782670158@Monstersaurus \
    --to=kieran.bingham@ideasonboard.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.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 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.