From: Daniel Mack <daniel@caiaq.de>
To: linux-kernel@vger.kernel.org
Cc: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org
Subject: [RFC] linux-input: dynamically allocate ABS axis information
Date: Wed, 19 May 2010 19:22:33 +0200 [thread overview]
Message-ID: <1274289757-2723-1-git-send-email-daniel@caiaq.de> (raw)
To support more axis on input devices, we should dynamically allocate
ABS axis information. Currently, six values (value, min, max, fuzz,
flat and resolution) are stored in arrays, each of ABS_CNT elements.
The following four patches makes the input core reuse the input_absinfo
struct and only carry one pointer per axis. These structs are allocated
on demand now, making it less painful to add new ABS axis eventually.
As everything is now nicely abstracted, we might even move over to a
more efficient storage than a linear pointer, but that can be done
later.
I successfully tested this on my desktop machine here.
Let me know what you think.
Thanks,
Daniel
[PATCH 1/4] input: use ABS_CNT rather than (ABS_MAX + 1)
[PATCH 2/4] input: add static inline helpers for ABS properties
[PATCH 3/4] input: switch to input_abs_*() access functions
[PATCH 4/4] input: dynamically allocate ABS information
next reply other threads:[~2010-05-19 17:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 17:22 Daniel Mack [this message]
2010-05-19 17:22 ` [PATCH 1/4] input: use ABS_CNT rather than (ABS_MAX + 1) Daniel Mack
2010-05-19 17:22 ` [PATCH 2/4] input: add static inline helpers for ABS properties Daniel Mack
2010-05-19 17:22 ` [PATCH 3/4] input: switch to input_abs_*() access functions Daniel Mack
2010-07-14 8:09 ` Dmitry Torokhov
2010-05-19 17:22 ` [PATCH 4/4] input: dynamically allocate ABS information Daniel Mack
2010-05-24 16:08 ` Daniel Mack
2010-05-24 16:15 ` Dmitry Torokhov
2010-06-16 8:39 ` Daniel Mack
2010-07-21 8:30 ` Dmitry Torokhov
2010-07-21 8:31 ` Dmitry Torokhov
2010-07-21 8:32 ` Dmitry Torokhov
2010-07-21 9:22 ` ext-phil.2.carmody
2010-07-21 10:42 ` Artem Bityutskiy
2010-08-11 7:02 ` Daniel Mack
2010-08-13 3:35 ` Dmitry Torokhov
2010-08-07 15:23 ` Daniel Mack
2010-08-11 3:29 ` Dmitry Torokhov
2010-07-14 8:18 ` Dmitry Torokhov
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=1274289757-2723-1-git-send-email-daniel@caiaq.de \
--to=daniel@caiaq.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).