All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Liu <yudiliu@google.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC PATCH v1 1/1] adapter - D-Bus API for querying the adapter's capability
Date: Tue, 11 Aug 2020 11:22:21 -0700	[thread overview]
Message-ID: <CAHC-ybxKkrDzvtyj3ksyeh4zMuoCGeCOoRodLHi1ADLBYL1efQ@mail.gmail.com> (raw)
In-Reply-To: <20200803165804.RFC.v1.1.Ibaa1dfd49179a141c19a651f3c2132a28b71b344@changeid>

Friendly ping for comments, thanks.


On Mon, Aug 3, 2020 at 4:58 PM Yu Liu <yudiliu@google.com> wrote:
>
> From: Archie Pusaka <apusaka@chromium.org>
>
> Initially this is introduced to query whether WBS is supported by the adapter,
> the API is generic enough to be extended to support querying others in
> the future.
>
> Reviewed-by: sonnysasaka@chromium.org
>
> ---
>
> Changes in v1:
> - Initial change
>
>  doc/adapter-api.txt | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>
> diff --git a/doc/adapter-api.txt b/doc/adapter-api.txt
> index 1a7255750..250d0e9b3 100644
> --- a/doc/adapter-api.txt
> +++ b/doc/adapter-api.txt
> @@ -204,6 +204,23 @@ Methods            void StartDiscovery()
>                                          org.bluez.Error.NotReady
>                                          org.bluez.Error.Failed
>
> +               dict GetSupportedCapabilities()
> +
> +                       This method returns a dictionary of supported
> +                       capabilities that is populated when the adapter
> +                       initiated.
> +
> +                       The dictionary is following the format
> +                       {capability : value}, where:
> +
> +                       string capability:      The supported capability under
> +                                               discussion.
> +                       variant value:          A more detailed description of
> +                                               the capability.
> +
> +                       Possible errors: org.bluez.Error.NotReady
> +                                        org.bluez.Error.Failed
> +
>  Properties     string Address [readonly]
>
>                         The Bluetooth device address.
> --
> 2.28.0.163.g6104cc2f0b6-goog
>

  reply	other threads:[~2020-08-11 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 23:58 [RFC PATCH v1 0/1] A client needs to query whether the Bluetooth adapter support WBS, so we Yu Liu
2020-08-03 23:58 ` [RFC PATCH v1 1/1] adapter - D-Bus API for querying the adapter's capability Yu Liu
2020-08-11 18:22   ` Yu Liu [this message]
2020-08-12 12:13   ` Marcel Holtmann
2020-08-17 21:28     ` Yu Liu

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=CAHC-ybxKkrDzvtyj3ksyeh4zMuoCGeCOoRodLHi1ADLBYL1efQ@mail.gmail.com \
    --to=yudiliu@google.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 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.