From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Jiri Kosina <jkosina@suse.cz>, Stephane Chatty <chatty@enac.fr>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] HID: multitouch: append " Pen" to the name of the stylus input
Date: Wed, 20 Mar 2013 15:42:27 +0100 [thread overview]
Message-ID: <5149CAD3.30603@redhat.com> (raw)
In-Reply-To: <20130319213806.GB7877@polaris.bitmath.org>
On 03/19/2013 10:38 PM, Henrik Rydberg wrote:
> Hi Benjamin,
>
>> This is not just cosmetics, it can help to write udev and X.org
>> rules.
>>
>> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
>> ---
>> drivers/hid/hid-multitouch.c | 24 +++++++++++++++++++++++-
>> 1 file changed, 23 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-multitouch.c
>> index d89f0eb..faeec95 100644
>> --- a/drivers/hid/hid-multitouch.c
>> +++ b/drivers/hid/hid-multitouch.c
>> @@ -44,6 +44,7 @@
>> #include <linux/slab.h>
>> #include <linux/usb.h>
>> #include <linux/input/mt.h>
>> +#include <linux/string.h>
>>
>>
>> MODULE_AUTHOR("Stephane Chatty <chatty@enac.fr>");
>> @@ -371,6 +372,15 @@ static int mt_pen_input_mapping(struct hid_device *hdev, struct hid_input *hi,
>> unsigned long **bit, int *max)
>> {
>> struct mt_device *td = hid_get_drvdata(hdev);
>> + char *name;
>> +
>> + if (hi->input->name == hdev->name) {
>> + name = kzalloc(sizeof(hdev->name) + 5, GFP_KERNEL);
>> + if (name) {
>> + sprintf(name, "%s Pen", hdev->name);
>> + hi->input->name = name;
>> + }
>> + }
>
> Why not simply duplicate the the string? This kind of magic sharing is
> not really helping. Also, for multi input devices, the assumptions in
> hidinput_allocate() seem to be the culprit. Perhaps the fix should be
> there instead.
Yes, hidinput_allocate() clearly steals the reference here. However,
fixing this in hid-core would not be simpler: some drivers (ntrig does
at least) assume that there is no need to free input->name, which means
that:
- either we need to fix each individual driver
- either we introduce some kind of mechanism in order not to free "const
char *" declarations like it happens in ntrig.
In v2, I'll just realloc for each input the input->name, and then if the
pen is here, then it will realloc the new name.
Cheers,
Benjamin
>
>>
>> td->pen_report_id = field->report->id;
>>
>> @@ -914,6 +924,7 @@ static int mt_probe(struct hid_device *hdev, const struct hid_device_id *id)
>> int ret, i;
>> struct mt_device *td;
>> struct mt_class *mtclass = mt_classes; /* MT_CLS_DEFAULT */
>> + struct hid_input *hi;
>>
>> for (i = 0; mt_classes[i].name ; i++) {
>> if (id->driver_data == mt_classes[i].name) {
>> @@ -964,7 +975,7 @@ static int mt_probe(struct hid_device *hdev, const struct hid_device_id *id)
>>
>> ret = hid_hw_start(hdev, HID_CONNECT_DEFAULT);
>> if (ret)
>> - goto fail;
>> + goto hid_fail;
>>
>> ret = sysfs_create_group(&hdev->dev.kobj, &mt_attribute_group);
>>
>> @@ -976,6 +987,10 @@ static int mt_probe(struct hid_device *hdev, const struct hid_device_id *id)
>>
>> return 0;
>>
>> +hid_fail:
>> + list_for_each_entry(hi, &hdev->inputs, list)
>> + if (hi->input->name != hdev->name)
>> + kfree(hi->input->name);
>> fail:
>> kfree(td->fields);
>> kfree(td);
>> @@ -1020,8 +1035,15 @@ static int mt_resume(struct hid_device *hdev)
>> static void mt_remove(struct hid_device *hdev)
>> {
>> struct mt_device *td = hid_get_drvdata(hdev);
>> + struct hid_input *hi;
>> +
>> sysfs_remove_group(&hdev->dev.kobj, &mt_attribute_group);
>> hid_hw_stop(hdev);
>> +
>> + list_for_each_entry(hi, &hdev->inputs, list)
>> + if (hi->input->name != hdev->name)
>> + kfree(hi->input->name);
>> +
>> kfree(td);
>> hid_set_drvdata(hdev, NULL);
>> }
>> --
>> 1.8.1.2
>>
>
> Thanks,
> Henrik
>
next prev parent reply other threads:[~2013-03-20 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 16:55 [PATCH 0/7] HID: multitouch: support of hybrid finger/pen devices Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 1/7] HID: input: don't register unmapped input devices Benjamin Tissoires
2013-03-19 21:25 ` Henrik Rydberg
2013-03-20 9:30 ` Benjamin Tissoires
2013-03-22 14:48 ` Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 2/7] HID: multitouch: breaks out touch handling in specific functions Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 3/7] HID: multitouch: do not map usage from non used reports Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 4/7] HID: multitouch: add handling for pen in dual-sensors device Benjamin Tissoires
2013-03-19 21:32 ` Henrik Rydberg
2013-03-20 13:42 ` Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 5/7] HID: multitouch: manually send sync event for pen input report Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 6/7] HID: multitouch: append " Pen" to the name of the stylus input Benjamin Tissoires
2013-03-19 21:38 ` Henrik Rydberg
2013-03-20 14:42 ` Benjamin Tissoires [this message]
2013-02-27 16:55 ` [PATCH 7/7] HID: multitouch: force BTN_STYLUS for pen devices Benjamin Tissoires
2013-03-18 22:14 ` [PATCH 0/7] HID: multitouch: support of hybrid finger/pen devices Jiri Kosina
2013-03-19 21:40 ` Henrik Rydberg
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=5149CAD3.30603@redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=benjamin.tissoires@gmail.com \
--cc=chatty@enac.fr \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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).