linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcin Tolysz <tolysz@gmail.com>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: linux-input@vger.kernel.org
Subject: Re: [RFC] Simple but effective way of changing HID device descriptors (resent)
Date: Thu, 31 Dec 2009 17:28:59 +0000	[thread overview]
Message-ID: <54bbe4e00912310928o70b3111cu7d1058a61947f971@mail.gmail.com> (raw)
In-Reply-To: <20091224093918.1fe7e32a.ospite@studenti.unina.it>

Just to make sure the corrected patch is: [RFC v2] [HID] allow using
external Hid Descriptors.

2009/12/24 Antonio Ospite <ospite@studenti.unina.it>:
> On Thu, 24 Dec 2009 02:29:47 +0000
> Marcin Tolysz <tolysz@gmail.com> wrote:
>
>> Simple but effective way of changing HID device descriptors using
>> firmware loading mechanism.
>> Just place your new descriptor in a location specified by driver
>> i.e. somewhere in /lib/firmware/hid/
>> If it is there it will replace HID descriptor from the device.
>> I do not do any parsing or checking, as it is done by hid driver.
>>
>> Signed-off-by: Marcin Tolysz <tolysz@gmail.com>
>>
>
> Only some style comments below, I haven't tested the patch. Plus, try
> running the patch through scripts/checkpatch.pl to spot all the other
> style issues.

Corrected most of style errors but 3 too long lines.

>> ---
>>   drivers/hid/hid-core.c |   26 +++++++++++++++++++++++++-
>>   1 files changed, 25 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
>> index 80792d3..5d8d656 100644
>> --- a/drivers/hid/hid-core.c
>> +++ b/drivers/hid/hid-core.c
>> @@ -27,6 +27,7 @@
>>   #include <linux/wait.h>
>>   #include <linux/vmalloc.h>
>>   #include <linux/sched.h>
>> +#include <linux/firmware.h>
>>
>>   #include <linux/hid.h>
>>   #include <linux/hiddev.h>
>> @@ -640,6 +641,10 @@ int hid_parse_report(struct hid_device *device,
>> __u8 *start,
>>       struct hid_item item;
>>       __u8 *end;
>>       int ret;
>> +     const struct firmware *fw;
>> +     int succ;
>
> success? Can't you init fw to NULL and derive this info checking
> (fw != NULL) before releasing firmware?
every other driver checks this value, fw is a structure thus I would
need to check fw->data;

>> +     char *file;
>> +
>>       static int (*dispatch_type[])(struct hid_parser *parser,
>>                                     struct hid_item *item) = {
>>               hid_parser_main,
>> @@ -650,10 +655,27 @@ int hid_parse_report(struct hid_device *device,
>> __u8 *start,
>>
>>       if (device->driver->report_fixup)
>>               device->driver->report_fixup(device, start, size);
>> +     /* Now load a hid descriptor from a file firmware
>> +     ignoring this fixup thing */
>> +     file=kmalloc(29, GFP_KERNEL);
>> +
>> sprintf(file,"hid/%04X:%04X:%04X:%04X.bin",device->bus,device->vendor,device->product,device->version);
>> +
>
> What about removing this 29?
> #define NEW_HID_DESCRIPTOR_PATH_FMT "hid/%04X:%04X:%04X:%04X.bin"
> and use it in kmalloc with strlen and in sprintf.

replaced by:
       file = kasprintf(GFP_KERNEL, "hid/%04X:%04X:%04X:%04X.bin",
                      device->bus, device->vendor, device->product,
device->version);
I did not putted it into define as this heavily depends on parameters,
and I do not want to separate them yet.

>> +     succ = request_firmware(&fw, file, &device->dev);
>> +
>> +     if (succ)
>> +             printk(KERN_INFO "To relace HID descriptor place it in
>> /lib/firmaware/%s\n", file);
>
> pr_info() could be used or maybe even dev_info()

I went for pr_info.

>> +     else{
>> +             start = fw->data;
>> +             size = fw->size;
>> +             printk(KERN_INFO "HID descriptor relaced with /lib/firmaware/%s\n",
>> file);
>> +     }
>> +     kfree(file);
>>
>>       device->rdesc = kmalloc(size, GFP_KERNEL);
>> -     if (device->rdesc == NULL)
>> +     if (device->rdesc == NULL){
>> +             if(!succ)release_firmware(fw);
>>               return -ENOMEM;
>> +     }
>>       memcpy(device->rdesc, start, size);
>>       device->rsize = size;
>>
>> @@ -690,6 +712,7 @@ int hid_parse_report(struct hid_device *device, __u8
>> *start,
>>                               dbg_hid("unbalanced delimiter at end of report description\n");
>>                               goto err;
>>                       }
>> +                     if(!succ)release_firmware(fw);
>>                       vfree(parser);
>>                       return 0;
>>               }
>> @@ -697,6 +720,7 @@ int hid_parse_report(struct hid_device *device, __u8
>> *start,
>>
>>       dbg_hid("item fetching failed at offset %d\n", (int)(end - start));
>>   err:
>> +     if(!succ)release_firmware(fw);
>>       vfree(parser);
>>       return ret;
>>   }
>> -- 1.6.5.7
>
> Regards,
>   Antonio

Many thanks for your help.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-12-31 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24  2:29 [RFC] Simple but effective way of changing HID device descriptors (resent) Marcin Tolysz
2009-12-24  8:39 ` Antonio Ospite
2009-12-31 17:28   ` Marcin Tolysz [this message]

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=54bbe4e00912310928o70b3111cu7d1058a61947f971@mail.gmail.com \
    --to=tolysz@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=ospite@studenti.unina.it \
    /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).