All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ 0/1] mesh: Move HCI handling to mesh-io-generic
Date: Tue, 18 Jun 2019 20:04:19 +0000	[thread overview]
Message-ID: <F5913AD6-9050-422D-8BED-AB6CD2B434D3@intel.com> (raw)
In-Reply-To: <34B4A752-E039-4CAD-A8A7-E8CC137DC8A4@intel.com>

Hi Michał (again)

> On Jun 18, 2019, at 12:59 PM, Gix, Brian <brian.gix@intel.com> wrote:
> 
> Hi Michał,
> 
>> On Jun 18, 2019, at 4:27 AM, Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com> wrote:
>> 
>> This patch enables us to implement more I/O layers, particularly non-HCI
>> ones.
>> 
>> As of Bluetooth 5.1, standard HCI commands don't allow precise control
>> over mesh-related advertising, making this I/O layer very inefficient.
>> Therefore, it is desirable to have an option to use a non-HCI transport
>> to talk to radio transceiver, at least until Bluetooth extends HCI so
>> that standard BLE Controllers achieve good performance.
> 
> The intent if the architecture was to allow for finer control with future controllers, and thus a mesh-io.c which doesn’t assume anything about underlying controllers, and then an *initial* mesh-io-generic.c which is what gets used by 4.x controllers... as more controllers are supported with finer tuning available, then mesh-io-<bt5+>.c can be added to the abstracted list.

We are also talking about how to share controllers between bluetoothd and meshd...   one idea is using the MGMT interface to send and receive specific advertisements...   that would necessitate a mesh-io-mgmt.c. However, it will also require support in the kernel.


> 
>> 
>> Another use case would be a non-local radio: the mesh stack can run on a
>> secure device, but due to physical constraints it might need to use
>> radio transceiver located at a distance, connected e.g. via LAN.
>> 
>> Michał Lowas-Rzechonek (1):
>> mesh: Move HCI handling to mesh-io-generic
>> 
>> mesh/main.c            |   4 +-
>> mesh/mesh-io-api.h     |   3 +-
>> mesh/mesh-io-generic.c | 203 ++++++++++++++++++++++++++++++++++++-----
>> mesh/mesh-io.c         |  17 ++--
>> mesh/mesh-io.h         |   2 +-
>> mesh/mesh.c            | 189 +++-----------------------------------
>> mesh/mesh.h            |   4 +-
>> 7 files changed, 209 insertions(+), 213 deletions(-)
>> 
>> -- 
>> 2.19.1
>> 

  reply	other threads:[~2019-06-18 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 11:26 [PATCH BlueZ 0/1] mesh: Move HCI handling to mesh-io-generic Michał Lowas-Rzechonek
2019-06-18 11:26 ` [PATCH BlueZ 1/1] " Michał Lowas-Rzechonek
2019-06-20 18:02   ` Gix, Brian
2019-06-18 19:59 ` [PATCH BlueZ 0/1] " Gix, Brian
2019-06-18 20:04   ` Gix, Brian [this message]
2019-06-19  6:56     ` Michał Lowas-Rzechonek

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=F5913AD6-9050-422D-8BED-AB6CD2B434D3@intel.com \
    --to=brian.gix@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=michal.lowas-rzechonek@silvair.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.