From: Troy Kisky <troy.kisky@boundarydevices.com>
To: "Krakowski, Oz" <ozk@ti.com>
Cc: mangesh gadre <mangeshgadre07@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: WL1271: WLAN_IRQ not working
Date: Fri, 01 Jul 2011 16:21:32 -0700 [thread overview]
Message-ID: <4E0E567C.4010003@boundarydevices.com> (raw)
In-Reply-To: <4E0CD5C4.7010702@boundarydevices.com>
On 6/30/2011 1:00 PM, Troy Kisky wrote:
> On 6/30/2011 12:20 PM, Krakowski, Oz wrote:
>> Troy,
>> On Thu, Jun 30, 2011 at 2:05 PM, Troy Kisky
>> <troy.kisky@boundarydevices.com> wrote:
>>> On 6/29/2011 11:24 PM, mangesh gadre wrote:
>>>> Hi,
>>>>
>>>> Please check if your wifi enable pin is in right state. secondly check if
>>>> regulator section of your chip is actually powering up wifi internal core .
>>>> check your circuit against standard ref circuit.
>>>> I have seen similar issue and there was some resistor missing in feedback
>>>> path of volatge regulator output path from chip. Most probably wifi section
>>>> of your chip is not powered up.
>>>
>>> I think the problem is solved, but can you point me to a "standard ref
>>> circuit" for TiWiR2. Maybe, I can avoid future problems.
>>
>> For the benefit of everyone, can you share what was the issue?
>>
>> Thanks,
>> Oz.
>
Another problem was that gpio interrupts were not working on mx53
platforms on 3.0-rc4. I just submitted a patch.
Thanks
Troy
prev parent reply other threads:[~2011-07-01 23:21 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
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 [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=4E0E567C.4010003@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mangeshgadre07@gmail.com \
--cc=ozk@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).