From: Balakrishna Godavarthi <bgodavar@codeaurora.org>
To: marcel@holtmann.org, johan.hedberg@gmail.com, mka@chromium.org
Cc: linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
rtatiya@codeaurora.org, hemantg@codeaurora.org,
c-hbandi@codeaurora.org, linux-arm-msm@vger.kernel.org,
Balakrishna Godavarthi <bgodavar@codeaurora.org>
Subject: [PATCH v1 0/1] Enable subsystem restart for Qualcomm bluetooth chip wcn3990.
Date: Mon, 9 Jul 2018 21:46:56 +0530 [thread overview]
Message-ID: <20180709161657.26609-1-bgodavar@codeaurora.org> (raw)
In many platforms Bluetooth chip wcn3990 is a discrete chip connected
via UART lines to app processor. if the chip goes into bad state
i.e. into hard fault exception routine, which will not further respond
to any commands from HOST via UART. In that case wcn3390 will intimate
HOST by generating hardware error. Host stack will initiate a close
and reopen of the hci driver. Prior to sending hard ware error, wcn3990
has a capability of sending the RAM dump i.e. memory dump of the BT chip.
this will help us to fix stability issues of the SoC. We at QCA driver
read the dump packets and store via devcoredump().
We perform restart after collecting the ram dump of the SoC.
Harish Bandi (1):
Bluetooth: hci_qca: Sub system restart support for WCN3990
drivers/bluetooth/btqca.h | 8 ++
drivers/bluetooth/hci_qca.c | 261 ++++++++++++++++++++++++++++++++++++
2 files changed, 269 insertions(+)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2018-07-09 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 16:16 Balakrishna Godavarthi [this message]
2018-07-09 16:16 ` [PATCH v1 1/1] Bluetooth: hci_qca: Sub system restart support for WCN3990 Balakrishna Godavarthi
2018-07-09 16:57 ` [PATCH v1 0/1] Enable subsystem restart for Qualcomm bluetooth chip wcn3990 Balakrishna Godavarthi
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=20180709161657.26609-1-bgodavar@codeaurora.org \
--to=bgodavar@codeaurora.org \
--cc=c-hbandi@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mka@chromium.org \
--cc=rtatiya@codeaurora.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).