From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Bartosz Golaszewski <brgl@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Adrian Ambrozewicz <aambrozewicz@nvidia.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Kent Gibson <warthog618@gmail.com>,
Dipen Patel <dipenp@nvidia.com>,
Thierry Reding <treding@nvidia.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpiolib: clear the event clock flags when a line is released
Date: Mon, 19 Oct 2026 10:02:19 +0200 [thread overview]
Message-ID: <179239693683.5934.5426638278693207577.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20261012-gpiolib-event-clock-v1-1-aambrozewicz@nvidia.com>
On Mon, 12 Oct 2026 16:49:45 +0300, Adrian Ambrozewicz wrote:
> gpiod_free_commit() clears the flags that a request sets on a line, but
> not GPIOD_FLAG_EVENT_CLOCK_REALTIME and GPIOD_FLAG_EVENT_CLOCK_HTE,
> which gpio_v2_line_config_flags_to_desc_flags() sets from the uAPI v2
> line config. Once a line requested with
> GPIO_V2_LINE_FLAG_EVENT_CLOCK_REALTIME or
> GPIO_V2_LINE_FLAG_EVENT_CLOCK_HTE is released, GPIO_V2_GET_LINEINFO_IOCTL
> and the line info changed events, the "released" one included, keep
> reporting that event clock for the free line:
>
> [...]
Applied, thanks!
[1/1] gpiolib: clear the event clock flags when a line is released
https://git.kernel.org/brgl/c/d35f61581ee67f8d4d58c325bac813cea528b6b9
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
prev parent reply other threads:[~2026-10-19 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 13:49 Adrian Ambrozewicz
[not found] ` <sashiko-outbox-168236@kernel.org>
2026-10-16 7:46 ` Adrian Ambrozewicz
2026-10-16 9:03 ` Bartosz Golaszewski
2026-10-16 9:39 ` Adrian Ambrozewicz
2026-10-19 8:02 ` Bartosz Golaszewski [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=179239693683.5934.5426638278693207577.b4-ty@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=aambrozewicz@nvidia.com \
--cc=brgl@kernel.org \
--cc=dipenp@nvidia.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=treding@nvidia.com \
--cc=warthog618@gmail.com \
/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
all inboxes | Powered by JetHome®