linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: "Levi, Shahar" <shahar_levi@ti.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: WL1271: WLAN_IRQ not working
Date: Tue, 28 Jun 2011 11:19:59 -0700	[thread overview]
Message-ID: <4E0A1B4F.8080700@boundarydevices.com> (raw)
In-Reply-To: <BANLkTikp+58Ae14a1OXr0F_OSsip69++yQ@mail.gmail.com>

On 6/27/2011 11:19 PM, Levi, Shahar wrote:
> On Tue, Jun 28, 2011 at 5:56 AM, Troy Kisky
> <troy.kisky@boundarydevices.com> wrote:
>> Hi
> Hi Troy,
> 
>>
>> I trying to get an LSR WL1271 sdio module to work. Everything seems to
>> work fine until the WLAN_IRQ pin should go high, but it never does. Checking
>> with a scope shows constant low. proc/interrupts also says 0. I'm using
>> 3.0.0-rc4 with patches for non-mainline board. If I make the interrupt
>> gp a high output, I can raise the level of the WLAN_IRQ pin slightly,
>> but it is still a logic 0.
>>
>>
>> tiwi_r2_datasheet.pdf says interrupts are "active-low or falling-edge"
>>
>> So, why does the driver request an active high interrupt? I'm guessing
>> datasheet bug.
>>
>> Anyway, here are the messages I'm getting with most debugging turned on,
>> if someone is willing to take a look.
>>
>> Thanks
>> Troy
> Could you possibly check the irq pin setting fit to your platform? It
> is read via wl12xx_get_platform_data().
> The driver irq is HIGH polarity level. In case your platform not
> support level you can switch to edge via
> WL12XX_PLATFORM_QUIRK_EDGE_IRQ.
> 
> All the best,
> Shahar
> 

Thanks for taking a look. I'm pretty sure it is a hardware problem and
not software. proc/interrupts is showing the correct irq as claimed.
Looking at a scope, I'm just getting no activity on the WLAN_IRQ pin.


The datasheet says that the slow clock is 32768 HZ +/- 150 ppm. Mine
currently measures 32650. This needs fixed, but is unlikely to be my
problem isn't it?

Perhaps I have a power up sequence problem ?


wbr
Troy


  reply	other threads:[~2011-06-28 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28  2:56 WL1271: WLAN_IRQ not working Troy Kisky
2011-06-28  6:19 ` Levi, Shahar
2011-06-28 18:19   ` Troy Kisky [this message]
2011-06-30 18:46     ` Krakowski, Oz
     [not found] ` <BANLkTimKSfgE7SOPVDhvOcDB5ox6uyPc_Q@mail.gmail.com>
2011-06-30 19:05   ` Troy Kisky
2011-06-30 19:20     ` Krakowski, Oz
2011-06-30 20:00       ` Troy Kisky
2011-07-01 23:21         ` Troy Kisky

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=4E0A1B4F.8080700@boundarydevices.com \
    --to=troy.kisky@boundarydevices.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shahar_levi@ti.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).