From: Antti Palosaari <crope@iki.fi>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 2/7] af9015 Remove call to get config from probe.
Date: Sat, 12 Nov 2011 21:36:04 +0200 [thread overview]
Message-ID: <4EBECAA4.1050400@iki.fi> (raw)
In-Reply-To: <4ebeb95d.e813b40a.37be.5102@mx.google.com>
On 11/12/2011 08:22 PM, Malcolm Priestley wrote:
> On Sat, 2011-11-12 at 18:18 +0200, Antti Palosaari wrote:
>> On 11/12/2011 05:55 PM, Malcolm Priestley wrote:
>>> Remove get config from probe and move to identify_state.
>>>
>>> intf->cur_altsetting->desc.bInterfaceNumber is always expected to be zero, so there
>>> no point in checking for it.
>>
>> Are you sure? IIRC there is HID remote on interface 1 or 2 or so (some
>> other than 0). Please double check.
>>
>>> Calling from probe seems to cause a race condition with some USB controllers.
>>
>> Why?
>>
> Is some other module going to claim the device?
>
> Would it not be better use usb_set_interface to set it back to 0?
>
> Rather than failing it back to the user.
Maybe I don't understand what you mean.
But here is the copy&paste from code:
/* interface 0 is used by DVB-T receiver and
interface 1 is for remote controller (HID) */
if (intf->cur_altsetting->desc.bInterfaceNumber == 0) {
As it says (comment in the code), interface 1 is for remote controller.
I added that to prevent call all that attach stuff twice. I have done
such check for some other drivers too where is multiple interfaces.
IIRC .probe() is called once per each interface device has. So it will
call that two times (if there is HID remote activated), resulting same
device appears two times in bad luck.
Just returning 0 for those probes we don't need sounds good approach for me.
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2011-11-12 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 15:55 [PATCH 2/7] af9015 Remove call to get config from probe Malcolm Priestley
2011-11-12 16:18 ` Antti Palosaari
2011-11-12 18:22 ` Malcolm Priestley
2011-11-12 19:36 ` Antti Palosaari [this message]
2011-11-13 12:04 ` Malcolm Priestley
2011-11-13 12:34 ` Antti Palosaari
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=4EBECAA4.1050400@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=tvboxspy@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