[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] hci command timers
We should release the timer when the host controller is ready to receive a new command from the host. In some cases this is when we receive a Command Complete and in some cases this is when we receive a Command Status. Though I agree that, we shouldn't always delete the timer when we receive a Command Status. I would be more correctly if we only deleted the timers for those command that have set the timers.
I don't have time to go through this in the code right now, so you more than welcome to do it :)
>From: Gordon McNutt [mailto:firstname.lastname@example.org]
>Sent: Wednesday, March 14, 2001 11:09 PM
>Subject: [bluetooth-dev] hci command timers
>Some HCI commands use send_cmd_block() and some don't. Only those that
>do start the command timer.
>However, whenever we get a Command_Status event we always release the
>command timer. And then, when we get a Command_Complete event, we
>sometimes release the command timer.
>Unless I'm missing something, this could be bad (not BAD, but bad). We
>might prematurely wake up user processes (before their commands are
>really done) and delete non-existing timers.
>I'm thinking we should only delete timers when we get the
>Command_Complete event. Am I missing something?
>To unsubscribe from this list: send the line "unsubscribe
>the body of a message to email@example.com
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to firstname.lastname@example.org