- 28 Jan, 2008 40 commits
-
-
David Woodhouse authored
Also, check that suspend is refused if HOST_SLEEP_CFG hasn't been done. Signed-off-by:
David Woodhouse <dwmw2@infradead.org> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
We (ab)use priv->fw_ready to stop the worker thread from sending more commands or data after the response to the HOST_SLEEP_ACTIVATE command comes in. And we set it from the callback function _directly_ to ensure that the worker thread sees it immediately; if we did it in lbs_suspend() after waking up, that might be too late. Signed-off-by:
-
David Woodhouse authored
We want it to send the HOST_SLEEP_ACTIVATE command on the way down... Signed-off-by:
-
David Woodhouse authored
This way, it looks more like a normal function. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
In particular, we shouldn't be waking the queues in lbs_host_to_card_done() any more. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Especially in the light of OLPC trac #5461, in which the firmware starts sending us seemingly random command responses which bear little relation to the command we sent it. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Otherwise the device won't let us change channels. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
sparse was getting on my tits. Signed-off-by:
-
Dan Williams authored
Signed-off-by:
Dan Williams <dcbw@redhat.com> Signed-off-by:
-
Dan Williams authored
Signed-off-by:
-
Dan Williams authored
Signed-off-by:
-
Dan Williams authored
Signed-off-by:
-
David Woodhouse authored
If stupid people like me give it arguments with the wrong type (like a pointer to the structure, for example, instead of the structure itself), then we should probably notice that at compile time. Otherwise, much confusion ensues. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
Bad dcbw. Always test on big-endian, or at least use sparse. Signed-off-by:
-
Dan Williams authored
Make it a struct cmd_header, since that's what it is, and clean up the places that it's used. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
This prevents us from trying to remove it when it didn't exist, in the error case. Signed-off-by:
-
David Woodhouse authored
Amazing what interesting things the compiler will tell you if you let it know what types you expect to be passing around. Signed-off-by:
-
Dan Williams authored
Signed-off-by:
-
Dan Williams authored
A simple callback which copies the response back into the command buffer that was used to send the command to the card. Will allow for direct command processing outside the mega-switches in cmd.c and cmdresp.c. Signed-off-by:
-
Dan Williams authored
Move direct command handling through __lbs_cmd() over to using the header as the first member of the command structure, and only define the __lbs_cmd() callback in one place rather than 3. Convert boot2 version command to new usage. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
No need to busy-wait, even if we did have a 100ms delay in the loop. This makes it easier to support the new 'firmware ready' event which is in the new firmware, too. Signed-off-by:
-
David Woodhouse authored
Increase the delay between issuing the RESET command and the usb reset, and be prepared to discard more than one 'normal' packet from it before it resets. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
Dan Williams authored
Total overkill to have an array when there's only one command in it. Signed-off-by:
-
David Woodhouse authored
The firmware is always initialised before we register the netdevices. It's not possible for pre_open_check() to fail. One day we might try loading firmware in ->open(), but still it won't be just a _check_, like this. Signed-off-by:
-
