From: Johan Hedberg <johan.hedberg@gmail.com>
To: zhangfei gao <zhangfei.gao@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Any flag indicating bt/fm is ready to run "hcitool cmd"
Date: Thu, 13 Jan 2011 14:26:22 +0200 [thread overview]
Message-ID: <20110113122622.GA31759@jh-x301> (raw)
In-Reply-To: <AANLkTi=TREFQbrwpt1QacoM+ehgJK9uZjBHib6t1pk7-@mail.gmail.com>
Hi,
On Thu, Jan 13, 2011, zhangfei gao wrote:
> > The HCIDEVUP ioctl is at least synchronized with the open() callback for
> > the HCI driver so in that sense if the driver is working fine it should
> > be possible to send commands when it returns. There is however an issue
> > with existing kernels that HCIDEVUP doesn't wait for all of the kernels
> > own HCI commands to finish before returning to user space. There was a
> > patch sent for this some time ago which you might be interested in
> > trying: http://marc.info/?l=linux-bluetooth&m=129296529630642&w=4
>
> Really thanks Johan,
> The patch synchronize hci_dev_open, it solve the problem we met, and
> "hcitool cmd" could immediately send after "hciconfig hci0 up" without
> problem.
Good to hear that it's working now.
> By the way, is this patch already in the kernel?
At least it's in the bluetooth-next tree:
http://git.kernel.org/?p=linux/kernel/git/padovan/bluetooth-next-2.6.git;a=commitdiff;h=23bb57633df97ede067ea26f3cdc8a7ba2cd8109
Johan
prev parent reply other threads:[~2011-01-13 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 7:02 Any flag indicating bt/fm is ready to run "hcitool cmd" zhangfei gao
2011-01-12 8:37 ` Johan Hedberg
2011-01-13 6:53 ` zhangfei gao
2011-01-13 12:26 ` Johan Hedberg [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=20110113122622.GA31759@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zhangfei.gao@gmail.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