From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Aniroop Mathur <aniroop.mathur@gmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [Question: Drivers/input/evdev.c] What is the use of write function in evdev_fops?
Date: Wed, 13 Aug 2014 10:06:39 -0700 [thread overview]
Message-ID: <20140813170639.GA16164@core.coreip.homeip.net> (raw)
In-Reply-To: <CADYu30-WqEUF-BiefJBo9yWUpKKX_zoLZGXsrJSdC46N8w0OVg@mail.gmail.com>
Hi Aniroop,
On Wed, Aug 13, 2014 at 10:16:34PM +0530, Aniroop Mathur wrote:
> Dear Mr. Torokhov and Linux-Input Community,
> Greetings of the day !! :)
>
> I have not seen some good use of write function in input subsystem.
> I am trying find the good uses of write function in Input subsystem,
> but could not find the solution over internet.
> Can you please help in answering my query below:
>
> As you know, in evdev.c file, fops is defined as below
> struct file_operations evdev_fops = {
> .read = evdev_read,
> .write = evdev_write,
> ...
> }
>
> So in what cases, evdev_write function is used ?
> One case I can think of is that, it can be used in input device simulator
> to write the recorded data back into buffer.
You are right, majority of times you are reading from the buffer. Still,
sometimes you want to control hardware state, for example, toggle keyboard LED.
That can be achieved by writing appropriate event to the event device.
For simulators I think uinput is suited the best.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-08-13 17:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 16:46 [Question: Drivers/input/evdev.c] What is the use of write function in evdev_fops? Aniroop Mathur
2014-08-13 17:06 ` Dmitry Torokhov [this message]
2014-08-13 18:11 ` Aniroop Mathur
2014-08-13 18:58 ` Dmitry Torokhov
2014-08-13 19:10 ` Aniroop Mathur
2014-08-13 19:20 ` Dmitry Torokhov
2014-08-13 19:28 ` Aniroop Mathur
2014-08-13 19:42 ` Dmitry Torokhov
2014-08-13 20:03 ` Aniroop Mathur
2014-08-14 19:25 ` Aniroop Mathur
2014-08-14 20:19 ` Dmitry Torokhov
2014-08-14 20:31 ` Aniroop Mathur
2014-08-18 1:57 ` Peter Hutterer
2014-08-18 16:04 ` Aniroop Mathur
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=20140813170639.GA16164@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=aniroop.mathur@gmail.com \
--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).