mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Rick L. Vinyard, Jr." <rvinyard@cs.nmsu.edu>
Cc: Linux USB <linux-usb@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Problem starting the input interrupt pipe on the G13
Date: Wed, 2 Sep 2009 17:50:51 -0700	[thread overview]
Message-ID: <20090903005051.GA6733@kroah.com> (raw)
In-Reply-To: <a571ebde1bc221dd250a03e9fb33ed66.squirrel@intranet.cs.nmsu.edu>

On Wed, Sep 02, 2009 at 03:25:50PM -0600, Rick L. Vinyard, Jr. wrote:
> Hello,
> 
> I'm still working on the G13 driver, but I've run into a problem with the
> interrupt in pipe. In essence, I can't figure out how to get it started.
> 
> The driver can be found at:
> http://g13.svn.sourceforge.net/viewvc/g13/driver/trunk/
> 
> I think the root of the problem lies in the fact that the G13 usage page
> is 0x00 (undefined). The output and feature reports seem to be working
> fine to set the backlight color, the LCD image and the leds on the 'M'
> keys.
> 
> However, nothing seems to be happening with the input report (there is
> only one input report type on endpoint address 0x81 that contains the
> joystick and key values).
> 
> The problem is getting the input pipe started. I grepped through the other
> drivers in the hid directory and I couldn't find any that had to
> explicitly start the input interrupt.

Have you just submitted an interrupt urb?

That should be all that is needed, when the device has data, it will
return with it if your urb is pending.

thanks,

greg k-h

  reply	other threads:[~2009-09-03  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 21:25 Rick L. Vinyard, Jr.
2009-09-03  0:50 ` Greg KH [this message]
2009-09-03 14:12   ` Rick L. Vinyard, Jr.
2009-09-03 14:35     ` Rick L. Vinyard, Jr.

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=20090903005051.GA6733@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rvinyard@cs.nmsu.edu \
    /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

all inboxes | Powered by JetHome®