linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
To: marcel@holtmann.org, linux-bluetooth@vger.kernel.org,
	ulf.hansson@linaro.org
Cc: chromeos-bluetooth-upstreaming@chromium.org, mka@chromium.org,
	dianders@chromium.org,
	Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] Bluetooth: btmrvl: Reset SDIO card on hang
Date: Thu, 19 Mar 2020 19:01:52 -0700	[thread overview]
Message-ID: <20200320020153.98280-1-abhishekpandit@chromium.org> (raw)


Hi Marcel,

This patch adds an error recovery mechanism to the btmrvl driver. We
have been using it on ChromeOS on kernel v4.19 and it has been on the
stable channel release of ChromeOS for a few months now.

A side effect of this change is that other functions on the same card
will be affected by the reset. The necessary patches to support this
reset have already been added to the mwifiex driver by Ulf:

11239229 New          [v3,1/3] mwifiex: Re-work support for SDIO HW reset
11239233 New          [v3,2/3] mmc: core: Drop check for mmc_card_is_removable() in mmc_rescan()
11239237 New          [v3,3/3] mmc: core: Re-work HW reset for SDIO cards

You can see more information at crbug.com/1004473

Thanks
Abhishek



Matthias Kaehlcke (1):
  Bluetooth: btmrvl: Detect hangs and force a reset of the SDIO card

 drivers/bluetooth/btmrvl_sdio.c | 24 ++++++++++++++++++++++++
 drivers/bluetooth/btmrvl_sdio.h |  1 +
 2 files changed, 25 insertions(+)

-- 
2.25.1.696.g5e7596f4ac-goog


             reply	other threads:[~2020-03-20  2:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20  2:01 Abhishek Pandit-Subedi [this message]
2020-03-20  2:01 ` [PATCH 1/1] Bluetooth: btmrvl: Detect hangs and force a reset of the SDIO card Abhishek Pandit-Subedi
2020-03-20 20:00   ` Doug Anderson
2020-03-20 20:56     ` Abhishek Pandit-Subedi

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=20200320020153.98280-1-abhishekpandit@chromium.org \
    --to=abhishekpandit@chromium.org \
    --cc=chromeos-bluetooth-upstreaming@chromium.org \
    --cc=dianders@chromium.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mka@chromium.org \
    --cc=ulf.hansson@linaro.org \
    /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).