All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolai Kondrashov <spbnick@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH 1/1] HID: add have_special_driver hid module parameter
Date: Sun, 01 Apr 2012 22:33:31 +0300	[thread overview]
Message-ID: <4F78AD8B.9020104@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1203301544270.25526@pobox.suse.cz>

Hi Jiri,

On 03/30/2012 04:49 PM, Jiri Kosina wrote:
> On Mon, 20 Feb 2012, Nikolai Kondrashov wrote:
>> Add "have_special_driver" hid module parameter - a list of additional HID
>> devices which have specialized driver on HID bus. Needed to support out-of-tree
>> HID drivers.
>
> I'd very much prefer just using sysfs (bind/unbind) way of doing things if
> possible for this purpose. What do you think?

I've tried this and it is not suitable. At least not in the current shape.

In short, two reasons:

1. The HID report descriptor is parsed only once, on first device probe and
    the resulting data is kept within device structure. It is not parsed
    again after unbind/bind, thus report_fixup of my driver is not called and
    the reports are getting interpreted according to the old one, rendering
    the device (partially) unusable.

2. The udev rules and scripts needed to make it work in a plug'n'play manner
    suitable for users are considerably more hacky than this solution.

I'd like to ask you to accept this patch for now.  Would it still be
possible to get this patch into 3.4? I promise to look for a better
solution. First step would probably be to fix rebinding.

It seems that you don't have much time recently to review/accept my patches.
Would you direct me to someone else who could do this and thus reduce your
load?

Thanks you.

Sincerely,
Nick

  parent reply	other threads:[~2012-04-01 19:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 21:29 [PATCH 1/1] HID: add have_special_driver hid module parameter Nikolai Kondrashov
2012-02-27 14:15 ` Nikolai Kondrashov
2012-02-28 14:30   ` Jiri Kosina
2012-02-28 15:12     ` Nikolai Kondrashov
2012-02-29 21:23     ` Nikolai Kondrashov
2012-03-29  8:00     ` Nikolai Kondrashov
2012-03-30 13:49 ` Jiri Kosina
2012-03-30 15:22   ` Nikolai Kondrashov
2012-03-30 23:03     ` David Herrmann
2012-04-01 19:44       ` Nikolai Kondrashov
2012-04-01 19:49         ` Jiri Kosina
2012-04-01 20:11           ` Nikolai Kondrashov
2012-04-01 20:10         ` David Herrmann
2012-04-01 20:22           ` Nikolai Kondrashov
2012-04-01 19:33   ` Nikolai Kondrashov [this message]
2012-04-01 19:46     ` Jiri Kosina
2012-04-01 20:50       ` Nikolai Kondrashov
2012-04-02 23:41         ` Jiri Kosina
2012-04-04  8:27           ` Nikolai Kondrashov
2012-04-08 10:48           ` Nikolai Kondrashov
2012-04-03 14:46         ` Henrik Rydberg
2012-04-03 15:09           ` Jiri Kosina
2012-04-03 16:37             ` Henrik Rydberg
2012-04-03 17:01               ` Jiri Kosina
2012-04-03 17:11                 ` 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=4F78AD8B.9020104@gmail.com \
    --to=spbnick@gmail.com \
    --cc=jkosina@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.