All of lore.kernel.org
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@codecoup.pl>
To: linux-bluetooth@vger.kernel.org, Alain Michaud <alainm@chromium.org>
Cc: Alain Michaud <alainm@chromium.org>
Subject: Re: [BlueZ PATCH v3] doc:Adding Roles property
Date: Thu, 23 Apr 2020 16:42:09 +0200	[thread overview]
Message-ID: <5347568.DvuYhMxLoT@ix> (raw)
In-Reply-To: <20200423142305.66778-1-alainm@chromium.org>

Hi,

On Thursday, 23 April 2020 16:23:05 CEST Alain Michaud wrote:
> This change adds a new property to indicate the support for concurrent
> roles which means that the controller has reported the appropriate
> LE_Supported_States (hdev->le_states) and that the controller's driver
> has reported correctly handling the various reported states.
> ---
> 
>  doc/adapter-api.txt | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/doc/adapter-api.txt b/doc/adapter-api.txt
> index acae032d9..1a7255750 100644
> --- a/doc/adapter-api.txt
> +++ b/doc/adapter-api.txt
> @@ -326,3 +326,11 @@ Properties	string Address [readonly]
> 
>  			Local Device ID information in modalias format
>  			used by the kernel and udev.
> +
> +		array{string} Roles [readonly]
> +
> +			List of supported roles. Possible values:
> +				"central": Supports the central role.
> +				"peripheral": Supports the peripheral 
role.
> +				"central-peripheral": Supports both 
roles
> +						      
concurrently.

If this is an array os strings why central-peripheral is needed?

-- 
pozdrawiam
Szymon Janc



  reply	other threads:[~2020-04-23 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 14:23 [BlueZ PATCH v3] doc:Adding Roles property Alain Michaud
2020-04-23 14:42 ` Szymon Janc [this message]
2020-04-23 14:51   ` Alain Michaud
2020-04-27 14:57     ` Alain Michaud
2020-04-27 16:47       ` Luiz Augusto von Dentz

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=5347568.DvuYhMxLoT@ix \
    --to=szymon.janc@codecoup.pl \
    --cc=alainm@chromium.org \
    --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 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.