linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Przemo Firszt <przemo@firszt.eu>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>, Ping Cheng <pinglinux@gmail.com>,
	Jason Gerecke <killertofu@gmail.com>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 0/5] Input - wacom: battery enhancements and unifying hid-wacom and wacom
Date: Thu, 10 Jul 2014 22:14:04 +0100	[thread overview]
Message-ID: <1405026844.2613.15.camel@fedora-lan> (raw)
In-Reply-To: <1405017900-16024-1-git-send-email-benjamin.tissoires@redhat.com>

Dnia 2014-07-10, czw o godzinie 14:44 -0400, Benjamin Tissoires pisze:
[..]
Hi Benjamin,
> However, I did not backport the speed attribute and the ac power
> device (which
> is infered by the battery status). I don't know if there are users of
> those two,
> so I let them aside for now. Przemo, any ideas if this is actually 
> used?
Both tablets that I had (Graphire Wireless and Intuos4 Wireless)
supports slow and fast reporting. Slow reporting is necessary with older
bluetooth receivers otherwise the lag between pen movement and cursor
movement made devices unusable.

I tried to expose all events reported by hardware and I think AC
reporting should stay in the kernel.

Intuos4 Wireless
AC power disconnected:
bash-4.2$ cat /sys/class/power_supply/wacom_ac/uevent 
POWER_SUPPLY_NAME=wacom_ac
POWER_SUPPLY_PRESENT=0
POWER_SUPPLY_ONLINE=0
POWER_SUPPLY_SCOPE=Device
bash-4.2$ cat /sys/class/power_supply/wacom_battery/uevent 
POWER_SUPPLY_NAME=wacom_battery
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_CAPACITY=85
POWER_SUPPLY_SCOPE=Device
POWER_SUPPLY_STATUS=Discharging

AC power connected:
bash-4.2$ cat /sys/class/power_supply/wacom_ac/uevent 
POWER_SUPPLY_NAME=wacom_ac
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_SCOPE=Device
bash-4.2$ cat /sys/class/power_supply/wacom_battery/uevent 
POWER_SUPPLY_NAME=wacom_battery
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_CAPACITY=85
POWER_SUPPLY_SCOPE=Device
POWER_SUPPLY_STATUS=Charging
-- 
Kind regards,
Przemo Firszt


  parent reply	other threads:[~2014-07-10 23:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 18:44 [PATCH 0/5] Input - wacom: battery enhancements and unifying hid-wacom and wacom Benjamin Tissoires
2014-07-10 18:44 ` [PATCH 1/5] Input - wacom: enhance Wireless Receiver battery reporting Benjamin Tissoires
2014-07-10 18:44 ` [PATCH 2/5] Input - wacom: use a specific name for the battery device Benjamin Tissoires
2014-07-10 18:44 ` [PATCH 3/5] Input - wacom: handle Graphire BT tablets in wacom.ko Benjamin Tissoires
2014-07-10 18:44 ` [PATCH 4/5] Input - wacom: handle Intuos 4 BT " Benjamin Tissoires
2014-07-10 18:45 ` [PATCH 5/5] HID: remove hid-wacom Bluetooth driver Benjamin Tissoires
2014-07-10 21:14 ` Przemo Firszt [this message]
2014-07-11 13:13   ` [PATCH 0/5] Input - wacom: battery enhancements and unifying hid-wacom and wacom Benjamin Tissoires
2014-07-19 21:15 ` Przemo Firszt
2014-07-22 13:49   ` Benjamin Tissoires

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=1405026844.2613.15.camel@fedora-lan \
    --to=przemo@firszt.eu \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=killertofu@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pinglinux@gmail.com \
    /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).