Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: linux-wireless@vger.kernel.org, kaloz@openwrt.org
Subject: Re: wl1271: tx stuck in firmware
Date: Wed, 09 Apr 2014 14:49:35 +0300	[thread overview]
Message-ID: <1397044175.4418.66.camel@dubbel> (raw)
In-Reply-To: <CAGm1_ktMWV0m1-gUTe8bQT1=f9HseBKCJn22bvPAgxynpeaQLg@mail.gmail.com>

On Wed, 2014-04-09 at 12:16 +0200, Yegor Yefremov wrote:
> On Wed, Apr 9, 2014 at 11:21 AM, Luca Coelho <luca@coelho.fi> wrote:
> > On Wed, 2014-04-09 at 11:14 +0200, Yegor Yefremov wrote:
> >> On Tue, Apr 8, 2014 at 10:29 PM, Luca Coelho <luca@coelho.fi> wrote:
> >> > On Tue, 2014-04-08 at 17:28 +0200, Yegor Yefremov wrote:
> >> >> Any idea, what could be wrong?
> >> >
> >> > First of all, try a clean kernel.
> >>
> >> It is not simple to get a clean kernel. "Official" support for
> >> am335x-evmsk WLAN was added first in the upcoming 3.15 kernel. I've
> >> tried the merge window version (3.14.0-12041-g75ff24f-dirty) and get
> >> following issue:
> >>
> >> # calibrator wlan0 plt power_mode on
> >> wlcore: power up
> >> wlcore: ERROR timeout waiting for the hardware to complete initialization
> >> wlcore: ERROR timeout waiting for the hardware to complete initialization
> >> wlcore: ERROR timeout waiting for the hardware to complete initialization
> >> wlcore: ERROR firmware boot in PLT mode failed despite 3 retries
> >> command failed: Input/output error (-5)
> >
> > Okay, the main question here is, did you make any changes in the
> > wlcore/wl12xx code? As I said, the TX watchdog should *not* be
> > initialized in PLT mode.
> 
> I made not changes to any file in drivers/net/wireless/ti/
> 
> > Maybe you could add some prints in the driver to see when the watchdog
> > timer is set up? Try to add a printk in every place where
> > wl12xx_rearm_tx_watchdog_locked() is called to see where it is being
> > armed.
> 
> drivers/net/wireless/ti/wlcore/tx.c in wl1271_tx_allocate()
> 
> # calibrator wlan0 plt power_mode on
> [   93.107215] wlcore: power up
> [   93.688714] wlcore: firmware booted in PLT mode PLT_ON (PLT 6.3.10.0.133)
> # [  139.232802] YY: wl1271_tx_allocate
> [  144.241849] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery

Okay, you have a starting point. :)

Now try to look from where this is being called and so on.  I don't
think we should be calling wl1271_tx_allocate() in PLT mode either.  Try
tracing back until you find where this is coming from.

--
Luca.


  reply	other threads:[~2014-04-09 11:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 15:28 wl1271: tx stuck in firmware Yegor Yefremov
2014-04-08 20:29 ` Luca Coelho
2014-04-09  9:14   ` Yegor Yefremov
2014-04-09  9:21     ` Luca Coelho
2014-04-09 10:16       ` Yegor Yefremov
2014-04-09 11:49         ` Luca Coelho [this message]
2014-04-09 12:20           ` Arik Nemtsov
2014-04-09 12:41             ` Luca Coelho
2014-04-09 13:07               ` Arik Nemtsov
2014-04-09 13:20                 ` Yegor Yefremov
2014-04-09 13:25                   ` Arik Nemtsov
2014-04-09 15:28                     ` Yegor Yefremov
2014-04-10  7:21                       ` Yegor Yefremov
2014-04-10  7:43                         ` Arik Nemtsov

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=1397044175.4418.66.camel@dubbel \
    --to=luca@coelho.fi \
    --cc=kaloz@openwrt.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yegorslists@googlemail.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