From: Luciano Coelho <coelho@ti.com>
To: Troy Kisky <troy.kisky@boundarydevices.com>,
Gary Thomas <gary@mlbassoc.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wl1271 watchdog interrupt
Date: Wed, 04 Apr 2012 05:58:05 +0300 [thread overview]
Message-ID: <1333508285.24637.2.camel@cumari> (raw)
In-Reply-To: <4F7BA34C.2030001@boundarydevices.com>
On Tue, 2012-04-03 at 18:26 -0700, Troy Kisky wrote:
> On 4/2/2012 1:39 AM, Luciano Coelho wrote:
> >>> wl12xx: ERROR watchdog interrupt received! starting recovery.
> >>> wl12xx: Reading FW panic log
> >>> wl12xx: ERROR command complete timeout
> > This is a firmware bug. Can you please take the contents
> > of /sys/bus/platform/drivers/wl12xx_driver/wl12xx/fwlog and send it to
> > us so we can take a look at what's going on?
> Sorry, it isn't a firmware bug. It was a configuration problem on my
> part. The defconfig
> file I was using was enabling a TVOUT driver which this board doesn't
> have. When
> the driver wanted to blank the screen, it was turning off my slow clock
> to my WL1271.
>
> When the WL1271 later becomes idle, it goes into a low power state which
> depends upon
> slow clock. So please tell your firmware guys, "never mind."
Okay, cool that you found the reason for the problem. :) I thought it
was a firmware problem because all the symptoms show that the chip
stopped responding. :)
> >> wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x23923
> > This tells us where the PC was when the crash happened. I'll ask our
> > firmware team to analyze this.
> "Never mind...."
Cool!
Now, Gary, do you still have the same (or a similar) problem with your
setup?
--
Cheers,
Luca.
next prev parent reply other threads:[~2012-04-04 2:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 1:26 wl1271 watchdog interrupt Troy Kisky
2012-03-27 14:25 ` Gary Thomas
2012-04-02 8:39 ` Luciano Coelho
2012-04-04 1:26 ` Troy Kisky
2012-04-04 2:58 ` Luciano Coelho [this message]
2012-04-04 11:20 ` Gary Thomas
2012-04-10 6:24 ` Luciano Coelho
2012-04-10 12:05 ` Gary Thomas
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=1333508285.24637.2.camel@cumari \
--to=coelho@ti.com \
--cc=gary@mlbassoc.com \
--cc=linux-wireless@vger.kernel.org \
--cc=troy.kisky@boundarydevices.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