From: Alexandre Courbot <gnurou@gmail.com>
To: Dirk Behme <dirk.behme@gmail.com>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] Documentation: gpio: consumer: describe the con_id parameter
Date: Tue, 14 Jul 2015 14:01:16 +0900 [thread overview]
Message-ID: <CAAVeFuKJJ8DCar-+_J6yEM+bckP1NgwTEk_f_rzChxe11Uf7TA@mail.gmail.com> (raw)
In-Reply-To: <1436593562-5119-1-git-send-email-dirk.behme@gmail.com>
On Sat, Jul 11, 2015 at 2:46 PM, Dirk Behme <dirk.behme@gmail.com> wrote:
> The con_id parameter has to match the GPIO description and is automatically
> extended by the GPIO suffix if not NULL. I had to look into the code to
> understand this and properly find the GPIO I've been looking for, so document
> this.
Good idea!
>
> Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
> ---
> Documentation/gpio/consumer.txt | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/Documentation/gpio/consumer.txt b/Documentation/gpio/consumer.txt
> index 75542b9..d0d1e47 100644
> --- a/Documentation/gpio/consumer.txt
> +++ b/Documentation/gpio/consumer.txt
> @@ -39,6 +39,18 @@ device that displays digits), an additional index argument can be specified:
> const char *con_id, unsigned int idx,
> enum gpiod_flags flags)
>
> +The con_id string parameter has to be either NULL or the prefix of the GPIO
> +suffixes ("gpios" or "gpio"):
It may be useful to explain that "gpios" and "gpio" are both looked up
by gpiod functions, otherwise the reader might wonder how to choose
one or the other.
> +
> +* If the GPIO description is just named with one of the GPIO suffixes
> + ("gpios" or "gpio") use NULL.
add a comma here:
("gpios" or "gpio"), use NULL.
> +* If the GPIO description is prefixed with anything, e.g. "reset-gpios", use the
> + prefix without the "-" as con_id parameter (in this example "reset").
> +
> +In case con_id is not NULL, the gpiod subsystem prefixes the GPIO suffix
s/gpiod/GPIO. gpiod is not a subsystem, just a set of functions.
Otherwise it looks good. Feel free to add my
Acked-by: Alexandre Courbot <acourbot@nvidia.com>
to the next revision.
prev parent reply other threads:[~2015-07-14 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 5:46 [PATCH] Documentation: gpio: consumer: describe the con_id parameter Dirk Behme
2015-07-14 5:01 ` Alexandre Courbot [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=CAAVeFuKJJ8DCar-+_J6yEM+bckP1NgwTEk_f_rzChxe11Uf7TA@mail.gmail.com \
--to=gnurou@gmail.com \
--cc=dirk.behme@gmail.com \
--cc=linux-gpio@vger.kernel.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).