All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: Jean-Francois Moine <moinejf@free.fr>,
	V4L Mailing List <linux-media@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: [RFC, PATCH] gspca pac7302: add support for camera button
Date: Mon, 16 Nov 2009 09:43:59 +0100	[thread overview]
Message-ID: <4B0110CF.1060907@redhat.com> (raw)
In-Reply-To: <4B00F804.2090203@freemail.hu>

Hi,

On 11/16/2009 07:58 AM, Németh Márton wrote:
> Hi,
> Hans de Goede wrote:
>> Hi,
>>
>> Thanks for working on this! I think it would be great if we could
>> get support for camera buttons in general into gspca.
>>
>> I've not looked closely at your code yet, have you looked at
>> the camera button code in the gspca sn9c20x.c driver? Also I would really
>
> As you proposed I had a look on sn9c20x. It seems that sn9c20x uses register read
> via USB control message. The pac7302 uses interrupt endpoint. So it looks like
> quite different to me. Currently I see the common point in the connection
> to input subsystem only.
>

Ah you are right, oops, most camera's use an interrupt end point so I assumed
sn9c20x would be the same, my bad.

>> like to see as much of the button handling code as possible go into
>> the gspca core. AFAIK many many camera's use an usb interrupt ep for this, so
>> I would like to see the setting up and cleanup of this interrupt ep be in
>> the core (as said before see the sn9c20x driver for another driver which
>> does such things).
>
> Unfortunately I do not know how the USB descriptors of other webcams look like.
> I have access to two webcams which are handled by gspca:
>

No problem, just put all the input code in pac7302.c for now, we will abstract it
later when we add support for the button on other camera's too.

<snip>

> Comparing these two endpoints shows the common and different points:
> Common: interface class, endpoint direction, endpoint type.
> Different: interface number, sub class, protocol, endpoint address, max
>             packet size, interval.
>
> Maybe the second example is not a good one because I don't know whether
> the interrupt endpoint is used for buttons or not.
>
> Do you have access to webcams equipped with button? Could you please
> send the device descriptor (lsusb -v) about these devices in order
> the common points can be identified for interrupt endpoints?
>

As the author/maintainer of quite a few drivers and libv4l author I have
build up quite a test camera collection, I'll send you the lsusb -v output
of a few in a private mail. But as said before, for now I think you can just put
the input code inside pac7302.c, then later on we can try to abstract it.

Regards,

Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Hans de Goede <hdegoede@redhat.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: Jean-Francois Moine <moinejf@free.fr>,
	V4L Mailing List <linux-media@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: [RFC, PATCH] gspca pac7302: add support for camera button
Date: Mon, 16 Nov 2009 09:43:59 +0100	[thread overview]
Message-ID: <4B0110CF.1060907@redhat.com> (raw)
In-Reply-To: <4B00F804.2090203@freemail.hu>

Hi,

On 11/16/2009 07:58 AM, Németh Márton wrote:
> Hi,
> Hans de Goede wrote:
>> Hi,
>>
>> Thanks for working on this! I think it would be great if we could
>> get support for camera buttons in general into gspca.
>>
>> I've not looked closely at your code yet, have you looked at
>> the camera button code in the gspca sn9c20x.c driver? Also I would really
>
> As you proposed I had a look on sn9c20x. It seems that sn9c20x uses register read
> via USB control message. The pac7302 uses interrupt endpoint. So it looks like
> quite different to me. Currently I see the common point in the connection
> to input subsystem only.
>

Ah you are right, oops, most camera's use an interrupt end point so I assumed
sn9c20x would be the same, my bad.

>> like to see as much of the button handling code as possible go into
>> the gspca core. AFAIK many many camera's use an usb interrupt ep for this, so
>> I would like to see the setting up and cleanup of this interrupt ep be in
>> the core (as said before see the sn9c20x driver for another driver which
>> does such things).
>
> Unfortunately I do not know how the USB descriptors of other webcams look like.
> I have access to two webcams which are handled by gspca:
>

No problem, just put all the input code in pac7302.c for now, we will abstract it
later when we add support for the button on other camera's too.

<snip>

> Comparing these two endpoints shows the common and different points:
> Common: interface class, endpoint direction, endpoint type.
> Different: interface number, sub class, protocol, endpoint address, max
>             packet size, interval.
>
> Maybe the second example is not a good one because I don't know whether
> the interrupt endpoint is used for buttons or not.
>
> Do you have access to webcams equipped with button? Could you please
> send the device descriptor (lsusb -v) about these devices in order
> the common points can be identified for interrupt endpoints?
>

As the author/maintainer of quite a few drivers and libv4l author I have
build up quite a test camera collection, I'll send you the lsusb -v output
of a few in a private mail. But as said before, for now I think you can just put
the input code inside pac7302.c, then later on we can try to abstract it.

Regards,

Hans

  reply	other threads:[~2009-11-16  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15  8:47 [RFC, PATCH] gspca pac7302: add support for camera button Németh Márton
2009-11-15 10:23 ` Hans de Goede
2009-11-15 10:23   ` Hans de Goede
2009-11-16  6:58   ` Németh Márton
2009-11-16  8:43     ` Hans de Goede [this message]
2009-11-16  8:43       ` Hans de Goede

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=4B0110CF.1060907@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    --cc=nm127@freemail.hu \
    /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.