From: Hans de Goede <hdegoede@redhat.com>
To: "Erik Andrén" <erik.andren@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Lee Jones <lee.jones@canonical.com>,
Jean-Francois Moine <moinejf@free.fr>
Subject: Re: [PATCH 3/7] gspca-stv06xx: support bandwidth changing
Date: Wed, 27 Oct 2010 15:17:12 +0200 [thread overview]
Message-ID: <4CC82658.3040205@redhat.com> (raw)
In-Reply-To: <AANLkTi=tiYJU0fLVqSiN-BRGgMqcf3eF0jFFVDTtr-Lh@mail.gmail.com>
Hi,
On 10/27/2010 02:39 PM, Erik Andrén wrote:
> 2010/10/27 Hans de Goede<hdegoede@redhat.com>:
>> stv06xx devices have only one altsetting, but the actual used
>> bandwidth can be programmed through a register. We were already
>> setting this register lower then the max packetsize of the altsetting
>> indicates. This patch makes the gspca-stv06xx update the usb descriptor
>> for the alt setting to reflect the actual packetsize in use, so that
>> the usb subsystem uses the correct information for scheduling usb transfers.
>>
>> This patch also tries to fallback to lower speeds in case a ENOSPC error
>> is received when submitting urbs, but currently this is only supported
>> with stv06xx cams with the pb0100 sensor, as this is the only one for
>> which we know how to change the framerate.
>>
>> This patch is based on an initial incomplete patch by
>> Lee Jones<lee.jones@canonical.com>
>>
>> Signed-off-by: Lee Jones<lee.jones@canonical.com>
>> Signed-off-by: Hans de Goede<hdegoede@redhat.com>
>
> Cool,
> Has this been verified to work with all affected devices?
Yes and no, it has been verified with a camera with a st6422 sensor
and one with a pb0100 sensor. It has not been verified with the others, but
it makes no changes to the others. See min and max bandwidth settings in
the sensor struct in the sensors .h file (and the FIXME comments there).
These result in the STV_ISO_SIZE_L register setting being left untouched
for the untested devices, effectively making this patch a nop for them.
Except that the usb core will be told that some of them do not use the full
bandwidth, which will allow peaceful coexistence with other devices.
AFAIK you have a vv6410 sensor camera, it would be cool if you could:
1) See if you can vary the framerate of it
2) See what the minimum required bandwidth is for each framerate
(change min and max packet_size to be the same to test).
3) Update max and min packetsize (to reflect the minimum needed
packetsize at the highest. resp lowest framerate).
4) Update the sensor_start function to program the framerate depending
on the available bandwidth (see the pb0100 code).
Thanks & Regards,
Hans
next prev parent reply other threads:[~2010-10-27 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 12:35 [GIT PATCHES FOR 2.6.37] Various gspca patches Hans de Goede
2010-10-27 12:35 ` [PATCH 1/7] gspca: submit interrupt urbs *after* isoc urbs Hans de Goede
2010-10-27 12:35 ` [PATCH 2/7] gspca: only set gspca->int_urb if submitting it succeeds Hans de Goede
2010-10-27 12:35 ` [PATCH 3/7] gspca-stv06xx: support bandwidth changing Hans de Goede
2010-10-27 12:39 ` Erik Andrén
2010-10-27 13:17 ` Hans de Goede [this message]
2010-10-27 12:35 ` [PATCH 4/7] gspca_xirlink_cit: various usb bandwidth allocation improvements / fixes Hans de Goede
2010-10-27 12:35 ` [PATCH 5/7] gspca_xirlink_cit: Frames have a 4 byte footer Hans de Goede
2010-10-27 12:35 ` [PATCH 6/7] gspca_xirlink_cit: Add support camera button Hans de Goede
2010-10-27 12:35 ` [PATCH 7/7] gspca_ov519: generate release button event on stream stop if needed Hans de Goede
2010-11-09 15:09 ` [GIT PATCHES FOR 2.6.37] Various gspca patches Mauro Carvalho Chehab
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=4CC82658.3040205@redhat.com \
--to=hdegoede@redhat.com \
--cc=erik.andren@gmail.com \
--cc=lee.jones@canonical.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=moinejf@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).