From: Mario Limonciello <mario_limonciello@dell.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH 1/2] hid2hci: iterate libusb devices twice
Date: Tue, 28 Jul 2009 18:12:42 +0000 [thread overview]
Message-ID: <4A6F3F9A.5040405@dell.com> (raw)
In-Reply-To: <4A6E19FD.7040908@dell.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
Hi Kay:
Kay Sievers wrote:
> On Mon, Jul 27, 2009 at 23:32, Marcel Holtmann<marcel@holtmann.org> wrote:
>
>
> Now it's getting funny. We need to call the nonsense two times to make
> it work? We need to fix the real issue here instead of doing guesswork
> and adding hacks like this. Any idea what's going on with the first
> scan? The device node is guaranteed to exist when we call stuff from
> RUN+= instructions.
>
>
I'm not sure what's going on here, but I think i'll just go down that
road of pulling the necessary code out of libusb's find_devices to just
craft a usb_device object with the information we already have so there
is no necessary scanning in the first place. There will still be a
dependency on libusb to be able to send a usb_control_msg, claim, etc,
but at least the time consuming, unnecessary scan will be gone.
>
> Well, libusb might be ok for stuff that just searches things which are
> always there, it's definitely not suitable to be used in conjunction
> with udev. The entire coldplug with 500 devices takes ~0.5 seconds
> here, while a single call to libusb takes ~0.15 just to find the
> device we already have. That alone is not acceptable, and now we
> should call the useless scan twice? Tsss ... :)
>
Yeah I understand. I'll follow up after I get something else together.
--
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2009-07-28 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 21:19 [PATCH 1/2] hid2hci: iterate libusb devices twice Mario Limonciello
2009-07-27 21:32 ` Marcel Holtmann
2009-07-28 0:12 ` Kay Sievers
2009-07-28 18:12 ` Mario Limonciello [this message]
2009-07-29 16:30 ` Mario Limonciello
2009-07-29 18:34 ` Mario_Limonciello
2009-07-29 22:14 ` Kay Sievers
2009-07-30 14:37 ` Alan Stern
2009-07-30 15:27 ` Kay Sievers
2009-07-30 15:37 ` Kay Sievers
2009-07-30 16:00 ` Alan Stern
2009-07-30 17:03 ` Mario Limonciello
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=4A6F3F9A.5040405@dell.com \
--to=mario_limonciello@dell.com \
--cc=linux-hotplug@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).