All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@nokia.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	linville@tuxdriver.com, yi.zhu@intel.com,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: make listen_interval be configurable by low level driver
Date: Tue, 15 Jul 2008 10:21:16 +0300	[thread overview]
Message-ID: <87od4zd34j.fsf@nokia.com> (raw)
In-Reply-To: <1ba2fa240807141434k5260e6b9q6468b450fccba3e7@mail.gmail.com> (ext Tomas Winkler's message of "Tue\, 15 Jul 2008 00\:34\:24 +0300")

Tomas Winkler <tomasw@gmail.com> writes:

>>
>> This stuff is very much hardware dependent, I don't deny that, but
>> still I would assume that the basic principles are almost the same. We
>> just need to come up with a good interface for the drivers. Sure, it's
>> more work now, but if we don't do it, PSM support will eventually get
>> really messy because all drivers do it somehow differently.
>>
> This patch only sets value of listen interval from the driver I just
> think this is exactly what you are suggesting.

No, I don't suggest that. I understood that for setting the
listen_interval you are after something like this:

         sysfs?                 register_hw()
user   ---------->   driver    -------------->  mac80211

(Please correct me if I misunderstood this.)

But I think that the flow should be like this:

       WE/cfg80211                config()
user   ---------->   mac80211  -------------->  driver

So that mac80211 would be one making the choice for the listen value
based on user input. But what the user input would be, that's an
another question.

> This is only required for sending correct value of listen interval
> to AP in association. Anything else is handled in the driver or
> firmware anyway.

Yes, driver will pass the information to the firmware. But I still
think mac80211 should make the decision, and the driver should be only
forwarding mac80211 decisions to the firmware.

> This patch should go in and we can reconsider it when other HW
> driver will implement PS so we can see the bigger picture.

I guess it's a good compromise for now, but as long as we change it
later.

-- 
Kalle Valo

  reply	other threads:[~2008-07-15  7:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 12:31 [PATCH 1/2] mac80211: pass dtim_period to low level driver Tomas Winkler
2008-07-14 12:31 ` [PATCH 2/2] mac80211: make listen_interval be configurable by " Tomas Winkler
2008-07-14 12:38   ` Johannes Berg
2008-07-14 12:46     ` Tomas Winkler
2008-07-14 13:26       ` Kalle Valo
2008-07-14 21:34         ` Tomas Winkler
2008-07-15  7:21           ` Kalle Valo [this message]
2008-07-15  7:30             ` Kalle Valo
2008-07-15  8:15             ` Johannes Berg
2008-07-15  8:13           ` Johannes Berg
2008-07-15  8:12         ` Johannes Berg
2008-07-15  8:29           ` Tomas Winkler
2008-07-15  8:41             ` Johannes Berg
2008-07-15  9:58               ` Helmut Schaa
2008-07-15 10:42               ` Tomas Winkler
2008-07-15 19:35             ` Kalle Valo
2008-07-15 19:30           ` Kalle Valo
2008-07-14 13:13     ` Kalle Valo
2008-07-14 12:36 ` [PATCH 1/2] mac80211: pass dtim_period to " Johannes Berg
2008-07-14 12:38   ` Tomas Winkler
2008-07-14 12:40     ` Johannes Berg
2008-07-14 13:17 ` Kalle Valo

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=87od4zd34j.fsf@nokia.com \
    --to=kalle.valo@nokia.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tomasw@gmail.com \
    --cc=yi.zhu@intel.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 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.