Age | Commit message (Collapse) | Author |
|
This is loosely based on a patch by Ivan Petrov.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Reported-by: Ivan Petrov <ivan_p@hotbox.ru>
|
|
IDs 0 and 1 are AR6002, not AR6001. This is based on a patch by
Ivan Petrov, but it differs in leaving the IDs in
include/linux/mmc/sdio_ids.h
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Reported-by: Ivan Petrov <ivan_p@hotbox.ru>
|
|
e2c0650efa751a6a2220618695fa41a2a5e7d23c introduced a platform-specific
hack to check if the MMC driver and hardware handle busy signaling from
the device properly.
Since this seems to be the case, we can revert this hack now.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
... and check the return value in ar6000_activate.
[ Werner: changed ___FUNCTION__ to __func__ ]
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
-the-ar6000-1232104308
pending-tracking-hist top was MERGE-via-stable-tracking-rfkill-support-for-the-ar6000-1232104308 / 09faeb511e9e6872c79b4d1ea2f3b5fefc16f3a1 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-rfkill-support-for-the-ar6000-
stable-tracking-hist top was rfkill-support-for-the-ar6000- / e82f8ffa04ebcb05506c8e22268371c3c3b03173 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
rfkill support for the AR6000 driver
This patch adds rfkill support to the AR6000 driver. The driver does
not directly implement an rfkill device but uses the help of a special
platform device, such that the latter can retain rfkill state when the
AR6k driver is removed (e.g., because of suspend).
If an attempt is made to bring the driver up (module load, bind, or
resume) while rfkill is blocking, only the driver's data structures
are initialized, but function activation and most of the rest of the
setup is deferred until the rfkill block is removed.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
As I've mentioned before, telling the WLAN module not to sleep
with "wmiconfig -i eth0 --power maxperf" reportedly improves
network stability in some situations where otherwise disconnects
were frequent. (Sorry if this sounds rather vague. I don't have
much real data on this phenomenon. More details would be welcome.)
Paul Lever from Atheros suggested that one possible source of
trouble when not using --power maxperf could be that the module
very often takes a nap and then needs to delay new commands while
waking up, and some SDIO hosts may fail to handle the delay
properly.
The S3C2442 manual leaves it unclear whether the controller handles
this condition or not. The Linux MMC/SDIO stack explicitly polls
for busy status in MMC mode but not in SDIO mode.
I've attached a patch against andy-tracking that rather crudely
checks if the module is signalling that it's still busy while we're
about to start a new transfer, and delays in this case.
In my tests, I could not make the busy condition occur (unless I
explicitly violated the stack's synchronization), but then I hardly
see any disconnects anyway.
So it would be good if those affected by frequent loss of association
could try this patch. More precisely,
- if association with the base station is often lost, and
- "wmiconfig -i eth0 --power maxperf" improves this, then
- please apply this patch, leave WLAN power at default settings
(i.e., wmiconfig -i eth0 --power rec), and report
- if the patch had any effect on the stability of associations, and
- whether "READ WHILE BUSY !" or "WRITE WHILE BUSY !" gets
logged in dmesg.
It may make sense to temporarily put this patch into andy-tracking.
While it may be perfectly useless, it shouldn't create any new
trouble either. In case it turns out to make a difference, I'll have
to find a better place in the stack for it, so it'll be reverted
either way.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
patch
pending-tracking-hist top was MERGE-via-stable-tracking-clean-hif-warning-patch / b8c3cb615a862e2a2167127195ffbd7ff18113dd ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-clean-hif-warning-patch
stable-tracking-hist top was clean-hif-warning-patch / 37b07c166a3bcc91a2ded54daa14412fbfb7cfd0 ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
clean-hif-warning.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
|
|
This is a replacement for Atheros' HIF layer that uses the Linux SDIO
stack.
Using GPLv2, like Atheros' code this is based on.
Work in progress.
Not-Yet-Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|