Linux wireless drivers development
 help / color / mirror / Atom feed
From: "mohamed salim abbas" <mabbaswireless@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Reinette Chatre" <reinette.chatre@intel.com>,
	linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net,
	"Mohamed Abbas" <mabbas@linux.intel.com>
Subject: Re: [PATCH] mac80211: notify mac from low level driver (iwlwifi)
Date: Fri, 4 Apr 2008 16:34:06 -0700	[thread overview]
Message-ID: <b3153e950804041634k2c3fd960h3e118deb7c42f0e7@mail.gmail.com> (raw)
In-Reply-To: <1207345183.3625.18.camel@johannes.berg>

On 4/4/08, Johannes Berg <johannes@sipsolutions.net> wrote:
>
> On Fri, 2008-04-04 at 14:35 -0700, mohamed salim abbas wrote:
> > On 4/4/08, Johannes Berg <johannes@sipsolutions.net> wrote:
> > >
> > > > + * This function must be called by low level driver to inform mac80211 of
> > > > + * low level driver status change or force mac80211 to re-assoc for low
> > > > + * level driver internal error that require re-assoc. A good example to use
> > > > + * this notification to call mac80211 after suspend/resume, some NIC require
> > > > + * re-assoc.
> > >
> > > I think the suspend/resume text should be dropped since IMHO that
> > > requires more work, reprogramming all the hardware crypto keys for
> > > example.
>
> > I can remove the suspend/resume text will be that good enough?
>
> Sure. I hope at some point somebody will implement proper suspend/resume
> (i.e. when the suspend callback is invoked all interfaces, stations,
> keys etc. are removed from the driver) but that's a lot more work. That
> you mention suspend/resume though makes me wonder: does iwlwifi store
> all that information locally and restore it to the hardware so that it
> can actually work with this across suspend/resume? For b43, I at least
> need to reset all WEP keys.

for iwl the driver on suspend behave like the device is going down, on
resume the driver reload the firmware and start fresh. the driver does
save some data to restore on resume.
I guess we can enhance on this to handle more scenario, but atleast
this is good enough for iwl driver.

>
> Thanks,
> johannes
>
>

  reply	other threads:[~2008-04-04 23:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 23:08 [PATCH] mac80211: notify upper layers after lower Reinette Chatre
2008-04-03 23:08 ` [PATCH] mac80211: notify mac from low level driver (iwlwifi) Reinette Chatre
2008-04-04 14:46   ` Johannes Berg
2008-04-04 21:35     ` mohamed salim abbas
2008-04-04 21:39       ` Johannes Berg
2008-04-04 23:34         ` mohamed salim abbas [this message]
2008-04-04 23:47           ` Johannes Berg
2008-04-04 23:55             ` mohamed salim abbas
2008-04-04 14:44 ` [PATCH] mac80211: notify upper layers after lower Johannes Berg

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=b3153e950804041634k2c3fd960h3e118deb7c42f0e7@mail.gmail.com \
    --to=mabbaswireless@gmail.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mabbas@linux.intel.com \
    --cc=reinette.chatre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox