From: Vincent Fazio <vfazio@gmail.com>
To: linux-gpio@vger.kernel.org
Cc: vfazio@xes-inc.com, Vincent Fazio <vfazio@gmail.com>
Subject: [libgpiod][PATCH 0/9] bindings: python: improve line requests and reconfiguration
Date: Thu, 9 Oct 2025 08:05:06 -0500 [thread overview]
Message-ID: <20251009130516.3729433-1-vfazio@gmail.com> (raw)
This series makes a number of minor improvements to consistency, speed,
and code clarity for line requests and reconfiguration.
Patch 1 makes iterating through a configuration object consistent across
line requests and reconfiguration and helps condense code, making it a
bit more readable.
Patch 2 removes an unused attribute from LineRequest.
Patches 3-5 are minor cleanups to simplify and speed up line requests.
Patch 6 makes the behavior of reconfiguring an unrequested line name
consistent with that of an unrequested offset.
Patches 7-8 make lines requested by offset reconfigurable via line name
making them consistent with lines requested by name being reconfigurable
via offset.
Patch 9 updates line reconfiguration to warn the caller if a line was
included that was not part of the original line request.
Vincent Fazio (9):
bindings: python: make config iteration consistent
bindings: python: remove unused attribute from LineRequest
bindings: python: chip: track requested lines when enumerating
bindings: python: chip: simplify duplicate checking
bindings: python: chip: check mapped_output_values membership once
bindings: python: line_request: ignore invalid line names in
reconfigure_lines
bindings: python: ext: add ability to query line name
bindings: python: chip: map names for lines requested by offset
bindings: python: line_request: warn on unknown lines when
reconfiguring
bindings/python/gpiod/_ext.pyi | 1 +
bindings/python/gpiod/_internal.py | 22 +++++-
bindings/python/gpiod/chip.py | 84 ++++++++-------------
bindings/python/gpiod/ext/chip.c | 31 ++++++++
bindings/python/gpiod/line_request.py | 36 +++++----
bindings/python/tests/tests_line_request.py | 63 ++++++++++++++--
6 files changed, 163 insertions(+), 74 deletions(-)
--
2.43.0
next reply other threads:[~2025-10-09 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 13:05 Vincent Fazio [this message]
2025-10-09 13:05 ` [libgpiod][PATCH 1/9] bindings: python: make config iteration consistent Vincent Fazio
2025-10-09 13:05 ` [libgpiod][PATCH 2/9] bindings: python: remove unused attribute from LineRequest Vincent Fazio
2025-10-09 13:05 ` [libgpiod][PATCH 3/9] bindings: python: chip: track requested lines when enumerating Vincent Fazio
2025-10-09 13:05 ` [libgpiod][PATCH 4/9] bindings: python: chip: simplify duplicate checking Vincent Fazio
2025-10-09 13:05 ` [libgpiod][PATCH 5/9] bindings: python: chip: check mapped_output_values membership once Vincent Fazio
2025-10-09 13:05 ` [libgpiod][PATCH 6/9] bindings: python: line_request: ignore invalid line names in reconfigure_lines Vincent Fazio
2025-10-09 13:05 ` [libgpiod][PATCH 7/9] bindings: python: ext: add ability to query line name Vincent Fazio
2025-10-09 13:05 ` [libgpiod][PATCH 8/9] bindings: python: chip: map names for lines requested by offset Vincent Fazio
2025-10-09 13:05 ` [libgpiod][PATCH 9/9] bindings: python: line_request: warn on unknown lines when reconfiguring Vincent Fazio
2025-10-13 15:31 ` [libgpiod][PATCH 0/9] bindings: python: improve line requests and reconfiguration Bartosz Golaszewski
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=20251009130516.3729433-1-vfazio@gmail.com \
--to=vfazio@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=vfazio@xes-inc.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).