From: Marcel Holtmann <marcel@holtmann.org>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 2/2] Bluetooth: Do not set HCI_RAW when HS enabled
Date: Fri, 11 Nov 2011 23:29:57 +0900 [thread overview]
Message-ID: <1321021801.15441.397.camel@aeonflux> (raw)
In-Reply-To: <1321020867-8938-2-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
> net/bluetooth/hci_core.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c
> index 189bada..1b08e4b 100644
> --- a/net/bluetooth/hci_core.c
> +++ b/net/bluetooth/hci_core.c
> @@ -51,6 +51,7 @@
>
> #include <net/bluetooth/bluetooth.h>
> #include <net/bluetooth/hci_core.h>
> +#include <net/bluetooth/l2cap.h>
>
> #define AUTO_OFF_TIMEOUT 2000
>
> @@ -570,8 +571,9 @@ int hci_dev_open(__u16 dev)
> if (test_bit(HCI_QUIRK_RAW_DEVICE, &hdev->quirks))
> set_bit(HCI_RAW, &hdev->flags);
>
> - /* Treat all non BR/EDR controllers as raw devices for now */
> - if (hdev->dev_type != HCI_BREDR)
> + /* Treat all non BR/EDR controllers as raw devices if
> + enable_hs is not set */
> + if (hdev->dev_type != HCI_BREDR && !enable_hs)
> set_bit(HCI_RAW, &hdev->flags);
this is fine with me. Even while the include of l2cap.h is kinda nasty.
Maybe the enable_hs variable actually needs to be moved into hci_*.c
files and not stay inside L2CAP.
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2011-11-11 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 14:14 [RFC 1/2] Bluetooth: Allow to change type for virtual HCI Emeltchenko Andrei
2011-11-11 14:14 ` [RFC 2/2] Bluetooth: Do not set HCI_RAW when HS enabled Emeltchenko Andrei
2011-11-11 14:29 ` Marcel Holtmann [this message]
2011-11-11 14:43 ` Emeltchenko Andrei
2011-11-11 14:28 ` [RFC 1/2] Bluetooth: Allow to change type for virtual HCI Marcel Holtmann
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=1321021801.15441.397.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.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