From: Santosh Shukla <sshukla82@hotmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: wl1271: how to use without runtime pm
Date: Wed, 15 Feb 2012 09:57:39 +0000 (UTC) [thread overview]
Message-ID: <loom.20120215T101548-412@post.gmane.org> (raw)
In-Reply-To: 1293782416.15791.10.camel@powerslave
Is there any resolution for this mail thread? I too came across this problem. My
H/W has WLAN_EN bit high( a h/w Switch) and Physically can not be configured for
RUN-TIME feature. So, I will have to run wl128x compat module without RUN-TIME
support.
Could any one suggest workaround for same so that I don't see SDIO WR/RD error
for sequence of wireless node down , followed by up (referred in this mail
thread).
Appreciate your opinion.
prev parent reply other threads:[~2012-02-15 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 21:07 wl1271: how to use without runtime pm Sergey Matyukevich
2010-12-29 21:22 ` Ohad Ben-Cohen
2010-12-30 22:08 ` Sergey Matyukevich
2010-12-31 8:00 ` Luciano Coelho
2012-02-15 9:57 ` Santosh Shukla [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20120215T101548-412@post.gmane.org \
--to=sshukla82@hotmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).