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;
MIME-Version: 1.0
References: <20200406180331.891822-1-marcel@holtmann.org> <CANFp7mXe3QtkKL8+TgTp=jwvpydABhDkiXks=3h4+op20rWhGQ@mail.gmail.com>
 <AC887BAA-95ED-456B-84D2-2D1EF6A8339F@holtmann.org> <CANFp7mU2+Z3f1ZqR8RCsOUu6Crc_xng12gcgn0YCwjzfH9Y-nQ@mail.gmail.com>
 <8FE42946-ED27-4F9F-8F30-2744D0AC2AB0@holtmann.org>
In-Reply-To: <8FE42946-ED27-4F9F-8F30-2744D0AC2AB0@holtmann.org>
From:   Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Date:   Wed, 10 Jun 2020 10:31:39 -0700
Message-ID: <CANFp7mUdL2eB8pWf1sfL_zC0zqTvc7QQuv8xR-pBSDds-Mg5Qw@mail.gmail.com>
Subject: Re: [PATCH] doc: Add commands and event for handling device flags
To:     Marcel Holtmann <marcel@holtmann.org>
Cc:     Bluez mailing list <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Thanks Marcel.

Do you want to handle the implementation in the kernel or shall I send
up a patch?

Abhishek

On Wed, Jun 10, 2020 at 10:23 AM Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Abhishek,
>
> > Coming back to this device flags idea, I think I would prefer the
> > original design over adding new management commands for each flag.
> > Bluez will just have to maintain the current flags and pending flags
> > (i.e. mgmt call) to decide when to emit property changed events for
> > the device WakeAllowed property.
> >
> > 0x0049 and 0x004A are now taken for experimental features but you have
> > my reviewed-by for the next available values for the original patch.
>
> I updated the patch and applied it.
>
> Regards
>
> Marcel
>