On Mon, Jan 29, 2007 at 10:55:48AM +0100, Jiri Kosina wrote:
quoted text
> Changing module parameter values through sysfs is not a very nice idea,=
=20
quoted text
> because the change of the value is indeed silent - the driver is not=20
> notified in any way, that the value has changed. So the driver should tak=
e=20
quoted text
> care of it by itself, which is not a nice thing.

There is module_param_call() - used at least by drivers/md/md.c:

static int get_ro(char *buffer, struct kernel_param *kp)
=2E..
static int set_ro(const char *val, struct kernel_param *kp)
=2E..
module_param_call(start_ro, set_ro, get_ro, NULL, S_IRUSR|S_IWUSR);