From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-input@vger.kernel.org
Subject: Re: question on device registration
Date: Sat, 21 Mar 2009 10:42:24 -0700 [thread overview]
Message-ID: <200903211042.26685.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <200807022208.57032.oliver@neukum.org>
On Wednesday 02 July 2008 13:08:56 Oliver Neukum wrote:
> Hi,
>
> what happens if you call input_report_key(), input_report_rel() or
> input_sync() for a device before you call input_register_device() ?
>
Well, this surely be a blast from the past for you but I was going
through my old mail...
You can safely use input_report* on an unrefistered input device as
long as it was alloocated with input_allocate_device(). The reported
events will simply be dropped by the input core.
--
Dmitry
prev parent reply other threads:[~2009-03-23 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 20:08 question on device registration Oliver Neukum
2009-03-21 17:42 ` Dmitry Torokhov [this message]
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=200903211042.26685.dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=oliver@neukum.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).