From: "Rafał Miłecki" <zajec5@gmail.com>
To: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Cc: b43-dev@lists.infradead.org, "Rafał Miłecki" <zajec5@gmail.com>
Subject: [PATCH 0/2] ssb: updates matching specs, fix for hangs?
Date: Mon, 24 May 2010 21:50:22 +0200 [thread overview]
Message-ID: <1274730624-22922-1-git-send-email-zajec5@gmail.com> (raw)
John, I don't really know w-t policy, so please decide where we should apply
these patches. I'll try to provide some description.
We got reports of some devices hanging with ssb module, it was around SPROM
reading. AFAIK two patches are needed to fix this issue. One was already
posted by Larry: "ssb: Handle alternate SSPROM location" (however I can not
find it in w-t). Second one is attached patch for fast powerup delay.
Not sure about PMU init patch, I think it is needed to get devices working
but not sure if it affects (fixes) handing issue.
Fix of hanging sounds important and thankfully patches are quite trivial. On
the other hand we are at the end of merge window already. So please, help with
taking a decision about this.
CC-ing b43, hope it's OK.
Rafał Miłecki (2):
ssb: update PMU init to match specs
ssb: fast powerup delay calculation for PMU capable devices
drivers/ssb/driver_chipcommon.c | 24 ++++++++++++++++++++++++
drivers/ssb/driver_chipcommon_pmu.c | 17 +++++++----------
2 files changed, 31 insertions(+), 10 deletions(-)
next reply other threads:[~2010-05-24 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 19:50 Rafał Miłecki [this message]
2010-05-24 19:50 ` [PATCH 1/2] ssb: update PMU init to match specs Rafał Miłecki
2010-05-24 19:50 ` [PATCH 2/2] ssb: fast powerup delay calculation for PMU capable devices Rafał Miłecki
2010-06-20 12:34 ` [PATCH 0/2] ssb: updates matching specs, fix for hangs? Rafał Miłecki
2010-06-20 12:41 ` Hauke Mehrtens
2010-06-20 12:56 ` Rafał Miłecki
2010-06-20 16:20 ` John W. Linville
2010-06-20 18:28 ` Rafał Miłecki
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=1274730624-22922-1-git-send-email-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).