Linux bluetooth development
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: "Stotland, Inga" <inga.stotland@intel.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ] mesh: Fix io inititalization sequence
Date: Sat, 16 Nov 2019 13:05:29 +0100	[thread overview]
Message-ID: <20191116120529.GB30589@aurel32.net> (raw)
In-Reply-To: <fa582ab72a01b588db65fa840109c82bb4870596.camel@intel.com>

On 2019-11-15 23:23, Gix, Brian wrote:
> Applied, Thanks
> 
> On Thu, 2019-11-14 at 15:52 -0800, Inga Stotland wrote:
> > This introduces a chain of callbacks to indicate whether mesh io
> > is initialized and mesh network is ready to use.
> > 
> > This fixes the reported situation when the receive callbacks
> > were setup before the HCI was fully initialized. In other words,
> > BT_HCI_CMD_LE_SET_SCAN_PARAMETERS was called before BT_HCI_CMD_RESET
> > and, as the result, the callback issueing BT_HCI_CMD_LE_SET_SCAN_ENABLE
> > command was not called.
> > ---
> >  mesh/main.c            | 42 ++++++++++++++++++++++++------------
> >  mesh/mesh-io-api.h     |  3 ++-
> >  mesh/mesh-io-generic.c | 48 +++++++++++++++++++++++++++++++-----------
> >  mesh/mesh-io.c         |  5 +++--
> >  mesh/mesh-io.h         |  6 +++++-
> >  mesh/mesh.c            | 33 ++++++++++++++++++++++++-----
> >  mesh/mesh.h            |  5 ++++-
> >  7 files changed, 107 insertions(+), 35 deletions(-)

I have just tried this patch, and I confirm it fixes the RX issue after
restarting the bluetooth-meshd daemon. Thanks!

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

      reply	other threads:[~2019-11-16 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191114235210.3312-1-inga.stotland@intel.com>
2019-11-15 23:23 ` [PATCH BlueZ] mesh: Fix io inititalization sequence Gix, Brian
2019-11-16 12:05   ` Aurelien Jarno [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=20191116120529.GB30589@aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=inga.stotland@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