From: Marcel Holtmann <marcel@holtmann.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 3/9 v3] Bluetooth: Keep track of UUID type upon addition
Date: Sat, 26 Jan 2013 18:07:46 +0100 [thread overview]
Message-ID: <1359220066.16748.14.camel@aeonflux> (raw)
In-Reply-To: <1359194924-3151-4-git-send-email-johan.hedberg@gmail.com>
Hi Johan,
> The primary purpose of the UUIDs is to eable generation of EIR and AD
assume this is suppose to read "enable".
> data. In these data formats the UUIDs are split into separate fields
> based on whether they're 16, 32 or 128 bit UUIDs. To make the generation
> of these data fields simpler this patch adds a type member to the
> bt_uuid struct and assigns a value to it as soon as the UUID is added to
> the kernel. This way the type doesn't need to be calculated each time
> the UUID list is later iterated.
>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
> include/net/bluetooth/hci_core.h | 5 ++++
> net/bluetooth/mgmt.c | 48 ++++++++++++++++++--------------------
> 2 files changed, 28 insertions(+), 25 deletions(-)
>
> diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h
> index bcf8ffe..6ed91ef 100644
> --- a/include/net/bluetooth/hci_core.h
> +++ b/include/net/bluetooth/hci_core.h
> @@ -83,9 +83,14 @@ struct bdaddr_list {
> bdaddr_t bdaddr;
> };
>
> +#define BT_UUID16 1
> +#define BT_UUID32 2
> +#define BT_UUID128 3
> +
I would have defined them as 16, 32 and 128. And not used constants at
all.
> struct bt_uuid {
> struct list_head list;
> u8 uuid[16];
> + u8 type;
And you could have used size instead of type here.
> u8 svc_hint;
> };
Not that I care much, but that is how I would have done it. I am open to
discuss this.
> diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c
> index 4fd45a3..d9f6b2c 100644
> --- a/net/bluetooth/mgmt.c
> +++ b/net/bluetooth/mgmt.c
> @@ -435,28 +435,6 @@ static u32 get_current_settings(struct hci_dev *hdev)
>
> #define PNP_INFO_SVCLASS_ID 0x1200
>
> -static u8 bluetooth_base_uuid[] = {
> - 0xFB, 0x34, 0x9B, 0x5F, 0x80, 0x00, 0x00, 0x80,
> - 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> -};
> -
> -static u16 get_uuid16(u8 *uuid128)
> -{
> - u32 val;
> - int i;
> -
> - for (i = 0; i < 12; i++) {
> - if (bluetooth_base_uuid[i] != uuid128[i])
> - return 0;
> - }
> -
> - val = get_unaligned_le32(&uuid128[12]);
> - if (val > 0xffff)
> - return 0;
> -
> - return (u16) val;
> -}
> -
> static void create_eir(struct hci_dev *hdev, u8 *data)
> {
> u8 *ptr = data;
> @@ -513,10 +491,10 @@ static void create_eir(struct hci_dev *hdev, u8 *data)
> list_for_each_entry(uuid, &hdev->uuids, list) {
> u16 uuid16;
>
> - uuid16 = get_uuid16(uuid->uuid);
> - if (uuid16 == 0)
> - return;
> + if (uuid->type != BT_UUID16)
> + continue;
>
> + uuid16 = get_unaligned_le16(&uuid->uuid[12]);
> if (uuid16 < 0x1100)
> continue;
>
> @@ -1304,6 +1282,25 @@ unlock:
> return err;
> }
>
> +static u8 bluetooth_base_uuid[] = {
> + 0xfb, 0x34, 0x9b, 0x5f, 0x80, 0x00, 0x00, 0x80,
> + 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> +};
> +
Make this one const.
> +static u8 bt_uuid_type(u8 *uuid)
> +{
Any reason the parameter can not be const here.
> + u32 val;
> +
> + if (memcmp(uuid, bluetooth_base_uuid, 12))
> + return BT_UUID128;
> +
> + val = get_unaligned_le32(&uuid[12]);
> + if (val > 0xffff)
> + return BT_UUID32;
> +
> + return BT_UUID16;
> +}
> +
And then called this get_uuid_size or something similar.
> static int add_uuid(struct sock *sk, struct hci_dev *hdev, void *data, u16 len)
> {
> struct mgmt_cp_add_uuid *cp = data;
> @@ -1329,6 +1326,7 @@ static int add_uuid(struct sock *sk, struct hci_dev *hdev, void *data, u16 len)
>
> memcpy(uuid->uuid, cp->uuid, 16);
> uuid->svc_hint = cp->svc_hint;
> + uuid->type = bt_uuid_type(cp->uuid);
>
> list_add_tail(&uuid->list, &hdev->uuids);
>
Regards
Marcel
next prev parent reply other threads:[~2013-01-26 17:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 10:08 [PATCH 0/9 v3] Bluetooth: Add 32 and 128 bit EIR UUID support Johan Hedberg
2013-01-26 10:08 ` [PATCH 1/9 v3] Bluetooth: Store UUIDs in the same order that they were added Johan Hedberg
2013-01-26 17:03 ` Marcel Holtmann
2013-01-26 10:08 ` [PATCH 2/9 v3] Bluetooth: Simplify UUIDs clearing code Johan Hedberg
2013-01-26 17:03 ` Marcel Holtmann
2013-01-26 10:08 ` [PATCH 3/9 v3] Bluetooth: Keep track of UUID type upon addition Johan Hedberg
2013-01-26 17:07 ` Marcel Holtmann [this message]
2013-01-26 10:08 ` [PATCH 4/9 v3] Bluetooth: Simplify UUID removal code Johan Hedberg
2013-01-26 17:09 ` Marcel Holtmann
2013-01-26 10:08 ` [PATCH 5/9 v3] Bluetooth: Simplify UUID16 list generation for EIR Johan Hedberg
2013-01-26 17:11 ` Marcel Holtmann
2013-01-26 10:08 ` [PATCH 6/9 v3] Bluetooth: Remove useless eir_len variable from EIR creation Johan Hedberg
2013-01-26 17:12 ` Marcel Holtmann
2013-01-26 10:08 ` [PATCH 7/9 v3] Bluetooth: Refactor UUID-16 list generation into its own function Johan Hedberg
2013-01-26 17:13 ` Marcel Holtmann
2013-01-26 10:08 ` [PATCH 8/9 v3] Bluetooth: Add support for 32-bit UUIDs in EIR data Johan Hedberg
2013-01-26 17:14 ` Marcel Holtmann
2013-01-26 10:08 ` [PATCH 9/9 v3] Bluetooth: Add support for 128-bit " Johan Hedberg
2013-01-26 17:15 ` 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=1359220066.16748.14.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=johan.hedberg@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