public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stelian Pop <stelian@popies.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] usb sysfs intf files no longer created when probe fails
Date: Wed, 22 Jun 2005 20:33:25 +0200	[thread overview]
Message-ID: <1119465205.5080.10.camel@deep-space-9.dsnet> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0506221144360.6938-100000@iolanthe.rowland.org>

Le mercredi 22 juin 2005 à 12:03 -0400, Alan Stern a écrit :
> On Wed, 22 Jun 2005, Stelian Pop wrote:
> 
> > Notice the '1-2:1.1' is missing. Upon booting I get:
> > 
> > Jun 22 13:34:04 localhost kernel: HID device not claimed by input or hiddev
> > Jun 22 13:34:04 localhost kernel: usbhid: probe of 1-2:1.1 failed with error -5
> > Jun 22 13:34:04 localhost kernel: usb 1-2: device_add(1-2:1.1) --> -5

> You shouldn't call usb_create_sysfs_intf_files in any case.

Ok.

> Your driver is returning -EIO from its probe routine according to the log,
> so it's not getting bound to the device. 

Actually that's usbhid which returns -EIO.

>  Hence there shouldn't be any
> attempt to unbind the device when your driver is removed.  This is a bug
> in usbcore; it tries to delete all the interfaces without checking whether 
> they were successfully added.

Since this is fixed by reverting the device_add patch, I'm wondering if
this isn't a driver model core bug, where it tries to device_remove all
the "devices" even if they weren't correctly added before...

But I haven't looked closely at the code, this is just a thought.

Stelian.
-- 
Stelian Pop <stelian@popies.net>


  reply	other threads:[~2005-06-22 18:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22 13:50 usb sysfs intf files no longer created when probe fails Stelian Pop
2005-06-22 14:07 ` [linux-usb-devel] " Stelian Pop
2005-06-22 14:56   ` Stelian Pop
2005-06-22 16:03     ` Alan Stern
2005-06-22 18:33       ` Stelian Pop [this message]
2005-06-22 16:17     ` Greg KH
2005-06-22 14:59 ` Greg KH
2005-06-22 15:09   ` [linux-usb-devel] " Stelian Pop
2005-06-22 15:41     ` Alan Stern
2005-06-22 15:53       ` Stelian Pop
2005-06-22 16:22         ` Greg KH
2005-06-22 18:27           ` Stelian Pop
2005-06-22 16:26         ` Greg KH
2005-06-22 18:25           ` Stelian Pop

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=1119465205.5080.10.camel@deep-space-9.dsnet \
    --to=stelian@popies.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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