linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/4] iwlwifi: Limit number of firmware reload
Date: Wed, 23 Feb 2011 11:57:21 +0100	[thread overview]
Message-ID: <20110223105720.GA11916@redhat.com> (raw)
In-Reply-To: <1298317536-5071-2-git-send-email-wey-yi.w.guy@intel.com>

Hi Wey

On Mon, Feb 21, 2011 at 11:45:33AM -0800, Wey-Yi Guy wrote:
> If device has serious problem and cause firmware can not recover itself.
> Keep reloading firmware will not help, it can only fill up the syslog and
> lock up the system because busy reloading.
Filling up logs could be simply avoided by limiting number of prints.

> Introduce the limit reload counter, if the reload reach the maximum within
> the pre-defined duration;stop the reload operation.
We have already one mechanism for limit too frequent firmware reload,
way not reuse it?

> +	reload_msec = jiffies_to_msecs((long) reload_jiffies -
> +				(long) priv->reload_jiffies);
What for are these (long) casts?

> +	/* firmware reload counter and timestamp */
> +	unsigned long reload_jiffies;
You do not initialize it, first reload_msec will have untrue value.

Beside, all these reload firmware mechanism are just crappy workarounds
for real firmware and/or driver bugs. Instead of creating such patches,
Intel should fix real problems in firmware and driver in first place,
such reloading will be not needed.

Stanislaw

  reply	other threads:[~2011-02-23 10:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 19:45 [PATCH 0/4] update for 2.6.39 Wey-Yi Guy
2011-02-21 19:45 ` [PATCH 1/4] iwlwifi: Limit number of firmware reload Wey-Yi Guy
2011-02-23 10:57   ` Stanislaw Gruszka [this message]
2011-02-23 15:18     ` Guy, Wey-Yi
2011-02-21 19:45 ` [PATCH 2/4] iwlwifi: Loading correct uCode again when fail to load Wey-Yi Guy
2011-02-21 19:45 ` [PATCH 3/4] iwlwifi: enable 2-wire bt coex support for non-combo device Wey-Yi Guy
  -- strict thread matches above, loose matches on Subject: below --
2011-02-21 19:06 [PATCH 0/4] update for 2.6.39 Wey-Yi Guy
2011-02-21 19:06 ` [PATCH 1/4] iwlwifi: Limit number of firmware reload Wey-Yi Guy

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=20110223105720.GA11916@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=wey-yi.w.guy@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;
as well as URLs for NNTP newsgroup(s).