[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1111132100000.15187@pobox.suse.cz>
Date: Sun, 13 Nov 2011 21:01:28 +0100 (CET)
From: Jiri Kosina <jkosina@...e.cz>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: KY Srinivasan <kys@...rosoft.com>,
"gregkh@...e.de" <gregkh@...e.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org>,
"ohering@...e.com" <ohering@...e.com>,
"joe@...ches.com" <joe@...ches.com>
Subject: Re: [PATCH 1/1] Staging: hv: Move the mouse driver out of staging
On Sun, 6 Nov 2011, Dmitry Torokhov wrote:
> > I am not a hid expert; but all hid low level drivers appear to do this.
> > Initially, I was directly invoking hid_connect() directly and based on your
> > Input, I chose to use hid_hw_start() which all other drivers are using.
>
> Note that the users of hid_hw_start() actually are not low level
> drivers, such as usbhid or bluetooth hidp, but higher-level drivers,
> such as hid-wacom, hid-a4tech, etc. Since your driver is a low-level
> driver (a provider so to speak) it should not call hid_hw_start() on its
> own but rather wait for the hid code to do it.
>
> Still, I am not a HID expert either so I'll defer to Jiri here.
Hi,
my understanding is that hv driver is actually a bit special in this
respect -- it's actually all-in-one both low-level and high-level driver.
I take it that there is not ever going to be a different high-level driver
using low-level hv transport (is that correct, KY?), so this might indeed
be an acceptable layout of the driver.
Thanks a lot,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists