linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Reimer <mail+linux-input@m-reimer.de>
To: linux-input@vger.kernel.org
Subject: uinput: ioctls for UI_BEGIN_FF_UPLOAD fails (returns -1). How to debug?
Date: Sun, 27 Mar 2016 20:53:54 +0200	[thread overview]
Message-ID: <56F82C42.6020002@m-reimer.de> (raw)

Hello,

I'm writing on an usermode input driver.

Currently my force feedback support just consists of some printf's as a 
first try.

My problem is, that it seems like as soon as I first sent something to 
my open uinput device (some buttons that were pressed on the device) the 
uinput backend seems to get into some bad state.

My "force feedback thread" gets the "EV_UINPUT" event trigger, but if I 
try to call

ioctl(args->fduinput, UI_BEGIN_FF_UPLOAD, &upload);

in this case, then the return value is "-1"...

The same code works without any problem if no buttons are pressed and 
"fftest" is called directly after startup of the driver application.

Can someone help me with debugging this problem? My understanding is, 
that this call shouldn't return -1 if the "EV_UINPUT" event was 
successfully received, right?

My system:

$ uname -a
Linux manuelspc 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 
x86_64 GNU/Linux

Thank you very much in advance.

Manuel

             reply	other threads:[~2016-03-27 18:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-27 18:53 Manuel Reimer [this message]
2016-03-27 19:11 ` uinput: ioctls for UI_BEGIN_FF_UPLOAD fails (returns -1). How to debug? Clément VUCHENER
2016-03-28  8:53   ` Manuel Reimer
2016-03-29 10:21     ` Clément VUCHENER
2016-03-29 16:48       ` Manuel Reimer
2016-03-31 17:46         ` Manuel Reimer
2016-04-03 10:02           ` Manuel Reimer
2016-04-03 10:21             ` Clément VUCHENER
2016-04-05 19:10               ` Manuel Reimer

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=56F82C42.6020002@m-reimer.de \
    --to=mail+linux-input@m-reimer.de \
    --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).