linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Panda, Bharat B" <bharat.b.panda@intel.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: RE: [PATCH] support fast advertising interval
Date: Mon, 1 Oct 2018 09:29:04 +0000	[thread overview]
Message-ID: <B42C2A3D4050B547BA40CAE18E023BE6461DBEA7@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <CABBYNZ+s9a1cKyH7T6J5+=60J7H6aoVt5K1_bx0aR+y0hh5pcw@mail.gmail.com>

Hi Marcel, Luiz,

> -----Original Message-----
> From: Luiz Augusto von Dentz [mailto:luiz.dentz@gmail.com]
> Sent: Thursday, September 27, 2018 4:47 PM
> To: Marcel Holtmann <marcel@holtmann.org>
> Cc: Panda, Bharat B <bharat.b.panda@intel.com>; linux-
> bluetooth@vger.kernel.org
> Subject: Re: [PATCH] support fast advertising interval
> 
> Hi Marcel, Bharat,
> 
> On Thu, Sep 27, 2018 at 1:57 PM, Marcel Holtmann <marcel@holtmann.org>
> wrote:
> > Hi Bharat,
> >
> >> Changes made to add support for fast advertising interval as per core
> >> 4.1 specification, section 9.3.11.2.
> >>
> >> A peripheral device enetering any of the following GAP modes and
> >> sending either non-connectable advertising events or scannable
> >> undirected advertising events should use adv_fast_interval2(100ms -
> >> 150ms) for adv_fast_period(30s).
> >>         - Non-Discoverable Mode
> >>         - Non-Connectable Mode
> >>         - Limited Discoverable Mode
> >>         - General Discoverable Mode
> >
> > can we also get a patch documenting this in mgmt-api.txt in bluez.git.
I will send a separate patch for same following v2 for current patch.
> >
> >>
> >> Signed-off-by: Bharat Bhusan Panda <bharat.b.panda@intel.com>
> >> ---
> >> include/net/bluetooth/hci_core.h |  2 ++
> >> net/bluetooth/hci_request.c      | 22 ++++++++++++++++++++++
> >> 2 files changed, 24 insertions(+)
> >>
> >> diff --git a/include/net/bluetooth/hci_core.h
> >> b/include/net/bluetooth/hci_core.h
> >> index b619a19..2fe908c 100644
> >> --- a/include/net/bluetooth/hci_core.h
> >> +++ b/include/net/bluetooth/hci_core.h
> >> @@ -1456,6 +1456,8 @@ struct hci_mgmt_chan {
> >> #define DISCOV_INTERLEAVED_INQUIRY_LEN        0x04
> >> #define DISCOV_BREDR_INQUIRY_LEN      0x08
> >> #define DISCOV_LE_RESTART_DELAY               msecs_to_jiffies(200)   /* msec
> */
> >> +#define DISCOV_LE_FAST_ADV_INT_MIN   100     /* msec */
> >> +#define DISCOV_LE_FAST_ADV_INT_MAX   150     /* msec */
> >>
> >> void mgmt_fill_version_info(void *ver); int mgmt_new_settings(struct
> >> hci_dev *hdev); diff --git a/net/bluetooth/hci_request.c
> >> b/net/bluetooth/hci_request.c index 66c0781..5cf3ef9 100644
> >> --- a/net/bluetooth/hci_request.c
> >> +++ b/net/bluetooth/hci_request.c
> >> @@ -1005,6 +1005,28 @@ void __hci_req_enable_advertising(struct
> hci_request *req)
> >>       else
> >>               cp.type = LE_ADV_NONCONN_IND;
> >>
> >> +     /* As per core 4.1 spec, section 9.3.11.2: A peripheral device
> >> +      * enetering any of the following GAP modes and sending either
> >
> > Fix the typo please.
> >
> >> +      * non-connectable advertising events or scannable undirected
> >> +      * advertising events should use adv_fast_interval2(100ms - 150ms)
> >> +      * for adv_fast_period(30s).
> >> +      *
> >> +      *      - Non-Discoverable Mode
> >> +      *      - Non-Connectable Mode
> >> +      *      - Limited Discoverable Mode
> >> +      *      - General Discoverable Mode
> >> +      */
> >> +     if ((cp.type == LE_ADV_NONCONN_IND) || (cp.type =
> >> + LE_ADV_SCAN_IND)) {
> >
> > This extra (x == y) parentheses are not needed.
> 
> Btw the second part of the expression seem wrong, it is assigning not
> comparing.
Yes, the assignment was always making the condition true. I have fixed the typo and retested the patch working.
Patch v2 will be followed with the fix.
> 
> >
> >> +             if ((hci_dev_test_flag(hdev, HCI_DISCOVERABLE)) ||
> >> +             (hci_dev_test_flag(hdev, HCI_LIMITED_DISCOVERABLE)) ||
> >> +             (hdev->discovery.limited == true)) {
> >
> > And this is wrongly aligned. In addition, you need a bit more comment text
> above explains on what are the conditions.
> >
> >> +                     cp.min_interval =
> >> +                             cpu_to_le16(DISCOV_LE_FAST_ADV_INT_MIN);
> >> +                     cp.max_interval =
> >> +                             cpu_to_le16(DISCOV_LE_FAST_ADV_INT_MAX);
> >> +             }
> >> +     }
> >> +
> >>       cp.own_address_type = own_addr_type;
> >>       cp.channel_map = hdev->le_adv_channel_map;
> >
> > Regards
> >
> > Marcel
> >
> 
> 
> 
> --
> Luiz Augusto von Dentz
Regards,
Bharat

  reply	other threads:[~2018-10-01  9:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27  8:46 [PATCH] support fast advertising interval Bharat Bhusan Panda
2018-09-27 10:57 ` Marcel Holtmann
2018-09-27 11:16   ` Luiz Augusto von Dentz
2018-10-01  9:29     ` Panda, Bharat B [this message]
2018-10-30  6:25       ` Panda, Bharat B
2018-10-30  7:55 ` 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=B42C2A3D4050B547BA40CAE18E023BE6461DBEA7@BGSMSX101.gar.corp.intel.com \
    --to=bharat.b.panda@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --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 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).