All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Joel Stanley <joel@jms.id.au>, linux-gpio@vger.kernel.org
Cc: Andrew Jeffery <andrew@aj.id.au>,
	openbmc@lists.ozlabs.org, Eddie James <eajames@linux.ibm.com>
Subject: Re: [libgpiod PATCH] gpioget: Add --line-name to lookup GPIO line
Date: Thu, 02 Dec 2021 13:21:40 +0800	[thread overview]
Message-ID: <06b3258c44f7ce434ec917c53ea4e1967ea75768.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20211201072902.127542-1-joel@jms.id.au>

Hi Joel,

> Systems provide line names to make using GPIOs easier for userspace.
> Use this feature to make the tools user friendly by adding the ability to
> show the state of a named line.
> 
>  $ gpioget --line-name power-chassis-good
>  1
> 
>  $ gpioget -L pcieslot-power
>  0

Awesome!

As someone who has had wasted hours of debugging the wrong GPIO lines
because of incorrect chip/offset calculations, +100 from me.

(or was that +101? I'll have to check the schematic again...)

Cheers,


Jeremy


      parent reply	other threads:[~2021-12-02  5:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01  7:29 [libgpiod PATCH] gpioget: Add --line-name to lookup GPIO line Joel Stanley
2021-12-01  7:29 ` Joel Stanley
2021-12-01  8:29 ` Bartosz Golaszewski
2021-12-01  8:29   ` Bartosz Golaszewski
2021-12-02  4:29   ` Joel Stanley
2021-12-02  4:29     ` Joel Stanley
2021-12-03  3:50     ` Zev Weiss
2021-12-03  3:50       ` Zev Weiss
2021-12-03  6:20       ` Andrew Jeffery
2021-12-03  6:20         ` Andrew Jeffery
2021-12-03 10:18         ` Bartosz Golaszewski
2021-12-03 10:18           ` Bartosz Golaszewski
2021-12-07  6:48           ` Joel Stanley
2021-12-07  6:48             ` Joel Stanley
2021-12-02  5:21 ` Jeremy Kerr [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=06b3258c44f7ce434ec917c53ea4e1967ea75768.camel@codeconstruct.com.au \
    --to=jk@codeconstruct.com.au \
    --cc=andrew@aj.id.au \
    --cc=eajames@linux.ibm.com \
    --cc=joel@jms.id.au \
    --cc=linux-gpio@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.