Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755961AbaGSVP6 (ORCPT ); Sat, 19 Jul 2014 17:15:58 -0400 Received: from aso-006-i447.relay.mailchannels.net ([23.91.64.128]:19387 "EHLO relay.mailchannels.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751174AbaGSVP4 (ORCPT ); Sat, 19 Jul 2014 17:15:56 -0400 X-Sender-Id: arvixe|x-authuser|przemo@firszt.eu X-Sender-Id: arvixe|x-authuser|przemo@firszt.eu X-MC-Relay: Good X-MailChannels-SenderId: arvixe|x-authuser|przemo@firszt.eu X-MailChannels-Auth-Id: arvixe Message-ID: <1405804548.13990.7.camel@fedora-lan> Subject: Re: [PATCH 0/5] Input - wacom: battery enhancements and unifying hid-wacom and wacom From: Przemo Firszt To: Benjamin Tissoires Cc: Dmitry Torokhov , Jiri Kosina , Ping Cheng , Jason Gerecke , linux-kernel@vger.kernel.org, linux-input@vger.kernel.org Date: Sat, 19 Jul 2014 22:15:48 +0100 In-Reply-To: <1405017900-16024-1-git-send-email-benjamin.tissoires@redhat.com> References: <1405017900-16024-1-git-send-email-benjamin.tissoires@redhat.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-2.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: przemo@firszt.eu Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dnia 2014-07-10, czw o godzinie 14:44 -0400, Benjamin Tissoires pisze: > Hi guys, > > Continuing on the Wacom cleanup, here are 5 patches. > > The first two enhance the battery reporting for the Wireless receiver by > adding the status of the battery (discharging, full, charging) - inspired by > the code found in hid-wacom.c, and also by adding notifications to the power > system so that upower knows when the battery changed. > > The last three are the handling of the two Wacom Bluetooth devices in wacom.ko. > Some enhancements here: > - Intuos4 now supports other tools than just the plain stylus (mouse, artpen, ...) > - one less driver for Wacom (~700 lines of code less in total) > - unifying access to LEDs/OLEDs from Bluetooth and USB devices > > 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? > > This whole code is based on top of the previous HID conversion patches. > I pushed a branch with all I have queued on the list here: > https://github.com/bentiss/linux/commits/hid-wacom-legacy-3.16-rc4 > > Again, given that there has been no answer on how this can be merged upstream > (Jiri? Dmitry?), I just piled those on top of the previous. > I wouldn't to resplit the input and hid specific changes if this is the choice > that is made. > > Cheers, > Benjamin > > Benjamin Tissoires (5): > Input - wacom: enhance Wireless Receiver battery reporting > Input - wacom: use a specific name for the battery device > Input - wacom: handle Graphire BT tablets in wacom.ko > Input - wacom: handle Intuos 4 BT in wacom.ko > HID: remove hid-wacom Bluetooth driver > > drivers/hid/Kconfig | 8 - > drivers/hid/Makefile | 1 - > drivers/hid/hid-core.c | 2 - > drivers/hid/hid-wacom.c | 973 --------------------------------------- > drivers/input/tablet/wacom.h | 6 + > drivers/input/tablet/wacom_sys.c | 114 ++++- > drivers/input/tablet/wacom_wac.c | 189 +++++++- > drivers/input/tablet/wacom_wac.h | 8 + > 8 files changed, 303 insertions(+), 998 deletions(-) > delete mode 100644 drivers/hid/hid-wacom.c > Benjamin, I think we might try to fix that [1] as well when making changes to the sysfs entries. Currently every tablet connected wirelessly will trigger creating new sysfs entries: /sys/class/power_supply/wacom_ac /sys/class/power_supply/wacom_battery so sysfs is not happy about attempts to create duplicates. We need to distinguish between devices using consecutive numbers or something else. [1] https://sourceforge.net/p/linuxwacom/bugs/248/ -- Kind regards, Przemo Firszt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/