From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
Erik Schilling <erik.schilling@linaro.org>,
Phil Howard <phil@gadgetoid.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Dan Carpenter <dan.carpenter@linaro.org>
Cc: "As advised by Dan Carpenter - I'm CC'ing
dbus"@lists.freedesktop.orgto, linux-gpio@vger.kernel.org,
dbus@lists.freedesktop.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH libgpiod v2 18/18] TODO: drop the DBus daemon from the list
Date: Fri, 28 Jun 2024 16:53:34 +0200 [thread overview]
Message-ID: <20240628-dbus-v2-18-e42336efe2d3@linaro.org> (raw)
In-Reply-To: <20240628-dbus-v2-0-e42336efe2d3@linaro.org>
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
We now have a full DBus API implementation. Drop this item from the list.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
TODO | 17 -----------------
1 file changed, 17 deletions(-)
diff --git a/TODO b/TODO
index 79a6246..5092f3f 100644
--- a/TODO
+++ b/TODO
@@ -11,23 +11,6 @@ serve as the starting point.
==========
-* implement dbus API for controlling GPIOs
-
-A common complaint from users about gpioset is that the state of a line is not
-retained once the program exits. While this is precisely the way linux
-character devices work, it's understandable that most users will want some
-centralized way of controlling GPIOs - similar to how sysfs worked.
-
-One of the possible solutions is a DBus API. We need a daemon exposing chips
-and lines as dbus objects and allowing to control and inspect lines using
-dbus methods and monitor them using signals.
-
-As of writing of this document some of the work has already been done and the
-skeleton of the dbus daemon written in C using GLib has already been developed
-and is partially functional.
-
-----------
-
* implement a simple daemon for controlling GPIOs in C together with a client
program
--
2.43.0
prev parent reply other threads:[~2024-06-28 14:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 14:53 [PATCH libgpiod v2 00/18] dbus: add GLib-based DBus daemon and command-line client Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 01/18] tests: split out reusable test code into a local static library Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 02/18] tests: split out the common test code for bash scripts Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 03/18] bindings: glib: add build files Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 04/18] bindings: glib: add public headers Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 05/18] bindings: glib: add core code Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 06/18] bindings: glib: add examples Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 07/18] bindings: glib: add tests Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 08/18] README: document GLib bindings Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 09/18] dbus: add build files Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 10/18] dbus: add the API definitions Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 11/18] dbus: add a wrapper around the gdbus-codegen generated header Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 12/18] dbus: add data files Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 13/18] dbus: add gpio-manager code Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 14/18] dbus: add tests Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 15/18] dbus: add a command-line client Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 16/18] dbus: client: add tests Bartosz Golaszewski
2024-06-28 14:53 ` [PATCH libgpiod v2 17/18] README: document the DBus API Bartosz Golaszewski
2024-06-28 14:53 ` Bartosz Golaszewski [this message]
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=20240628-dbus-v2-18-e42336efe2d3@linaro.org \
--to=brgl@bgdev.pl \
--cc="As advised by Dan Carpenter - I'm CC'ing dbus"@lists.freedesktop.orgto \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=dbus@lists.freedesktop.org \
--cc=erik.schilling@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=phil@gadgetoid.com \
--cc=viresh.kumar@linaro.org \
--cc=warthog618@gmail.com \
/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).