From: "Arthur Crepin-Leblond" <arthur@marmottus.net>
To: "Bastien Nocera" <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/1] Expose the disconnect reason over D-Bus
Date: Mon, 12 Dec 2022 16:36:42 +0100 [thread overview]
Message-ID: <7dc4-63974a80-14d-24592140@246924754> (raw)
In-Reply-To: <988dc1f9add28a70ba18ce2f3042aac0bea04b5b.camel@hadess.net>
On Monday, December 12, 2022 15:49 CET, Bastien Nocera <hadess@hadess.net> wrote:
> On Mon, 2022-12-12 at 14:32 +0100, Arthur Crepin-Leblond wrote:
> > Hello,
> >
> > I am trying to expose the device disconnect reason over D-Bus and the
> > most elegant way I found was to subscribe to the adapter notify
> > callback that gives the reason as an argument.
>
> Any reason why this can't be a signal with the reason as an argument?
I chose the easy path by copying the existing code for the device properties
that get updated like the "Connected" or "ServicesResolved".
I am not too familiar with BlueZ signals other than PropertiesChanged,
InterfacesRemoved/Added. What would you have in mind?
And apologies in advance, it's my first time submitting here, I do not have
an advanced knowledge of the BlueZ internals.
next prev parent reply other threads:[~2022-12-12 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 13:32 [PATCH BlueZ 0/1] Expose the disconnect reason over D-Bus Arthur Crepin-Leblond
2022-12-12 13:32 ` [PATCH BlueZ 1/1] device: " Arthur Crepin-Leblond
2022-12-12 14:41 ` bluez.test.bot
2022-12-12 14:49 ` [PATCH BlueZ 0/1] " Bastien Nocera
2022-12-12 15:36 ` Arthur Crepin-Leblond [this message]
2022-12-13 20:45 ` Luiz Augusto von Dentz
2022-12-20 12:30 ` Arthur Crepin-Leblond
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=7dc4-63974a80-14d-24592140@246924754 \
--to=arthur@marmottus.net \
--cc=hadess@hadess.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox