From: amit karwar <amitkarwar@gmail.com>
To: Brian Norris <briannorris@chromium.org>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>
Subject: Re: [RFC PATCH] Revert "mwifiex: fix system hang problem after resume"
Date: Thu, 6 Apr 2017 10:02:31 +0530 [thread overview]
Message-ID: <CAEhWJF==rVqrO3sWz2Sq-7kd=6=66rfJs7+9qu4dgeB3ONyYLg@mail.gmail.com> (raw)
In-Reply-To: <20170331202136.100342-1-briannorris@chromium.org>
On Sat, Apr 1, 2017 at 1:51 AM, Brian Norris <briannorris@chromium.org> wrote:
> This reverts commit 437322ea2a36d112e20aa7282c869bf924b3a836.
>
> This above-mentioned "fix" does not actually do anything to prevent a
> race condition. It simply papers over it so that the issue doesn't
> appear.
>
> If this is a real problem, it should be explained better than the above
> commit does, and an alternative, non-racy solution should be found.
>
> For further reason to revert this: there's ot reason we can't try
> resetting the card when it's *actually* stuck in host-sleep mode. So
> instead, this is unnecessarily creating scenarios where we can't recover
> Wifi.
>
> Cc: Amitkumar Karwar <akarwar@marvell.com>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
> ---
> Amit, please take a look. AIUI, your "fix" is wrong, and quite racy. If you
> still think it's needed, can you please propose an alternative? Or at least
> explain more why this is needed? Thanks.
>
I agree. Fix just covers the issue. We need to investigate why system
hangs when card reset is attempted in host sleep activated scenario.
Acked-by: Amitkumar Karwar <amitkarwar@gmail.com>
Regards,
Amitkumar Karwar
next prev parent reply other threads:[~2017-04-06 4:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 20:21 [RFC PATCH] Revert "mwifiex: fix system hang problem after resume" Brian Norris
2017-04-01 16:20 ` Dmitry Torokhov
2017-04-06 4:32 ` amit karwar [this message]
2019-08-03 1:06 ` Brian Norris
2019-08-03 1:55 ` Kalle Valo
2019-08-03 2:02 ` Brian Norris
2019-08-03 2:08 ` 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='CAEhWJF==rVqrO3sWz2Sq-7kd=6=66rfJs7+9qu4dgeB3ONyYLg@mail.gmail.com' \
--to=amitkarwar@gmail.com \
--cc=akarwar@marvell.com \
--cc=briannorris@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jeffy.chen@rock-chips.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.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).