From: Sonny Sasaka <sonnysasaka@chromium.org>
To: linux-bluetooth@vger.kernel.org
Cc: Sonny Sasaka <sonnysasaka@chromium.org>
Subject: [PATCH] build: Add option to disable battery profile
Date: Fri, 1 May 2020 14:53:52 -0700 [thread overview]
Message-ID: <20200501215352.23858-1-sonnysasaka@chromium.org> (raw)
Some clients may want to handle battery profile through the generic GATT
interface rather than BlueZ's internal Battery interface.
---
Makefile.plugins | 2 ++
configure.ac | 4 ++++
2 files changed, 6 insertions(+)
diff --git a/Makefile.plugins b/Makefile.plugins
index 98eee9ec8..b9733d31c 100644
--- a/Makefile.plugins
+++ b/Makefile.plugins
@@ -101,8 +101,10 @@ builtin_cppflags += $(ALSA_CFLAGS)
builtin_ldadd += $(ALSA_LIBS)
endif
+if BATTERY
builtin_modules += battery
builtin_sources += profiles/battery/battery.c
+endif
if SIXAXIS
plugin_LTLIBRARIES += plugins/sixaxis.la
diff --git a/configure.ac b/configure.ac
index 1433ace4a..d4fa862b5 100644
--- a/configure.ac
+++ b/configure.ac
@@ -181,6 +181,10 @@ AC_ARG_ENABLE(hog, AC_HELP_STRING([--disable-hog],
[disable HoG profile]), [enable_hog=${enableval}])
AM_CONDITIONAL(HOG, test "${enable_hog}" != "no")
+AC_ARG_ENABLE(battery, AC_HELP_STRING([--disable-battery],
+ [disable battery profile]), [enable_battery=${enableval}])
+AM_CONDITIONAL(BATTERY, test "${enable_battery}" != "no")
+
AC_ARG_ENABLE(health, AC_HELP_STRING([--enable-health],
[enable health profiles]), [enable_health=${enableval}])
AM_CONDITIONAL(HEALTH, test "${enable_health}" = "yes")
--
2.17.1
next reply other threads:[~2020-05-01 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 21:53 Sonny Sasaka [this message]
2020-05-06 11:24 ` [PATCH] build: Add option to disable battery profile Marcel Holtmann
2020-05-06 14:01 ` Alain Michaud
2020-05-06 14:08 ` Bastien Nocera
2020-05-06 16:35 ` Luiz Augusto von Dentz
2020-05-06 16:44 ` Marcel Holtmann
2020-05-06 16:44 ` Luiz Augusto von Dentz
2020-05-06 17:18 ` Sonny Sasaka
2020-05-13 7:50 ` Marcel Holtmann
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=20200501215352.23858-1-sonnysasaka@chromium.org \
--to=sonnysasaka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).