Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: "J.A. Bezemer" <j.a.bezemer@opensourcepartners.nl>
Cc: linux-gpio@vger.kernel.org, brgl@bgdev.pl
Subject: Re: [libgpiod][PATCH v2] core: fix deselection of output direction when edge detection is selected
Date: Wed, 3 Jan 2024 02:27:44 +0800	[thread overview]
Message-ID: <20240102182744.GA5195@rigel> (raw)
In-Reply-To: <Pine.LNX.4.64.2401021550390.16108@wormhole.robuust.nl>

On Tue, Jan 02, 2024 at 03:52:01PM +0100, J.A. Bezemer wrote:
> Fix deselection of output direction when edge detection is selected in
> make_kernel_flags(). Use correct flag to perform deselection rather than
> a library enum.
>
> For correct usage, there are no visible side-effects. The wrongly reset
> kernel flags are always zero already.
>
> For incorrect usage of edge detection combined with output direction,
> both output and input directions would have been requested from the
> kernel, causing a confusing error. Such usage will now be sanitized, as
> intended, into a working configuration with only input direction.
>
> Signed-off-by: Anne Bezemer <j.a.bezemer@opensourcepartners.nl>

That works for me.

Reviewed-by: Kent Gibson <warthog618@gmail.com>

> ---
>   lib/line-config.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lib/line-config.c b/lib/line-config.c
> index 2749a2a..9bf7734 100644
> --- a/lib/line-config.c
> +++ b/lib/line-config.c
> @@ -381,18 +381,18 @@ static uint64_t make_kernel_flags(struct gpiod_line_settings *settings)
>   	case GPIOD_LINE_EDGE_FALLING:
>   		flags |= (GPIO_V2_LINE_FLAG_EDGE_FALLING |
>   			  GPIO_V2_LINE_FLAG_INPUT);
> -		flags &= ~GPIOD_LINE_DIRECTION_OUTPUT;
> +		flags &= ~GPIO_V2_LINE_FLAG_OUTPUT;
>   		break;
>   	case GPIOD_LINE_EDGE_RISING:
>   		flags |= (GPIO_V2_LINE_FLAG_EDGE_RISING |
>   			  GPIO_V2_LINE_FLAG_INPUT);
> -		flags &= ~GPIOD_LINE_DIRECTION_OUTPUT;
> +		flags &= ~GPIO_V2_LINE_FLAG_OUTPUT;
>   		break;
>   	case GPIOD_LINE_EDGE_BOTH:
>   		flags |= (GPIO_V2_LINE_FLAG_EDGE_FALLING |
>   			  GPIO_V2_LINE_FLAG_EDGE_RISING |
>   			  GPIO_V2_LINE_FLAG_INPUT);
> -		flags &= ~GPIOD_LINE_DIRECTION_OUTPUT;
> +		flags &= ~GPIO_V2_LINE_FLAG_OUTPUT;
>   		break;
>   	default:
>   		break;
> --
> 2.30.2
>

  reply	other threads:[~2024-01-02 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 14:52 [libgpiod][PATCH v2] core: fix deselection of output direction when edge detection is selected J.A. Bezemer
2024-01-02 18:27 ` Kent Gibson [this message]
2024-01-03  8:46 ` Bartosz Golaszewski
2024-01-03 19:17   ` J.A. Bezemer

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=20240102182744.GA5195@rigel \
    --to=warthog618@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=j.a.bezemer@opensourcepartners.nl \
    --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