From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Bluetooth: Add BT_PHY socket option
Date: Fri, 14 Feb 2020 08:52:44 +0100 [thread overview]
Message-ID: <4C035186-EB33-40B1-8A0D-227FBC2269BD@holtmann.org> (raw)
In-Reply-To: <CABBYNZ+MqBhjwCaU7UmezrT8nZ9h5WUZ4Fmrq+cXE_mQSy1E4g@mail.gmail.com>
Hi Luiz,
>>>> This adds BT_PHY socket option (read-only) which can be used to read
>>>> the PHYs in use by the underline connection.
>>>>
>>>> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>>>> ---
>>>> include/net/bluetooth/bluetooth.h | 17 ++++++
>>>> include/net/bluetooth/hci_core.h | 2 +
>>>> net/bluetooth/hci_conn.c | 88 +++++++++++++++++++++++++++++++
>>>> net/bluetooth/l2cap_sock.c | 13 +++++
>>>> net/bluetooth/sco.c | 13 +++++
>>>> 5 files changed, 133 insertions(+)
>>>>
>>>> diff --git a/include/net/bluetooth/bluetooth.h b/include/net/bluetooth/bluetooth.h
>>>> index e42bb8e03c09..1576353a2773 100644
>>>> --- a/include/net/bluetooth/bluetooth.h
>>>> +++ b/include/net/bluetooth/bluetooth.h
>>>> @@ -121,6 +121,23 @@ struct bt_voice {
>>>>
>>>> #define BT_SNDMTU 12
>>>> #define BT_RCVMTU 13
>>>> +#define BT_PHY 14
>>>> +
>>>> +#define BT_PHY_BR_1M_1SLOT 0x00000001
>>>> +#define BT_PHY_BR_1M_3SLOT 0x00000002
>>>> +#define BT_PHY_BR_1M_5SLOT 0x00000004
>>>> +#define BT_PHY_EDR_2M_1SLOT 0x00000008
>>>> +#define BT_PHY_EDR_2M_3SLOT 0x00000010
>>>> +#define BT_PHY_EDR_2M_5SLOT 0x00000020
>>>> +#define BT_PHY_EDR_3M_1SLOT 0x00000040
>>>> +#define BT_PHY_EDR_3M_3SLOT 0x00000080
>>>> +#define BT_PHY_EDR_3M_5SLOT 0x00000100
>>>> +#define BT_PHY_LE_1M_TX 0x00000200
>>>> +#define BT_PHY_LE_1M_RX 0x00000400
>>>> +#define BT_PHY_LE_2M_TX 0x00000800
>>>> +#define BT_PHY_LE_2M_RX 0x00001000
>>>> +#define BT_PHY_LE_CODED_TX 0x00002000
>>>> +#define BT_PHY_LE_CODED_RX 0x00004000
>>>>
>>>> __printf(1, 2)
>>>> void bt_info(const char *fmt, ...);
>>>> diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h
>>>> index 89ecf0a80aa1..dcc0dc6e2624 100644
>>>> --- a/include/net/bluetooth/hci_core.h
>>>> +++ b/include/net/bluetooth/hci_core.h
>>>> @@ -1477,6 +1477,8 @@ void *hci_sent_cmd_data(struct hci_dev *hdev, __u16 opcode);
>>>> struct sk_buff *hci_cmd_sync(struct hci_dev *hdev, u16 opcode, u32 plen,
>>>> const void *param, u32 timeout);
>>>>
>>>> +u32 hci_conn_get_phy(struct hci_conn *conn);
>>>> +
>>>> /* ----- HCI Sockets ----- */
>>>> void hci_send_to_sock(struct hci_dev *hdev, struct sk_buff *skb);
>>>> void hci_send_to_channel(unsigned short channel, struct sk_buff *skb,
>>>> diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c
>>>> index 87691404d0c6..9ff2611b272f 100644
>>>> --- a/net/bluetooth/hci_conn.c
>>>> +++ b/net/bluetooth/hci_conn.c
>>>> @@ -1725,3 +1725,91 @@ struct hci_chan *hci_chan_lookup_handle(struct hci_dev *hdev, __u16 handle)
>>>>
>>>> return hchan;
>>>> }
>>>> +
>>>> +u32 hci_conn_get_phy(struct hci_conn *conn)
>>>> +{
>>>> + u32 phys = 0;
>>>> +
>>>> + hci_dev_lock(conn->hdev);
>>>> +
>>>> + switch (conn->type) {
>>>> + case SCO_LINK:
>>>> + phys |= BT_PHY_BR_1M_1SLOT;
>>>> +
>>>> + break;
>>>
>>> something is missing here. The SCO links can also be 3 and 5 slots.
>>
>> I couldn't find any information regarding the slot for HV1, HV2, HV3
>> and DV so I assume they were all using 1 slot.
>
> It is actually 1 slot, see:
>
> BLUETOOTH CORE SPECIFICATION Version 5.2 | Vol 2, Part B
> page 471
> Table 6.2: Packets defined for synchronous, asynchronous, and CSB
> logical transport types
good call. I even managed to expunge that from my brain after 20 years of Bluetooth 1.1 spec ;)
Regards
Marcel
prev parent reply other threads:[~2020-02-14 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 19:00 [PATCH] Bluetooth: Add BT_PHY socket option Luiz Augusto von Dentz
2020-02-08 8:32 ` Marcel Holtmann
2020-02-10 21:13 ` Luiz Augusto von Dentz
2020-02-10 21:26 ` Luiz Augusto von Dentz
2020-02-14 7:52 ` Marcel Holtmann [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=4C035186-EB33-40B1-8A0D-227FBC2269BD@holtmann.org \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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;
as well as URLs for NNTP newsgroup(s).