All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the v4l-dvb-next tree
Date: Mon, 6 Dec 2021 10:27:41 +0100	[thread overview]
Message-ID: <20211206102741.209d1e94@coco.lan> (raw)
In-Reply-To: <20211206200639.203bcea3@canb.auug.org.au>

Em Mon, 6 Dec 2021 20:06:39 +1100
Stephen Rothwell <sfr@canb.auug.org.au> escreveu:

> Hi all,
> 
> In commit
> 
>   c1c95d709941 ("media: uvcvideo: Increase UVC_CTRL_CONTROL_TIMEOUT to 5 seconds.")
> 
> Fixes tag
> 
>   Fixes:
> 
> has these problem(s):
> 
>   - No SHA1 recognised
> 
Thanks! This is not actually a fixes tag, just a text to tell what
runtime errors were addressed. 

So, I'm changing the description to:

    media: uvcvideo: Increase UVC_CTRL_CONTROL_TIMEOUT to 5 seconds.
    
    Some uvc devices appear to require the maximum allowed USB timeout
    for GET_CUR/SET_CUR requests.
    
    So lets just bump the UVC control timeout to 5 seconds which is the
    same as the usb ctrl get/set defaults:
    USB_CTRL_GET_TIMEOUT 5000
    USB_CTRL_SET_TIMEOUT 5000
    
    It fixes the following runtime warnings:
       Failed to query (GET_CUR) UVC control 11 on unit 2: -110 (exp. 1).
       Failed to query (SET_CUR) UVC control 3 on unit 2: -110 (exp. 2).


in order to make it clearer.

Thanks,
Mauro

  reply	other threads:[~2021-12-06  9:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06  9:06 linux-next: Fixes tag needs some work in the v4l-dvb-next tree Stephen Rothwell
2021-12-06  9:27 ` Mauro Carvalho Chehab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-30 21:55 Stephen Rothwell
2023-07-31 22:29 ` Sakari Ailus
2023-07-16 21:53 Stephen Rothwell
2023-03-20 21:23 Stephen Rothwell
2023-03-20 21:50 ` Sakari Ailus
2023-02-06 21:08 Stephen Rothwell
2022-05-13  8:49 Stephen Rothwell
2022-05-08 22:26 Stephen Rothwell
2022-05-08 22:54 ` Laurent Pinchart
2021-10-18 20:40 Stephen Rothwell
2021-07-22 22:51 Stephen Rothwell
2021-07-23  0:38 ` Yizhuo Zhai
2021-07-23  0:58   ` Stephen Rothwell
2021-07-23  2:19     ` Yizhuo Zhai
2021-07-23  7:04   ` Mauro Carvalho Chehab
2021-06-17 10:54 Stephen Rothwell
2021-05-23  2:49 Stephen Rothwell
2021-05-23  8:36 ` Sean Young
2021-05-23  9:30   ` Mauro Carvalho Chehab
2020-06-11 21:17 Stephen Rothwell

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=20211206102741.209d1e94@coco.lan \
    --to=mchehab@kernel.org \
    --cc=james.hilliard1@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.