From: "Henrik Rydberg" <rydberg@bitmath.se>
To: David Herrmann <dh.herrmann@googlemail.com>
Cc: linux-input@vger.kernel.org, jkosina@suse.cz
Subject: Re: [PATCH v3] HID: Allow drivers to be their own listener
Date: Fri, 20 Jul 2012 14:28:01 +0200 [thread overview]
Message-ID: <20120720122801.GA1463@polaris.bitmath.org> (raw)
In-Reply-To: <1342777749-31457-1-git-send-email-dh.herrmann@googlemail.com>
On Fri, Jul 20, 2012 at 11:49:09AM +0200, David Herrmann wrote:
> hid-picolcd and hid-wiimote do not allow any of hidinput, hiddev or hidraw
> to claim the device but still want to remain on the bus. Hence, if a
> driver uses the raw_event callback but no other listener claimed the
> device, we still leave it on the bus as the driver handles everything by
> itself. It thus becomes its own listener.
>
> Under some circumstances (eg., hidinput_connect() fails and raw_event set)
> a device may be left on the bus even though it requires external
> listeners. But then if hidinput_connect() fails there are bigger issues
> than a device that is left unhandled. So we can safely use this heuristic
> to avoid adding another flag for special devices like hid-picolcd and
> hid-wiimote.
>
> This also removes the ugly hack from hid-picolcd as this is no longer
> required.
>
> Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
> ---
> Sorry for the delay. I had two exams this week that got into my way. Anyway, I
> hope this time the patch looks ok.
>
> Thanks to Henrik for reviewing it the previous times.
Thanks, David, looking good now.
Acked-by: Henrik Rydberg <rydberg@euromail.se>
Henrik
next prev parent reply other threads:[~2012-07-20 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 9:49 [PATCH v3] HID: Allow drivers to be their own listener David Herrmann
2012-07-20 12:28 ` Henrik Rydberg [this message]
2012-07-20 12:49 ` Jiri Kosina
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=20120720122801.GA1463@polaris.bitmath.org \
--to=rydberg@bitmath.se \
--cc=dh.herrmann@googlemail.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 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).