From: Jaganath Kanakkassery <jaganath.k.os@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Jaganath Kanakkassery <jaganathx.kanakkassery@intel.com>
Subject: [PATCH v2 06/18] Bluetooth: Define PHY flags in hdev and set 1M as default
Date: Tue, 24 Apr 2018 19:20:39 +0530 [thread overview]
Message-ID: <1524577851-17238-7-git-send-email-jaganathx.kanakkassery@intel.com> (raw)
In-Reply-To: <1524577851-17238-1-git-send-email-jaganathx.kanakkassery@intel.com>
1M is mandatory to be supported by LE controllers and the same
would be set in power on. This patch defines hdev flags for
LE PHYs and set 1M to default.
Signed-off-by: Jaganath Kanakkassery <jaganathx.kanakkassery@intel.com>
---
include/net/bluetooth/hci.h | 7 +++++++
net/bluetooth/hci_core.c | 4 ++++
2 files changed, 11 insertions(+)
diff --git a/include/net/bluetooth/hci.h b/include/net/bluetooth/hci.h
index 85ceeb9..c4105e6 100644
--- a/include/net/bluetooth/hci.h
+++ b/include/net/bluetooth/hci.h
@@ -261,6 +261,13 @@ enum {
HCI_FORCE_BREDR_SMP,
HCI_FORCE_STATIC_ADDR,
+ HCI_LE_PHY_1M_TX,
+ HCI_LE_PHY_1M_RX,
+ HCI_LE_PHY_2M_TX,
+ HCI_LE_PHY_2M_RX,
+ HCI_LE_PHY_CODED_TX,
+ HCI_LE_PHY_CODED_RX,
+
__HCI_NUM_FLAGS,
};
diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c
index cdc9616..45df3ad 100644
--- a/net/bluetooth/hci_core.c
+++ b/net/bluetooth/hci_core.c
@@ -322,6 +322,10 @@ static void le_setup(struct hci_request *req)
/* LE-only controllers have LE implicitly enabled */
if (!lmp_bredr_capable(hdev))
hci_dev_set_flag(hdev, HCI_LE_ENABLED);
+
+ /* Set PHY to 1M for TX and RX */
+ hci_dev_set_flag(hdev, HCI_LE_PHY_1M_TX);
+ hci_dev_set_flag(hdev, HCI_LE_PHY_1M_RX);
}
static void hci_setup_event_mask(struct hci_request *req)
--
2.7.4
next prev parent reply other threads:[~2018-04-24 13:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 13:50 [PATCH v2 00/18] Bluetooth: Extended Adv, Scan, Connection and PHY support Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 01/18] Bluetooth: Introduce helpers for LE set scan start and complete Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 02/18] Bluetooth: Use extended scanning if controller supports Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 03/18] Bluetooth: Process extended ADV report event Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 04/18] Bluetooth: Introduce helpers for le conn status and complete Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 05/18] Bluetooth: Use extended LE Connection if supported Jaganath Kanakkassery
2018-04-24 13:50 ` Jaganath Kanakkassery [this message]
2018-04-24 13:50 ` [PATCH v2 07/18] Bluetooth: Implement Get PHY Configuration mgmt command Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 08/18] Bluetooth: Implement Set PHY Confguration command Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 09/18] Bluetooth: Set Scan PHYs based on selected PHYs by user Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 10/18] Bluetooth: Handle extended ADV PDU types Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 11/18] Bluetooth: Use selected PHYs in extended connect Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 12/18] Bluetooth: Read no of adv sets during init Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 13/18] Bluetooth: Impmlement extended adv enable Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 14/18] Bluetooth: Use Set ext adv/scan rsp data if controller supports Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 15/18] Bluetooth: Implement disable and removal of adv instance Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 16/18] Bluetooth: Use ext adv for directed adv Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 17/18] Bluetooth: Implement Set ADV set random address Jaganath Kanakkassery
2018-04-24 13:50 ` [PATCH v2 18/18] Bluetooth: Implement secondary advertising on different PHYs Jaganath Kanakkassery
2018-06-06 5:51 ` [PATCH v2 00/18] Bluetooth: Extended Adv, Scan, Connection and PHY support Jaganath K
2018-06-19 9:55 ` Szymon Janc
2018-06-21 7:59 ` Jagan K
2018-06-21 9:46 ` Szymon Janc
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=1524577851-17238-7-git-send-email-jaganathx.kanakkassery@intel.com \
--to=jaganath.k.os@gmail.com \
--cc=jaganathx.kanakkassery@intel.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;
as well as URLs for NNTP newsgroup(s).