linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: "Éric Piel" <eric.piel@tremplin-utc.net>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore
Date: Sun, 18 Oct 2009 00:51:27 -0700	[thread overview]
Message-ID: <20091018075127.GH3935@core.coreip.homeip.net> (raw)
In-Reply-To: <20091013031741.GB2887@core.coreip.homeip.net>

On Mon, Oct 12, 2009 at 08:17:41PM -0700, Dmitry Torokhov wrote:
> On Mon, Oct 12, 2009 at 11:54:17AM -0700, Greg KH wrote:
> > On Mon, Oct 12, 2009 at 11:33:13AM -0700, Dmitry Torokhov wrote:
> > > On Mon, Oct 12, 2009 at 10:35:51AM -0700, Greg KH wrote:
> > > > On Mon, Oct 12, 2009 at 08:48:46AM -0700, Dmitry Torokhov wrote:
> > > > > > So at least, unbind should fail as well as bind.
> > > > > >
> > > > > 
> > > > > That would be Greg's domain s it is driver core decision whether to
> > > > > allow unbinding platform devices registered with
> > > > > platform_driver_probe().
> > > > 
> > > > No, I do not see why that should not be allowed.
> > > > 
> > > 
> > > Because once you did unbind the device you are stuck (unless the driver
> > > is compiled as a module, but then you could just unload the module
> > > instead of unbinding). Disallowing unbind would allow discarding not
> > > only __devinit but __devexit sections when driver is built in which
> > > would make ebedded people happy[^Hier].
> > 
> > Yeah, good point.
> > 
> > Does anyone do bind/unbind with platform devices today?
> > 
> > If not, a patch changing this would be welcome.
> > 
> 
> How about this one?
> 

*ping* We need to resolve this, otherwise everyone who likes to rebind
i8042 in couse of STR/STD will be in trouble.

