bluetooth: replace schedule_timeout()
Subsystems (2)
PATCH 1/1 bluetooth: replace schedule_timeout()
I would appreciate any comments from the janitors list. This is one (of many) cases where I made a decision about replacing
set_current_state(TASK_INTERRUPTIBLE);schedule_timeout(some_time);
with
msleep(jiffies_to_msecs(some_time));
msleep() is not exactly the same as the previous code, but I only did this replacement where I thought long delays were *desired*. If this is not the case here, then just disregard this patch.
Thanks,
Nish
Applys-to: 2.6.7
Description: Uses msleep() instead of schedule_timeout() to guarantee the task delays at least the desired time amount.
drivers/bluetooth/bluecard_cs.c +2 -4
@@ -776,8 +776,7 @@ int bluecard_open(bluecard_info_t *info)outb (0x80 , iobase +0x30 );/* Wait some time */ -set_current_state (TASK_INTERRUPTIBLE ); -schedule_timeout (HZ /100 ); +msleep (100 );/* Turn FPGA on */ outb (0x00 , iobase +0x30 );
@@ -823,8 +822,7 @@ int bluecard_open(bluecard_info_t *info)outb ((0x0f <<RTS_LEVEL_SHIFT_BITS ) |1 , iobase +REG_RX_CONTROL );/* Timeout before it is safe to send the first HCI packet */ -set_current_state (TASK_INTERRUPTIBLE ); -schedule_timeout ((HZ *5 ) /4 );// or set it to 3/2 +msleep (1250 );/* Register HCI device */ if (hci_register_dev (hdev) <0 ) {
_______________________________________________
Kernel-janitors mailing list
[email protected]
http://lists.osdl.org/mailman/listinfo/kernel-janitors
PATCH 1/1 bluetooth: replace schedule_timeout()
I would appreciate any comments from the janitors list. This is one (of many) cases where I made a decision about replacing
set_current_state(TASK_INTERRUPTIBLE);schedule_timeout(some_time);
with
msleep(jiffies_to_msecs(some_time));
msleep() is not exactly the same as the previous code, but I only did this replacement where I thought long delays were *desired*. If this is not the case here, then just disregard this patch.
Thanks,
Nish
Applys-to: 2.6.7
Description: Uses msleep() instead of schedule_timeout() to guarantee the task delays at least the desired time amount.
drivers/bluetooth/bt3c_cs.c +1 -2
@@ -633,8 +633,7 @@ int bt3c_open(bt3c_info_t *info) }/* Timeout before it is safe to send the first HCI packet */ -set_current_state (TASK_INTERRUPTIBLE ); -schedule_timeout (HZ ); +msleep (1000 );/* Register HCI device */ err =hci_register_dev (hdev);
_______________________________________________
Kernel-janitors mailing list
[email protected]
http://lists.osdl.org/mailman/listinfo/kernel-janitors
PATCH 1/1 bluetooth: replace schedule_timeout()
In reply to Nishanth AravamudanI would appreciate any comments from the janitors list. This is one (of many) cases where I made a decision about replacing
set_current_state(TASK_INTERRUPTIBLE);schedule_timeout(some_time);
with
msleep(jiffies_to_msecs(some_time));
msleep() is not exactly the same as the previous code, but I only did this replacement where I thought long delays were *desired*. If this is not the case here, then just disregard this patch.
Thanks,
Nish
Applys-to: 2.6.7
Description: Uses msleep() instead of schedule_timeout() to guarantee the task delays at least the desired time amount.
drivers/bluetooth/btuart_cs.c +1 -2
@@ -545,8 +545,7 @@ int btuart_open(btuart_info_t *info)btuart_change_speed (info,DEFAULT_BAUD_RATE );/* Timeout before it is safe to send the first HCI packet */ -set_current_state (TASK_INTERRUPTIBLE ); -schedule_timeout (HZ ); +msleep (1000 );/* Register HCI device */ if (hci_register_dev (hdev) <0 ) {
_______________________________________________
Kernel-janitors mailing list
[email protected]
http://lists.osdl.org/mailman/listinfo/kernel-janitors
PATCH 1/1 bluetooth: replace schedule_timeout()
In reply to Nishanth AravamudanI would appreciate any comments from the janitors list. This is one (of many) cases where I made a decision about replacing
set_current_state(TASK_INTERRUPTIBLE);schedule_timeout(some_time);
with
msleep(jiffies_to_msecs(some_time));
msleep() is not exactly the same as the previous code, but I only did this replacement where I thought long delays were *desired*. If this is not the case here, then just disregard this patch.
Thanks,
Nish
Applys-to: 2.6.7
Description: Uses msleep() instead of schedule_timeout() to guarantee the task delays at least the desired time amount.
drivers/bluetooth/dtl1_cs.c +1 -2
@@ -524,8 +524,7 @@ int dtl1_open(dtl1_info_t *info)spin_unlock_irqrestore (&(info->lock), flags);/* Timeout before it is safe to send the first HCI packet */ -set_current_state (TASK_INTERRUPTIBLE ); -schedule_timeout (HZ *2 ); +msleep (2000 );/* Register HCI device */ if (hci_register_dev (hdev) <0 ) {
_______________________________________________
Kernel-janitors mailing list
[email protected]
http://lists.osdl.org/mailman/listinfo/kernel-janitors
PATCH 1/1 bluetooth: replace schedule_timeout() with
In reply to Nishanth AravamudanPlease find below the corrected version, which compiles without error for me.
I would appreciate any comments from the janitors list. This is one (of many) cases where I made a decision about replacing
set_current_state(TASK_INTERRUPTIBLE);schedule_timeout(some_time);
with
msleep(jiffies_to_msecs(some_time));
msleep() is not exactly the same as the previous code, but I only did this replacement where I thought long delays were *desired*. If this is not the case here, then just disregard this patch.
Thanks,
Nish
Applys-to: 2.6.7
Description: Uses msleep() instead of schedule_timeout() to guarantee the task delays at least the desired time amount.
drivers/bluetooth/bluecard_cs.c +3 -4
@@ -34,6 +34,7 @@#include <linux/ioport.h> #include <linux/spinlock.h> #include <linux/skbuff.h> +#include <linux/delay.h> #include <asm/io.h> #include <pcmcia/version.h>
@@ -776,8 +777,7 @@ int bluecard_open(bluecard_info_t *info)outb (0x80 , iobase +0x30 );/* Wait some time */ -set_current_state (TASK_INTERRUPTIBLE ); -schedule_timeout (HZ /100 ); +msleep (100 );/* Turn FPGA on */ outb (0x00 , iobase +0x30 );
@@ -823,8 +823,7 @@ int bluecard_open(bluecard_info_t *info)outb ((0x0f <<RTS_LEVEL_SHIFT_BITS ) |1 , iobase +REG_RX_CONTROL );/* Timeout before it is safe to send the first HCI packet */ -set_current_state (TASK_INTERRUPTIBLE ); -schedule_timeout ((HZ *5 ) /4 );// or set it to 3/2 +msleep (1250 );/* Register HCI device */ if (hci_register_dev (hdev) <0 ) {
_______________________________________________
Kernel-janitors mailing list
[email protected]
http://lists.osdl.org/mailman/listinfo/kernel-janitors
PATCH 1/1 bluetooth: replace schedule_timeout() with
In reply to Nishanth AravamudanPlease find below the corrected version, which compiles without error for me.
I would appreciate any comments from the janitors list. This is one (of many) cases where I made a decision about replacing
set_current_state(TASK_INTERRUPTIBLE);schedule_timeout(some_time);
with
msleep(jiffies_to_msecs(some_time));
msleep() is not exactly the same as the previous code, but I only did this replacement where I thought long delays were *desired*. If this is not the case here, then just disregard this patch.
Thanks,
Nish
Applys-to: 2.6.7
Description: Uses msleep() instead of schedule_timeout() to guarantee the task delays at least the desired time amount.
drivers/bluetooth/btuart_cs.c +2 -3
@@ -32,7 +32,7 @@#include <linux/ptrace.h> #include <linux/ioport.h> #include <linux/spinlock.h> - +#include <linux/delay.h> #include <linux/skbuff.h> #include <linux/string.h> #include <linux/serial.h>
@@ -545,8 +545,7 @@ int btuart_open(btuart_info_t *info)btuart_change_speed (info,DEFAULT_BAUD_RATE );/* Timeout before it is safe to send the first HCI packet */ -set_current_state (TASK_INTERRUPTIBLE ); -schedule_timeout (HZ ); +msleep (1000 );/* Register HCI device */ if (hci_register_dev (hdev) <0 ) {
_______________________________________________
Kernel-janitors mailing list
[email protected]
http://lists.osdl.org/mailman/listinfo/kernel-janitors
PATCH 1/1 bluetooth: replace schedule_timeout() with
In reply to Nishanth AravamudanPlease find below the corrected version, which compiles without error for me.
I would appreciate any comments from the janitors list. This is one (of many) cases where I made a decision about replacing
set_current_state(TASK_INTERRUPTIBLE);schedule_timeout(some_time);
with
msleep(jiffies_to_msecs(some_time));
msleep() is not exactly the same as the previous code, but I only did this replacement where I thought long delays were *desired*. If this is not the case here, then just disregard this patch.
Thanks,
Nish
Applys-to: 2.6.7
Description: Uses msleep() instead of schedule_timeout() to guarantee the task delays at least the desired time amount.
drivers/bluetooth/dtl1_cs.c +2 -3
@@ -32,7 +32,7 @@#include <linux/ptrace.h> #include <linux/ioport.h> #include <linux/spinlock.h> - +#include <linux/delay.h> #include <linux/skbuff.h> #include <linux/string.h> #include <linux/serial.h>
@@ -524,8 +524,7 @@ int dtl1_open(dtl1_info_t *info)spin_unlock_irqrestore (&(info->lock), flags);/* Timeout before it is safe to send the first HCI packet */ -set_current_state (TASK_INTERRUPTIBLE ); -schedule_timeout (HZ *2 ); +msleep (2000 );/* Register HCI device */ if (hci_register_dev (hdev) <0 ) {
_______________________________________________
Kernel-janitors mailing list
[email protected]
http://lists.osdl.org/mailman/listinfo/kernel-janitors