From: Suraj <suraj@Atheros.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Suraj Sumangala <Suraj.Sumangala@Atheros.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>
Subject: Re: [RFC v2] Bluetooth: Provide access to reassembled Rx packets
Date: Mon, 26 Jul 2010 23:53:14 +0530 [thread overview]
Message-ID: <4C4DD292.60001@Atheros.com> (raw)
In-Reply-To: <1280157203.2621.48.camel@localhost.localdomain>
Hi Marcel,
On 7/26/2010 8:43 PM, Marcel Holtmann wrote:
> Hi Suraj,
>
>> Provide the HCI transport driver access to reassembled Rx packets before
>> sending to Host.
>
> you still haven't answered my question on why you want this. It makes no
> sense to me to relay all packets back to the driver. That is just a
> waste of CPU cycles.
>
> Regards
>
> Marcel
>
>
The requirement is simple. The driver need to know the status of certain
vendor specific commands by checking the parameters of Command complete
events.
We also have a requirements to verify the status of HCI RESET command to
update power management feature.
If you are concerned about CPU cycle, we can limit this only for HCI
events and not for ACL/SCO packets.
Please do let me know if you think there is an alternate way so that the
HCI transport driver can access to HCI events.
Regards
Suraj
next prev parent reply other threads:[~2010-07-26 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 6:34 [RFC v2] Bluetooth: Provide access to reassembled Rx packets Suraj Sumangala
2010-07-26 15:13 ` Marcel Holtmann
2010-07-26 18:23 ` Suraj [this message]
2010-07-26 22:42 ` Marcel Holtmann
2010-07-27 2:23 ` Suraj
2010-07-27 4:48 ` Suraj
2010-07-27 5:14 ` Marcel Holtmann
2010-07-27 15:36 ` Suraj
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=4C4DD292.60001@Atheros.com \
--to=suraj@atheros.com \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=Suraj.Sumangala@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.