Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757321Ab2JQPCa (ORCPT ); Wed, 17 Oct 2012 11:02:30 -0400 Received: from mail-pa0-f46.google.com ([209.85.220.46]:38193 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757296Ab2JQPC2 (ORCPT ); Wed, 17 Oct 2012 11:02:28 -0400 Date: Wed, 17 Oct 2012 08:02:17 -0700 From: Greg Kroah-Hartman To: Guennadi Liakhovetski Cc: linux-kernel@vger.kernel.org, Linux Media Mailing List Subject: Re: [Q] reprobe deferred-probing drivers Message-ID: <20121017150217.GA29424@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1095 Lines: 23 On Wed, Oct 17, 2012 at 10:27:36AM +0200, Guennadi Liakhovetski wrote: > Hi > > I've got a situation, for which I currently don't have a (good) solution. > > Let's say device A depends on device B and as long as B hasn't probed, A > requests deferred probing. Now B probes, which causes A to also succeed > its probing. Next we want to remove B, say, by unloading its driver. A has > to go back into "deferred-probing" state. How do we do it? This can be > achieved by unloading B's driver and loading again. Essentially, we have > to use the sysfs "unbind" and then the "bind" attributes. But how do we do > this from the kernel? Shall we export driver_bind() and driver_unbind()? No, no driver should ever have to mess with that at all, it is up to the bus to do this. Do you have a pointer to the code you are concerned about? greg k-h -- 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/