From: Tom Rini <trini@konsulko.com>
To: Rasmus Villemoes <ravi@prevas.dk>
Cc: u-boot@lists.denx.de, Heinrich Schuchardt <xypron.glpk@gmx.de>,
Heiko Schocher <hs@denx.de>, Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v3 0/3] reenable dm_gpio tests, add support for gpio-line-names lookup
Date: Wed, 5 Nov 2025 09:20:18 -0600 [thread overview]
Message-ID: <20251105152018.GO6688@bill-the-cat> (raw)
In-Reply-To: <20251104174458.3385564-1-ravi@prevas.dk>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
On Tue, Nov 04, 2025 at 06:44:55PM +0100, Rasmus Villemoes wrote:
> Hopefully third time's the charm.
>
> I merely wanted to add support (mostly for use by the 'gpio' shell
> command) for looking up a gpio via the gpio-line-names DT property. We
> already have a "gpio_request_by_line_name()", but cmd/gpio.c does a
> separate "lookup + request", so it felt more natural to teach the
> lookup machinery this as well. That ran into
> OF_CONTROL-but-not-OF_LIBFDT being a thing for SPL, so here's yet
> another attempt.
>
> Now, when trying to do my civic duty and add tests for this, I found
> that test/dm/gpio.c has been defunct for a couple of years, and
> reinstating it is not entirely trivial.
>
> After a couple of rounds CI is now happy with this:
> https://github.com/u-boot/u-boot/pull/828
>
> Rasmus Villemoes (3):
> test: gpio: include in build, and fixup bitrot
> gpio: search gpio-line-names property in dm_gpio_lookup_name
> test: gpio: add test for gpio-line-names lookup
>
> arch/sandbox/dts/test.dts | 2 ++
> drivers/gpio/Kconfig | 16 ++++++++++++++++
> drivers/gpio/gpio-uclass.c | 11 ++++++++++-
> test/dm/Makefile | 2 +-
> test/dm/gpio.c | 24 +++++++++++++++++++-----
> 5 files changed, 48 insertions(+), 7 deletions(-)
Thanks for doing your "civic duty" and fixing these up!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-05 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 17:44 [PATCH v3 0/3] reenable dm_gpio tests, add support for gpio-line-names lookup Rasmus Villemoes
2025-11-04 17:44 ` [PATCH v3 1/3] test: gpio: include in build, and fixup bitrot Rasmus Villemoes
2025-11-05 5:48 ` Heiko Schocher
2025-11-04 17:44 ` [PATCH v3 2/3] gpio: search gpio-line-names property in dm_gpio_lookup_name Rasmus Villemoes
2025-11-05 5:52 ` Heiko Schocher
2025-11-04 17:44 ` [PATCH v3 3/3] test: gpio: add test for gpio-line-names lookup Rasmus Villemoes
2025-11-05 5:53 ` Heiko Schocher
2025-11-05 15:20 ` Tom Rini [this message]
2025-11-11 22:16 ` [PATCH v3 0/3] reenable dm_gpio tests, add support " Tom Rini
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=20251105152018.GO6688@bill-the-cat \
--to=trini@konsulko.com \
--cc=hs@denx.de \
--cc=ravi@prevas.dk \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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