linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-gpio@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH 0/5] core: provide information about the parent chip in line requests
Date: Thu, 20 Jul 2023 11:27:36 +0800	[thread overview]
Message-ID: <ZLipqIJE1Mo4oK00@sol> (raw)
In-Reply-To: <20230719192057.172560-1-brgl@bgdev.pl>

On Wed, Jul 19, 2023 at 09:20:52PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> 
> While working on the DBus API, it occurred to me that while we can obtain
> the list of requested offsets from a line request, this information lacks
> context if we cannot get any information about the parent chip on which
> the request was made.
> 
> We cannot reference the chip in any way as its lifetime is disconnected
> from the request but we can at least provide the path to the character
> device used to open it as a way of providing some context for the offsets.
> 

No problem with this conceptually, the only question I have is which
one of these should be stored:
 - requested path e.g. 'a_symlink_to_my_favorite_chip'
 - canonicalised path e.g. '/dev/gpiochip0'
 - chip name e.g. 'gpiochip0'
 - chip number e.g. 0

In this patch we get the requested path, right?

Cheers,
Kent.

> This series adds a new getter for struct gpiod_line_request and wrappers
> for it for all bindings. This will be used in the upcoming DBus GPIO
> manager code.
> 
> Bartosz Golaszewski (5):
>   core: provide gpiod_line_request_get_chip_path()
>   tests: add a test-case for gpiod_line_request_get_chip_path()
>   bindings: cxx: provide line_request::chip_path()
>   bindings: python: provide the chip_path property in line_request
>   bindings: rust: provide LineRequest::chip_path()
> 
>  bindings/cxx/gpiodcxx/line-request.hpp       |  7 +++++++
>  bindings/cxx/line-request.cpp                | 10 +++++++++-
>  bindings/cxx/tests/tests-line-request.cpp    |  6 ++++--
>  bindings/python/gpiod/chip.py                |  1 +
>  bindings/python/gpiod/line_request.py        | 12 +++++++++--
>  bindings/python/tests/tests_line_request.py  | 13 +++++++-----
>  bindings/rust/libgpiod/src/line_request.rs   | 12 +++++++++++
>  bindings/rust/libgpiod/tests/line_request.rs | 13 ++++++++++++
>  include/gpiod.h                              |  9 +++++++++
>  lib/chip.c                                   |  2 +-
>  lib/internal.h                               |  3 ++-
>  lib/line-request.c                           | 20 ++++++++++++++++++-
>  tests/tests-line-request.c                   | 21 ++++++++++++++++++++
>  13 files changed, 116 insertions(+), 13 deletions(-)
> 
> -- 
> 2.39.2
> 

  parent reply	other threads:[~2023-07-20  3:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 19:20 [libgpiod][PATCH 0/5] core: provide information about the parent chip in line requests Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 1/5] core: provide gpiod_line_request_get_chip_path() Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 2/5] tests: add a test-case for gpiod_line_request_get_chip_path() Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 3/5] bindings: cxx: provide line_request::chip_path() Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 4/5] bindings: python: provide the chip_path property in line_request Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 5/5] bindings: rust: provide LineRequest::chip_path() Bartosz Golaszewski
2023-07-20  5:04   ` Erik Schilling
2023-07-20  8:04     ` Bartosz Golaszewski
2023-07-20  8:10       ` Erik Schilling
2023-07-20  3:27 ` Kent Gibson [this message]
2023-07-20  7:59   ` [libgpiod][PATCH 0/5] core: provide information about the parent chip in line requests Bartosz Golaszewski
2023-07-20  8:05     ` Kent Gibson
2023-07-20  8:25       ` Bartosz Golaszewski
2023-07-20  8:39         ` Kent Gibson
2023-07-20  8:49           ` Bartosz Golaszewski
2023-07-20  9:16             ` Kent Gibson
2023-07-20  9:38               ` Bartosz Golaszewski
2023-07-20  9:52                 ` Kent Gibson
2023-07-20 12:30                   ` Bartosz Golaszewski
2023-07-20 13:37                     ` Kent Gibson
2023-07-20 15:01                       ` Bartosz Golaszewski
2023-07-21  1:37                         ` Kent Gibson
2023-07-20  8:42     ` Andy Shevchenko

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=ZLipqIJE1Mo4oK00@sol \
    --to=warthog618@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=viresh.kumar@linaro.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).