> -- 
> Dmitry
> 
> 
> Driver core: allow certain drivers prohibit bind/unbind via sysfs
> 
> From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> 
> Platform drivers registered via platform_driver_probe() can be bound
> to devices only once, upon registration, because discard their probe()
> routines to save memory. Unbinding the driver through sysfs 'unbind'
> leaves the device stranded and confuses users so let's not create
> bind and unbind attributes for such drivers.
> 
> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
> ---
> 
>  drivers/base/bus.c      |   17 +++++++++++------
>  drivers/base/platform.c |    6 +++++-
>  include/linux/device.h  |    4 +++-
>  3 files changed, 19 insertions(+), 8 deletions(-)
> 
> 
> diff --git a/drivers/base/bus.c b/drivers/base/bus.c
> index 973bf2a..63c143e 100644
> --- a/drivers/base/bus.c
> +++ b/drivers/base/bus.c
> @@ -689,15 +689,19 @@ int bus_add_driver(struct device_driver *drv)
>  		printk(KERN_ERR "%s: driver_add_attrs(%s) failed\n",
>  			__func__, drv->name);
>  	}
> -	error = add_bind_files(drv);
> -	if (error) {
> -		/* Ditto */
> -		printk(KERN_ERR "%s: add_bind_files(%s) failed\n",
> -			__func__, drv->name);
> +
> +	if (!drv->suppress_bind_attrs) {
> +		error = add_bind_files(drv);
> +		if (error) {
> +			/* Ditto */
> +			printk(KERN_ERR "%s: add_bind_files(%s) failed\n",
> +				__func__, drv->name);
> +		}
>  	}
>  
>  	kobject_uevent(&priv->kobj, KOBJ_ADD);
>  	return 0;
> +
>  out_unregister:
>  	kfree(drv->p);
>  	drv->p = NULL;
> @@ -720,7 +724,8 @@ void bus_remove_driver(struct device_driver *drv)
>  	if (!drv->bus)
>  		return;
>  
> -	remove_bind_files(drv);
> +	if (!drv->suppress_bind_attrs)
> +		remove_bind_files(drv);
>  	driver_remove_attrs(drv->bus, drv);
>  	driver_remove_file(drv, &driver_attr_uevent);
>  	klist_remove(&drv->p->knode_bus);
> diff --git a/drivers/base/platform.c b/drivers/base/platform.c
> index ed156a1..4fa954b 100644
> --- a/drivers/base/platform.c
> +++ b/drivers/base/platform.c
> @@ -521,11 +521,15 @@ int __init_or_module platform_driver_probe(struct platform_driver *drv,
>  {
>  	int retval, code;
>  
> +	/* make sure driver won't have bind/unbind attributes */
> +	drv->driver.suppress_bind_attrs = true;
> +
>  	/* temporary section violation during probe() */
>  	drv->probe = probe;
>  	retval = code = platform_driver_register(drv);
>  
> -	/* Fixup that section violation, being paranoid about code scanning
> +	/*
> +	 * Fixup that section violation, being paranoid about code scanning
>  	 * the list of drivers in order to probe new devices.  Check to see
>  	 * if the probe was successful, and make sure any forced probes of
>  	 * new devices fail.
> diff --git a/include/linux/device.h b/include/linux/device.h
> index aca31bf..2ea3e49 100644
> --- a/include/linux/device.h
> +++ b/include/linux/device.h
> @@ -124,7 +124,9 @@ struct device_driver {
>  	struct bus_type		*bus;
>  
>  	struct module		*owner;
> -	const char 		*mod_name;	/* used for built-in modules */
> +	const char		*mod_name;	/* used for built-in modules */
> +
> +	bool suppress_bind_attrs;	/* disables bind/unbind via sysfs */
>  
>  	int (*probe) (struct device *dev);
>  	int (*remove) (struct device *dev);

-- 
Dmitry

  reply	other threads:[~2009-10-18  7:51 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11  0:04 [REGRESSION] "bind" a device to a driver doesn't not work anymore Éric Piel
2009-10-11  3:00 ` Greg KH
2009-10-12  4:35   ` Dmitry Torokhov
2009-10-12 11:46     ` Éric Piel
2009-10-12 14:44       ` Greg KH
2009-10-12 15:45         ` Dmitry Torokhov
2009-10-12 17:37           ` Greg KH
2009-10-12 15:48       ` Dmitry Torokhov
2009-10-12 16:48         ` Éric Piel
2009-10-12 17:35         ` Greg KH
2009-10-12 18:33           ` Dmitry Torokhov
2009-10-12 18:54             ` Greg KH
2009-10-12 19:20               ` Dmitry Torokhov
2009-10-12 19:58                 ` Greg KH
2009-10-13  3:17               ` Dmitry Torokhov
2009-10-18  7:51                 ` Dmitry Torokhov [this message]
2009-10-18  8:02                   ` Greg KH
2009-10-23  2:01                     ` Dmitry Torokhov
2009-10-26 20:59                       ` Greg KH
2009-10-26 21:34                         ` Dmitry Torokhov
2009-10-26 23:59                           ` Greg KH
2009-10-27 16:16                             ` Dmitry Torokhov
2009-10-13  9:52         ` Éric Piel
  -- strict thread matches above, loose matches on Subject: below --
2009-10-14  2:05 Dmitry Torokhov
2009-10-15 17:24 ` Éric Piel
2009-10-15 18:13   ` Dmitry Torokhov
2009-10-15 18:27     ` Dmitry Torokhov
2009-10-15 19:32     ` Éric Piel
2009-10-15 19:51       ` Dmitry Torokhov
2009-10-15 21:33         ` Éric Piel
2009-10-15 21:59           ` Dmitry Torokhov
2009-10-15 22:44             ` Éric Piel
2009-10-21 19:34             ` Éric Piel
2009-10-21 20:20               ` Dmitry Torokhov
2009-10-22 16:10                 ` Éric Piel
2009-10-22 16:22                   ` Dmitry Torokhov
2009-10-22 17:48                     ` Éric Piel
2009-10-22 18:19                       ` Dmitry Torokhov
2009-10-22 18:32                         ` Dmitry Torokhov
2009-10-23  8:08                         ` Éric Piel
2009-10-23  8:58                           ` Dmitry Torokhov
2009-10-23  9:21                             ` Éric Piel
2009-10-23 16:31                               ` Dmitry Torokhov
2009-10-25 11:47                                 ` Éric Piel
2009-10-25 19:07                                   ` Dmitry Torokhov

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=20091018075127.GH3935@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=eric.piel@tremplin-utc.net \
    --cc=gregkh@suse.de \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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).