From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] c0fb6c: client: Add command wake
Date: Wed, 18 Dec 2024 06:40:13 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/c2caa2-dfb1ff@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: c0fb6c067e48e1c867d2447a275253bea4d7ec40
https://github.com/bluez/bluez/commit/c0fb6c067e48e1c867d2447a275253bea4d7ec40
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-12-17 (Tue, 17 Dec 2024)
Changed paths:
M client/main.c
Log Message:
-----------
client: Add command wake
This adds command wake which can be used to set WakeAllowed property:
[bluetoothctl]> wake XX:XX:XX:XX:XX:XX off
[bluetoothctl]> Changing wake off succeeded
[bluetoothctl]> [CHG] Device XX:XX:XX:XX:XX:XX WakeAllowed: no
[bluetoothctl]> wake XX:XX:XX:XX:XX:XX on
[bluetoothctl]> Changing wake on succeeded
[bluetoothctl]> [CHG] Device XX:XX:XX:XX:XX:XX WakeAllowed: yes
[bluetoothctl]> wake XX:XX:XX:XX:XX:XX
Commit: dfb1ffdc95a00bc06d81a75c11ab5ad2e24d37bf
https://github.com/bluez/bluez/commit/dfb1ffdc95a00bc06d81a75c11ab5ad2e24d37bf
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-12-17 (Tue, 17 Dec 2024)
Changed paths:
M src/device.c
Log Message:
-----------
device: Fix not being able to set WakeAllowed
Setting WakeAllowed was not working as intended since
device_set_wake_override was changing the current_flags which
btd_device_flags_changed checks to determine if flags has been changed
to only then call device_set_wake_allowed_complete.
Fixes: https://github.com/bluez/bluez/issues/1045
Compare: https://github.com/bluez/bluez/compare/c2caa26a4d62...dfb1ffdc95a0
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2024-12-18 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/c2caa2-dfb1ff@github.com \
--to=noreply@github.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.