public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Problem with drivers/usb/input/hid-core.c
Date: Sat, 05 Aug 2006 20:08:34 +0100	[thread overview]
Message-ID: <44D4ECB2.5050109@superbug.co.uk> (raw)

Hi,

I tried posting to the linux-usb-devel list, but it seems to have died.

<Extract start>
/*
 * Analyse a received field, and fetch the data from it. The field
 * content is stored for next report processing (we do differential
 * reporting to the layer).
 */

static void hid_input_field(struct hid_device *hid, struct hid_field
*field, __u8 *data, int interrupt, struct pt_regs *regs)

<Extract end>

Why is "differential reporting to the layer" done?

I have a USB device that uses the interrupt urb to notify the PC of
events. Each time an event happens, a usb interrupt is created, and the
driver reads the value from the report. Most of the time the event
contains exactly the same report info as the previous interrupt. As a
result of this differential reporting, I only see the first event, and
then no more until the event changes. How can I get repeated events of
the same report up to user space? I am currently using the
/dev/usb/hiddev0 interface.

Any clues?

For now, I am removing the "differential reporting to the layer" code,
ensuring that all interrupt urbs reach the higher layers.

The "differential reporting" code must be there for a reason, does
anyone know why it is present?

James


             reply	other threads:[~2006-08-05 19:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05 19:08 James Courtier-Dutton [this message]
2006-08-05 20:58 ` Problem with drivers/usb/input/hid-core.c Greg KH

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=44D4ECB2.5050109@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox