linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Eduard Hasenleithner <eduard@hasenleithner.at>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Wacom Intuos4 LED and OLED control
Date: Fri, 6 May 2011 08:52:04 -0700	[thread overview]
Message-ID: <20110506155204.GA4754@core.coreip.homeip.net> (raw)
In-Reply-To: <1302303254-3062-1-git-send-email-eduard@hasenleithner.at>

Hi Eduard,

On Sat, Apr 09, 2011 at 12:54:14AM +0200, Eduard Hasenleithner wrote:
> This commit enables control of the LEDs and OLED displays found
> on the Wacom Intuos4 M, L, and XL. For this purpose, a new "led"
> attribute group is added to the sysfs entry of the input device.
> 
> This "led" group only shows up when the correct device (M, L,
> or XL) is detected. Four write-only attributes are created:
> * "luminance":
> 	array of three integers specfying
> 	* status led brightness when no button is pressed (0..127)
> 	* status led brightness when a button is pressed (0..127)
> 	* brightness of the OLED display (0..15)

This violates "one value per attribute" sysfs principle. I think these
should be split into brightness on, brightness off, and display brightness.
I also wonder if status LED should be wired into LED subsystem... Not
sure though... The tablet does not allow controlling when LEDs are
activated, does it?

> * "status_select":
> 	specifies the id (0..3) of the status led, -1 = none

I think we should create 4 separate groups led0 .. led3 each containing
the attributes above instead of implementing the selector which is
inherently racy.

> * "button_select":
> 	specifies the button id (0..7) of the image
> * "button_rawimg":
> 	sets the raw image data of the button (binary, 1024 octets)

Same here, create as many binary attributes as needed (probably putting
into separate group).

Also please document these attributes in
Documentation/ABI/testing/sysfs-wacom

Thanks!

-- 
Dmitry

  parent reply	other threads:[~2011-05-06 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 22:54 [PATCH] Wacom Intuos4 LED and OLED control Eduard Hasenleithner
2011-04-13  9:08 ` Eduard Hasenleithner
2011-05-06 15:52 ` Dmitry Torokhov [this message]
2011-05-06 16:28   ` Eduard Hasenleithner
2011-05-06 16:43     ` Dmitry Torokhov
2011-05-06 17:32       ` Eduard Hasenleithner
2011-05-06 17:42         ` Dmitry Torokhov
2011-05-06 17:57           ` Eduard Hasenleithner
2011-06-02  9:51             ` San Vu Ngoc
     [not found]               ` <BANLkTi=E4BEpF0G90q4zNHtVLvpTDhWtvA@mail.gmail.com>
     [not found]                 ` <20110817071724.GF29361@core.coreip.homeip.net>
2011-09-02 21:48                   ` Eduard Hasenleithner

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=20110506155204.GA4754@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=eduard@hasenleithner.at \
    --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).