All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: Andrey Yurovsky <andrey@cozybit.com>,
	Bing Zhao <bzhao@marvell.com>, Dan Williams <dcbw@redhat.com>,
	Amitkumar Karwar <akarwar@marvell.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"libertas-dev@lists.infradead.org"
	<libertas-dev@lists.infradead.org>
Subject: Re: [PATCH] libertas: Add auto deep sleep support for SD8385/SD8686/SD8688
Date: Fri, 18 Sep 2009 09:37:42 +0200	[thread overview]
Message-ID: <200909180937.42727.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <20090917161154.GA877@Chamillionaire.breakpoint.cc>

> I agree on this. Debugfs is for debug only and should stay
> that way. What do other driver in regard to this?

I see this now as an example where a Manufacturer (Marvell) 
starts to work with the community, has a nice feature (probably 
bacause of customer-request) and cannot get this into the kernel 
because of this issue :-)


Debugfs isn't suitable for anything except debugging. It is, per 
definition, an interface for developers that want to debug it. 
The idea is that a kernel for end-user devices won't even have 
debugfs compiled in.

If libertas currently does use debugfs for something != 
debugging?  I don't know, but than that has been a lapse, an 
oversight. Let's not do that oversight again.


So you can use

* iwpriv
* sysfs
* kernel module parameters
* nl80211/cfg80211
* Maybe the new "stable debugfs" proposed by Rostedt (see the
  Article "A stable debugfs" on http://lwn.net/Articles/350463/,
  but here it's not even clear that this will come).

For me, iwpriv seems the best candidate as long as libertas 
doesn't have a cfg80211/nl80211 interface.



> I hardly belive that the libertas driver is the only "deep
> sleep" user. 

I think that ATH6K WLAN devices might be candidates for this, 
too. If the interface is "iwpriv XXX deepsleep 0" / "iwpriv XXX 
deepsleep 1" I don't see a reason they could do it similar.


> iwconfig has an interface for this I think:
> |interface power {period N|timeout N|saving N|off}

That's something very differently.


-- 
http://www.holgerschurig.de

  parent reply	other threads:[~2009-09-18  7:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 23:45 [PATCH] libertas: Add auto deep sleep support for SD8385/SD8686/SD8688 Bing Zhao
2009-09-15 23:41 ` Andrey Yurovsky
2009-09-16 20:20   ` Bing Zhao
2009-09-16 20:47     ` Andrey Yurovsky
2009-09-17 16:11       ` Sebastian Andrzej Siewior
2009-09-18  1:47         ` Bing Zhao
2009-09-18  7:37         ` Holger Schurig [this message]
2009-09-18 17:37           ` Dan Williams
2009-09-20 14:58 ` Dan Williams
2009-09-28 22:42   ` Bing Zhao
2009-09-29  7:04     ` Holger Schurig
2009-09-29 18:36       ` Bing Zhao
2009-09-29  7:24     ` Holger Schurig
2009-10-01 18:00     ` Dan Williams

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=200909180937.42727.hs4233@mail.mn-solutions.de \
    --to=hs4233@mail.mn-solutions.de \
    --cc=akarwar@marvell.com \
    --cc=andrey@cozybit.com \
    --cc=bzhao@marvell.com \
    --cc=dcbw@redhat.com \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sebastian@breakpoint.cc \
    /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.