summaryrefslogtreecommitdiffstats
path: root/drivers/base/firmware_class.c
diff options
context:
space:
mode:
authorkay.sievers@vrfy.org <kay.sievers@vrfy.org>2005-04-18 21:57:31 -0700
committerGreg KH <greg@press.kroah.org>2005-04-18 21:57:31 -0700
commit6897089c5f7989603ccb9c696050470ba1dbd262 (patch)
tree858c77a9aefc2f7b7b2c310b07e243d19a78e148 /drivers/base/firmware_class.c
parent6f31e42221c7deae4527136ce0dd73990d8bc1d1 (diff)
downloadop-kernel-dev-6897089c5f7989603ccb9c696050470ba1dbd262.zip
op-kernel-dev-6897089c5f7989603ccb9c696050470ba1dbd262.tar.gz
[PATCH] add TIMEOUT to firmware_class hotplug event
On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote: > The current implementation of the firmware class breaks a fundamental > assumption in udevd: that the physical device can be initialised fully > prior to executing the next event for that device. Here we add a TIMEOUT value to the hotplug environment of the firmware requesting event. I will adapt udevd not to wait for anything else, if it finds a TIMEOUT key. Signed-off-by: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/base/firmware_class.c')
-rw-r--r--drivers/base/firmware_class.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
index 26c9464..97fe13f 100644
--- a/drivers/base/firmware_class.c
+++ b/drivers/base/firmware_class.c
@@ -102,6 +102,9 @@ firmware_class_hotplug(struct class_device *class_dev, char **envp,
if (add_hotplug_env_var(envp, num_envp, &i, buffer, buffer_size, &len,
"FIRMWARE=%s", fw_priv->fw_id))
return -ENOMEM;
+ if (add_hotplug_env_var(envp, num_envp, &i, buffer, buffer_size, &len,
+ "TIMEOUT=%i", loading_timeout))
+ return -ENOMEM;
envp[i] = NULL;
OpenPOWER on IntegriCloud