All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Weinlader <dan@weinlader.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k driver failure requiring power cycle?
Date: Fri, 06 May 2011 12:03:33 -0400	[thread overview]
Message-ID: <4DC41BD5.3050000@weinlader.org> (raw)
In-Reply-To: <BANLkTinu6DxvUyug9+8xspWQi7drP2hUyQ@mail.gmail.com>

On 5/6/2011 10:49 AM, Adrian Chadd wrote:
> I've not come across it before. But you could in theory do a complete
> chip reset? Or even put the chip completely to sleep (MAC + BB +
> radio) and wake it up?
>
> What do others think?

Thanks for the response Adrian. Can a full chip reset be done from user 
land?

Regards,

Dan

>
>
> Adrian
>
> On 6 May 2011 19:01, Daniel Weinlader<dan@weinlader.org>  wrote:
>> I am planning on using an SR-71E (AR9280) radio with the ath9k driver in
>> an embedded device and was wondering if I might encounter a failure mode
>> that requires power cycling the radio? Has anyone ever encountered a
>> such failure that a reboot just would not fix?
>>
>> I can programmatically bring the interface down and back up again, and
>> even reboot the machine, but power cycling it would be a bit more
>> problematic. But I would rather find out now if it is required, than
>> when it is in the field.
>>
>> Regards,
>>
>> Dan
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>

  reply	other threads:[~2011-05-06 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 11:01 [ath9k-devel] ath9k driver failure requiring power cycle? Daniel Weinlader
2011-05-06 14:49 ` Adrian Chadd
2011-05-06 16:03   ` Daniel Weinlader [this message]
2011-05-09  4:43     ` Mohammed Shafi

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=4DC41BD5.3050000@weinlader.org \
    --to=dan@weinlader.org \
    --cc=ath9k-devel@lists.ath9k.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.