Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp533795ybc; Sat, 16 Nov 2019 04:08:28 -0800 (PST) X-Google-Smtp-Source: APXvYqwQ6hHB4DRS6hdLv1tr6LKCBSaV9AGrI1duu8W1GxqUZDgsKyX1teFUZjcrL3eOV5Ow/iid X-Received: by 2002:a17:906:938d:: with SMTP id l13mr9426920ejx.74.1573906108154; Sat, 16 Nov 2019 04:08:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573906108; cv=none; d=google.com; s=arc-20160816; b=WLvH+DAh2GwvpMWgXe+zeE4xwdbTC3xMfGAKL8JRlwURATtrjhR4smYg4mB+FuV8/E 5N4pK/TasZ/YnqpmQjzSxXKnJ+7w7no+0b7QFSXiRXovcG2fkwk0lilxtchGYJfvWvkS RobKqj6cPWhNv4yeq7L4Ug3JwHn6ZYR/llKKkBizknRD3fYhZzKjXqPUHXmrUfvvt2Zn bSwb7+wCtj9vgNZ/HbQCsWcb6lUh5ubu2HepNvbirUCBpvmjVOhbUPc+EG72kycqc+TR h26VOz3QK6f03DBJj42uFODSw6ueHi/pSh7wyPTVDbnOtrnjG5M40rjtKu+m/+J0cyWr HVFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=eU5fWBaw/qG8v+T9a/1FEuKOJ9fIXJzS0SzvUTEROzY=; b=Ut5wxxx0QP5NX7DwOOXktaSgl522kx4FM9t8BJAVYuZmEnHM/8zR+NffOM7BqvF8vL kV9dsBDW2nk4Fh+ctjF3NY4PyMbmJBEHIYb6WJKGvJ63RWRvQriZq39XDmzXlZAubSK5 78tYOydrHTL2g65gZrmqaavZugYF+nM+p4WhP4X46ttGJJvK5N0ypaip1ZPaMqMVHkmg bcUMhql6jEbAYElJNDDbfY2gk7dHiXwkw65NCmAsOa7DDnHoE1dyEcBfiRJYt3PyTeGI jLQQzjU6OUANgkxmhB8BYsv4NuAzFkn3K/pXViPjTBHdu9AaZLPs6sJMuGmhvJVjxSkK PCZQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a28si9796019edc.5.2019.11.16.04.07.43; Sat, 16 Nov 2019 04:08:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727436AbfKPMFe (ORCPT + 99 others); Sat, 16 Nov 2019 07:05:34 -0500 Received: from hall.aurel32.net ([195.154.113.88]:52650 "EHLO hall.aurel32.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727331AbfKPMFe (ORCPT ); Sat, 16 Nov 2019 07:05:34 -0500 Received: from [2a01:e35:2fdd:a4e1:fe91:fc89:bc43:b814] (helo=ohm.rr44.fr) by hall.aurel32.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iVwpW-000186-Io; Sat, 16 Nov 2019 13:05:30 +0100 Received: from aurel32 by ohm.rr44.fr with local (Exim 4.92.3) (envelope-from ) id 1iVwpV-0001Lw-7N; Sat, 16 Nov 2019 13:05:29 +0100 Date: Sat, 16 Nov 2019 13:05:29 +0100 From: Aurelien Jarno To: "Stotland, Inga" Cc: "linux-bluetooth@vger.kernel.org" Subject: Re: [PATCH BlueZ] mesh: Fix io inititalization sequence Message-ID: <20191116120529.GB30589@aurel32.net> References: <20191114235210.3312-1-inga.stotland@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org 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