public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Shaobo He <shaobo@cs.utah.edu>
Cc: linux-media@vger.kernel.org
Subject: Re: Question about drivers/media/usb/uvc/uvc_v4l2.c
Date: Tue, 5 Mar 2019 22:07:14 +0200	[thread overview]
Message-ID: <20190305200714.GL14928@pendragon.ideasonboard.com> (raw)
In-Reply-To: <3bfdd00d-abff-8683-6e25-1010cc568702@cs.utah.edu>

Hello Shoabo,

On Sat, Mar 02, 2019 at 03:29:25PM -0700, Shaobo He wrote:
> Hi Laurent,
> 
> Thank you very much for your reply. This is what I thought, too. It seems that 
> there's an implicit order of execution that is not clearly implied in the code, 
> meaning `uvc_parse_streaming` is called before `uvc_v4l2_try_format`.

It is implied by the logic of the driver that calls
uvc_parse_streaming() at probe time before registering video nodes, and
with uvc_v4l2_try_format() only being called from userspace through the
video nodes.

> That being said, I was wondering maybe a better practice to write the loop in 
> `uvc_v4l2_try_format` would be like the following,
> 
> ```
> format=NULL;
> ...
> for (i = 0; i < stream->nformats; ++i) {
> 		format = &stream->format[i];
> 		if (format->fcc == fmt->fmt.pix.pixelformat)
> 			break;
> }
> // dereferencing format
> ```
> to
> ```
> // just declaration
> format;
> i=0;
> do {
> 		format = &stream->format[i];
> 		if (format->fcc == fmt->fmt.pix.pixelformat)
> 			break;
> 		++i;
> } while (i<stream->nformats)
> // dereferencing format
> ```
> I mean you can save one initialization, provided compiler does it and one branch.

I like for loops better in general, they convey the meaning in a cleaner
way. The compiler should be able to do its job here and optimize the
code correctly, I don't think a change is worth it, especially as we're
not dealing with a hot path.

> On 2019/3/2 14:43, Laurent Pinchart wrote:
> > On Sat, Mar 02, 2019 at 01:22:49PM -0700, Shaobo He wrote:
> >> Hello everyone,
> >>
> >> This is Shaobo from Utah again. I've been bugging the mailing list with my
> >> patches. I have a quick question about a function in
> >> `drivers/media/usb/uvc/uvc_v4l2.c`. In `uvc_v4l2_try_format`, can
> >> `stream->nformats` be 0? I saw that in other files, this field could be zero
> >> which is considered as error cases. I was wondering if it's true for this
> >> function, too.
> > 
> > The uvc_parse_streaming() function should answer this question :-)

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2019-03-05 20:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 20:22 Question about drivers/media/usb/uvc/uvc_v4l2.c Shaobo He
2019-03-02 21:43 ` Laurent Pinchart
2019-03-02 22:29   ` Shaobo He
2019-03-05 20:07     ` 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=20190305200714.GL14928@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=shaobo@cs.utah.edu \
    /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