linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikel Astiz <mikel.astiz.oss@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: [RFC BlueZ v1 06/13] dbus: Add Device property to org.bluez.Service1
Date: Thu,  6 Jun 2013 10:21:38 +0200	[thread overview]
Message-ID: <1370506905-19641-7-git-send-email-mikel.astiz.oss@gmail.com> (raw)
In-Reply-To: <1370506905-19641-1-git-send-email-mikel.astiz.oss@gmail.com>

From: Mikel Astiz <mikel.astiz@bmw-carit.de>

Expose in D-Bus the object path of the device which the service belongs
to.
---
 src/service.c | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/src/service.c b/src/service.c
index 7b9e271..b5b0a8e 100644
--- a/src/service.c
+++ b/src/service.c
@@ -348,6 +348,22 @@ void btd_service_disconnecting_complete(struct btd_service *service, int err)
 		change_state(service, BTD_SERVICE_STATE_CONNECTED, err);
 }
 
+static gboolean service_get_device(const GDBusPropertyTable *property,
+					DBusMessageIter *iter, void *data)
+{
+	struct btd_service *service = data;
+	const char *path = device_get_path(service->device);
+
+	dbus_message_iter_append_basic(iter, DBUS_TYPE_OBJECT_PATH, &path);
+
+	return TRUE;
+}
+
+static const GDBusPropertyTable service_properties[] = {
+	{ "Device", "o", service_get_device },
+	{ }
+};
+
 static int service_register(struct btd_service *service, unsigned int id)
 {
 	DBusConnection *dbus_conn = btd_get_dbus_connection();
@@ -359,7 +375,7 @@ static int service_register(struct btd_service *service, unsigned int id)
 
 	if (g_dbus_register_interface(dbus_conn,
 					path, SERVICE_INTERFACE,
-					NULL, NULL, NULL, service,
+					NULL, NULL, service_properties, service,
 					NULL) == FALSE) {
 		g_free(path);
 		error("Unable to register service interface for %s",
-- 
1.8.1.4


  parent reply	other threads:[~2013-06-06  8:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  8:21 [RFC BlueZ v1 00/13] Add experimental org.bluez.Service1 Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 01/13] test: Remove obsolete test script Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 02/13] test: Add UUID alias table to bluezutils.py Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 03/13] test: Support human-friendly UUIDs in test-device Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 04/13] test: Show human-friendly UUIDs in list-devices Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 05/13] dbus: Add new org.bluez.Service1 Mikel Astiz
2013-06-06  8:29   ` Gustavo Padovan
2013-06-06  9:26     ` Mikel Astiz
2013-06-06  8:21 ` Mikel Astiz [this message]
2013-06-06  8:21 ` [RFC BlueZ v1 07/13] dbus: Add UUID property to org.bluez.Service1 Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 08/13] dbus: Add state " Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 09/13] dbus: Add Connect/Disconnect " Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 10/13] doc: Add API documentation for org.bluez.Service1 Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 11/13] dbus: Deprecate old profile-connecting API Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 12/13] test: Add test-service script Mikel Astiz
2013-06-06  8:21 ` [RFC BlueZ v1 13/13] test: Add --uuid to test-service Mikel Astiz

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=1370506905-19641-7-git-send-email-mikel.astiz.oss@gmail.com \
    --to=mikel.astiz.oss@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mikel.astiz@bmw-carit.de \
    /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).