From: Ville Tervo <ville.tervo@nokia.com>
To: ext Tomas Winkler <tomas.winkler@intel.com>
Cc: "marcel@holtmann.org" <marcel@holtmann.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"guy.cohen@intel.com" <guy.cohen@intel.com>,
"ron.rindjunsky@intel.com" <ron.rindjunsky@intel.com>,
Gregory Paskar <greogry.paskar@intel.com>
Subject: Re: [bluetooth-next 1/1] bluetooth: handle device reset event
Date: Wed, 24 Feb 2010 14:25:18 +0200 [thread overview]
Message-ID: <4B851AAE.10401@nokia.com> (raw)
In-Reply-To: <1266486007-25015-1-git-send-email-tomas.winkler@intel.com>
Hi Tomas,
ext Tomas Winkler wrote:
> From: Gregory Paskar <greogry.paskar@intel.com>
>
> A bluetooth device experiencing hardware failure may issue
> a HARDWARE_ERROR hci event. The reaction to this event is device
> reset flow implemented in following sequence.
>
> 1. Notify: HCI_DEV_DOWN
> 2. Reinitialize internal structures.
> 3. Call driver flush function
> 4. Send HCI reset request to the device.
> 5. Send HCI init sequence reset to the device.
> 6. Notify HCI_DEV_UP.
Drivers on some embedded platforms can disable whole bt chip with gpio
line. Actually hw reset is sometimes needed for the reset. I'm wondering
if it would be feasible to add hdev->close() and hdev->open requense to
reset code? It would force driver to do hw reset for the chip.
--
Ville
prev parent reply other threads:[~2010-02-24 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 9:40 [bluetooth-next 1/1] bluetooth: handle device reset event Tomas Winkler
2010-02-21 10:27 ` Marcel Holtmann
2010-02-24 12:25 ` Ville Tervo [this message]
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=4B851AAE.10401@nokia.com \
--to=ville.tervo@nokia.com \
--cc=greogry.paskar@intel.com \
--cc=guy.cohen@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=ron.rindjunsky@intel.com \
--cc=tomas.winkler@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).