From: Hans de Goede <hdegoede@redhat.com>
To: Antonio Ospite <ao2@ao2.it>
Cc: linux-media@vger.kernel.org, Alexander Sosna <alexander@xxor.de>
Subject: Re: [RFC 1/2] gspca: provide a mechanism to select a specific transfer endpoint
Date: Tue, 24 Jun 2014 16:16:51 +0200 [thread overview]
Message-ID: <53A98853.10307@redhat.com> (raw)
In-Reply-To: <20140624153558.c0a933633fdb8bb20977918a@ao2.it>
Hi,
On 06/24/2014 03:35 PM, Antonio Ospite wrote:
> On Thu, 19 Jun 2014 16:27:59 +0200
> Hans de Goede <hdegoede@redhat.com> wrote:
>
>> Hi Antonio,
>>
>> Thanks for working on this.
>>
>> On 06/04/2014 10:24 PM, Antonio Ospite wrote:
>>> Add a xfer_ep_index field to struct gspca_dev, and change alt_xfer() so
>>> that it accepts a parameter which represents a specific endpoint to look
>>> for.
>>>
>>> If a subdriver wants to specify a value for gspca_dev->xfer_ep_index it
>>> can do that in its sd_config() callback.
>>>
>>> Signed-off-by: Antonio Ospite <ao2@ao2.it>
>>> ---
>>>
>>> I am not sure if it is OK to specify an endpoint _index_ or if it would be
>>> better to specify the endpoint address directly (in Kinect 0x81 is for video
>>> data and 0x82 is for depth data).
>>>
>>> Hans, any comment on that?
>>
>> I think it would be better to use the endpoint address directly for this,
>> relying on the order in which the endpoints are listed in the descriptor
>> feels wrong to me.
>>
>
> I see.
>
> If I declare the new field as __u8 (same type of a bEndpointAddress), I
> could mark an invalid ep address with ~(USB_ENDPOINT_DIR_MASK |
> USB_ENDPOINT_NUMBER_MASK) in gspca_dev_probe2(), instead of using an
> int set to -1; how does that sound?
I would prefer an int with a simple -1 value of invalid.
Regards,
Hans
next prev parent reply other threads:[~2014-06-24 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 18:13 gspca second isoc endpoint / kinect depth Alexander Sosna
2014-04-09 9:05 ` Hans de Goede
2014-06-04 20:24 ` [RFC 0/2] gspca_kinect: add support for the depth stream Antonio Ospite
2014-06-04 20:24 ` [RFC 1/2] gspca: provide a mechanism to select a specific transfer endpoint Antonio Ospite
2014-06-19 14:27 ` Hans de Goede
2014-06-24 13:35 ` Antonio Ospite
2014-06-24 14:16 ` Hans de Goede [this message]
2014-06-04 20:24 ` [RFC 2/2] gspca_kinect: add support for the depth stream Antonio Ospite
2014-06-19 14:35 ` Hans de Goede
2014-06-25 8:00 ` Antonio Ospite
2014-06-25 9:27 ` [PATCH 0/2] gspca, " Antonio Ospite
2014-06-25 9:27 ` [PATCH 1/2] gspca: provide a mechanism to select a specific transfer endpoint Antonio Ospite
2014-06-25 9:27 ` [PATCH 2/2] gspca_kinect: add support for the depth stream Antonio Ospite
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=53A98853.10307@redhat.com \
--to=hdegoede@redhat.com \
--cc=alexander@xxor.de \
--cc=ao2@ao2.it \
--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.