linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@nokia.com>
To: "ext Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Eliad Peller <eliad@wizery.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] wl1271: add recover testmode command
Date: Mon, 01 Nov 2010 23:42:25 +0200	[thread overview]
Message-ID: <1288647745.21112.76.camel@powerslave> (raw)
In-Reply-To: <AANLkTin+RQ8zjbQKFcZJjoVcT=GkuMYTYEbt47TFuAC6@mail.gmail.com>

On Mon, 2010-11-01 at 22:21 +0100, ext Gábor Stefanik wrote:
> On Mon, Nov 1, 2010 at 9:59 PM, Eliad Peller <eliad@wizery.com> wrote:
> >>> add RECOVER testmode command.
> >>> this command triggers a recovery sequence (by enqueueing a recovery_work).
> >>>
> >>> Signed-off-by: Eliad Peller <eliad@wizery.com>
> >>> ---
> >>
> >> So, the point of this patch is to allow hardware recovery from the
> >> userspace? In what kind of scenario do you need this?
> >>
> >
> > yes.
> > it's mainly for testing (or if we want to recover manually for some reason).
> > this is why i implemented it as a testmode command.
> 
> Isn't testmode for features used during regulatory testing, that the
> user should be unable to access to ensure further regulatory
> compliance?

Not exactly, it's just an interface to be used during production (and
possibly R&D) tests.  In the specific case of wl12xx, we use it for
production-line testing and for calibration and testing during R&D.

A normal user shouldn't use this by default (all distros and device
manufacturers should have it disabled in the kernel), but there's no way
to prevent a hacker from enabling it in a custom kernel.

In any case, I'm not sure I really like this idea of a HW recovery test
command.  This should really be done automatically by the driver and,
with Juuso's implementation plus the watchdog, we shouldn't really need
it.

-- 
Cheers,
Luca.


  reply	other threads:[~2010-11-01 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 12:09 [PATCH 1/2] wl1271: handle HW watchdog interrupt Eliad Peller
2010-10-27 12:09 ` [PATCH 2/2] wl1271: add recover testmode command Eliad Peller
2010-11-01 13:24   ` Luciano Coelho
2010-11-01 20:59     ` Eliad Peller
2010-11-01 21:21       ` Gábor Stefanik
2010-11-01 21:42         ` Luciano Coelho [this message]
2010-11-02  7:05           ` Eliad Peller
2010-11-02  7:34             ` Luciano Coelho
2010-11-02 10:10   ` Luciano Coelho
2010-11-01 13:22 ` [PATCH 1/2] wl1271: handle HW watchdog interrupt Luciano Coelho
2010-11-01 20:49   ` Eliad Peller
2010-11-02 10:11 ` Luciano Coelho
2010-11-02 11:10   ` Eliad Peller

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=1288647745.21112.76.camel@powerslave \
    --to=luciano.coelho@nokia.com \
    --cc=eliad@wizery.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.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).