archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <>
To: Ramon Fried <>
Cc: Bartosz Golaszewski <>,
	"open list:GPIO SUBSYSTEM" <>,
	"" <>,
	Stefan Wahren <>
Subject: Re: [PATCH] gpiolib: Take MUX usage into account
Date: Tue, 6 Aug 2019 15:04:34 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Aug 3, 2019 at 3:34 PM Ramon Fried <> wrote:

> From: Stefan Wahren <>
> The user space like gpioinfo only see the GPIO usage but not the
> MUX usage (e.g. I2C or SPI usage) of a pin. As a user we want to know which
> pin is free/safe to use. So take the MUX usage of strict pinmux controllers
> into account to get a more realistic view for ioctl GPIO_GET_LINEINFO_IOCTL.
> Signed-off-by: Stefan Wahren <>
> Tested-By: Ramon Fried <>
> Signed-off-by: Ramon Fried <>
> ---
> Sending Stefan's RFC as patch, as I tested it and it seems to work,
> additionally, an accompanying fix was made by me to gpiolibd to fix a
> display error of the actual result:

This is mostly fine, some style nits so I fixed it up when

Linus Walleij

  parent reply	other threads:[~2019-08-06 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03 13:34 [PATCH] gpiolib: Take MUX usage into account Ramon Fried
2019-08-05  8:33 ` Bartosz Golaszewski
2019-08-06 13:04 ` Linus Walleij [this message]
2019-08-06 13:11   ` Linus Walleij
2019-08-06 19:54     ` Ramon Fried

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \

* 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).