linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jeremy Moles <jeremy@emperorlinux.com>
Cc: linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>
Subject: Re: Researching An Experimental Touchscreen Driver
Date: Sat, 27 Nov 2010 21:55:08 -0800	[thread overview]
Message-ID: <20101128055507.GA14499@core.coreip.homeip.net> (raw)
In-Reply-To: <1290917571.1932.15.camel@bathysphere>

On Sat, Nov 27, 2010 at 11:12:51PM -0500, Jeremy Moles wrote:
> 
> WHOA! Now we're cooking! My probe succeeds and now my
> event/input_mapping/input_mapped functions all get called!
> 
> When driver developers are writing HID glue drivers like this, how is it
> you generally determine the contents of your drv_data structure? Via
> hardware specs or is there some way to poke at the device via USB and
> have it tell you? Perhaps this question is a bit TOO out of line, as I'm
> sure that information is available in the standard USB HID
> information...
> 

If you are talking about data structures that are accessed via
hig_get_drvdata() and hid_set_drvdata() then it is entirely up to driver
writer to define them. Basically whatever state you need to be able to
handle the device.

-- 
Dmitry

  reply	other threads:[~2010-11-28  5:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 16:07 Researching An Experimental Touchscreen Driver Jeremy Moles
2010-11-27 22:48 ` Jeremy Moles
2010-11-27 23:51 ` Dmitry Torokhov
2010-11-28  2:23   ` Jeremy Moles
2010-11-28  3:07     ` Dmitry Torokhov
2010-11-28  4:12       ` Jeremy Moles
2010-11-28  5:55         ` Dmitry Torokhov [this message]
2010-11-28  6:38       ` Dmitry Torokhov
2010-11-28 15:38         ` Jiri Kosina

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=20101128055507.GA14499@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=jeremy@emperorlinux.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).