Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Isak Westin <karl.westin@loytec.com>
To:     "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Mesh: Possibility to combine functionality of bluetooth daemon and
 bluetooth-mesh daemon
Thread-Topic: Mesh: Possibility to combine functionality of bluetooth daemon
 and bluetooth-mesh daemon
Thread-Index: AddSRA+l/nJ10uo2QpybqLxzHaKHBQ==
Date:   Wed, 26 May 2021 15:30:53 +0000
Message-ID: <GV0P278MB012962632005A4784A9F243995249@GV0P278MB0129.CHEP278.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 351bc557-5f57-4ee5-6b9c-08d9205b4007
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 May 2021 15:30:53.6871
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 19f25823-17ff-421f-ad4e-8fed035aedda
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: quj7eO76wKbto3Lm3Vw5Kh8GDdwvBGnKQTvNdaK4rAV/4AM+3ud0jUr5KSKPYtl5uOXcObueNb+vT/rPjF4ACQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: GVAP278MB0182
X-OriginatorOrg: loytec.com
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.1960-8.6.0.1013-26182.000
X-TM-AS-Result: No-1.401-7.0-31-10
X-imss-scan-details: No-1.401-7.0-31-10
X-TMASE-Version: IMSVA-9.1.0.1960-8.6.1013-26182.000
X-TMASE-Result: 10-1.400800-10.000000
X-TMASE-MatchedRID: tW3636Wvo7Zfv1zVItekLKzHDCtzZvHZuSNyZKeaiD7WXfwzppZ8SCA9
        jDSyvwu9CIaa5JvsIzDTUef4xpw62ln5PmrlcMwbiZH+akICId3348e2CE/wYuDujCQCy7oGtY4
        N1nU8OYTXk0G1wmGFdeYWAQZj3Gas/uMEpT79T/PBXUwxE0W1ZkF+QlYpjQppmR36SjdWDGX/R1
        RTJsCnKTz75yF2//lYZJHjlDH+IiXT1VVKbhb4L5eZUDMyphfS57qwfXv3cNueEPi9wVyFrp99h
        kt3h4dXmy1pYYi7ZRKm5k33+uPKy8hIjxFAr+0zf8dNT84FpMZdWM3xsKqukXepM/I+teqco8WM
        kQWv6iXGlDvsLUDW2o6HM5rqDwqt7UJHB/uWWyslYe6EsigwgjVUBfsyfMNT24sihSR9H4c88v/
        oZOAxKUMlgVr7/jiUQQfCy4xXIw6kceLnztUEXr60BX13m3TqLr3kj3gYm08HH3J2uF6L8XQWaI
        bnjyDJVkIsYwVz6UifuqKKGgitHJRMZUCEHkRt
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Precedence: bulk
List-ID: <linux-bluetooth.vger.kernel.org>
X-Mailing-List: linux-bluetooth@vger.kernel.org

Hi linux-bluetooth developers,

I hope my question is not unsuitable for this mailing list.

I have read in the archives of this mailing list that the Bluetooth mesh da=
emon needs exclusive access to a Bluetooth controller.
If I understand that correctly (just to be clear), it means that when I onl=
y have one controller, I have to choose between either using mesh operation=
s or "normal" Bluetooth operations (normal here meaning all operations that=
 the regular Bluetooth daemon already performs).

In my company we are now developing a Bluetooth mesh lighting solution by u=
sing the Bluetooth-mesh daemon in an embedded Linux environment (with only =
one Bluetooth controller attached via HCI). We have a custom mesh applicati=
on that is using the mesh DBUS api to perform mesh operations. I am current=
ly looking in to how we can additionally allow this application to perform =
other Bluetooth operations (i.e. acting as an observer, and in the future a=
lso as a central device).

When you have time, I would be interested to hear your general thoughts abo=
ut this topic. Whether or not you believe it is doable or if it perhaps alr=
eady is a part of a long-term plan.
I am also in general open to help contributing to the project.

Thank you for your time,
Isak