Re: [PATCH 2.6.10-rc1 4/4] driver-model: attach/detach sysfs node implemented
From: Dmitry Torokhov (dtor_core_at_ameritech.net)
Date: 11/04/04
- Previous message: Greg KH: "Re: [PATCH 2.6.10-rc1 4/5] driver-model: kobject_add() error path reference counting fix"
- Maybe in reply to: Tejun Heo: "Re: [PATCH 2.6.10-rc1 4/4] driver-model: attach/detach sysfs node implemented"
- Next in thread: Tejun Heo: "Re: [PATCH 2.6.10-rc1 4/4] driver-model: attach/detach sysfs node implemented"
- Reply: Tejun Heo: "Re: [PATCH 2.6.10-rc1 4/4] driver-model: attach/detach sysfs node implemented"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 4 Nov 2004 11:06:19 -0800 (PST) To: Greg KH <greg@kroah.com>
> Greg KH wrote:
> On Thu, Nov 04, 2004 at 12:05:31PM -0500, Dmitry Torokhov wrote:
> > Also, there usually much more going on with regard to locking and
> > other bus-specific actions besides taking bus's rwsem when binding
> > devices. Serio bus will definitely get upset if you try to disconnect
> > even a leaf device in the manner presented above and I think USB
> > will get upset as well.
>
> No, we can disconnect a driver from a device just fine for USB with no
What about connecting? I am pretty ignorant of USB inner workings
but when I took a glance there seems to be a lot of preparations
before device is ready to be probed...
> problems (as long as it's not the hub driver from a hub device, we need
> to never be able to disconnect those.)
Never say never ;) That was the first thing I did after playing with
PCI devices when I tried doing what Tejun did.
If kernel advertises an userspace interface it will be used. I can see
myself wanting to disconnect my hub and all its devices so my wireless
explorer does not use batteries and I do not want to figure out what
port it is connected to... Someone else will find another reason,
I don't know.
I also think that even PCI should kill children devices behind a bridge
if bridge driver is disconnected to manage resources in more strict way.
But I think that would require notion of generic/specialized driver and
require automatic rebinding of specialized driver over generic one so
every PCI device has a driver attached to it.
-- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Greg KH: "Re: [PATCH 2.6.10-rc1 4/5] driver-model: kobject_add() error path reference counting fix"
- Maybe in reply to: Tejun Heo: "Re: [PATCH 2.6.10-rc1 4/4] driver-model: attach/detach sysfs node implemented"
- Next in thread: Tejun Heo: "Re: [PATCH 2.6.10-rc1 4/4] driver-model: attach/detach sysfs node implemented"
- Reply: Tejun Heo: "Re: [PATCH 2.6.10-rc1 4/4] driver-model: attach/detach sysfs node implemented"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|