Received-SPF: pass (google.com: domain of linux-kernel+bounces-207780-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: brgl@bgdev.pl,
	Huichun Feng <foxhoundsk.tw@gmail.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	corbet@lwn.net,
	linus.walleij@linaro.org,
	linux-doc@vger.kernel.org,
	linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	warthog618@gmail.com
Subject: Re: [PATCH v2] docs: gpio: prefer pread(2) for interrupt reading
Date: Mon, 10 Jun 2024 09:38:36 +0200
Message-ID: <171800510952.16671.14245266233040448666.b4-ty@linaro.org>
In-Reply-To: <20240609173728.2950808-1-foxhoundsk.tw@gmail.com>
References: <20240609173728.2950808-1-foxhoundsk.tw@gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>


On Mon, 10 Jun 2024 01:37:28 +0800, Huichun Feng wrote:
> In legacy sysfs GPIO, when using poll(2) on the sysfs GPIO value for
> state change awaiting, a subsequent read(2) is required for consuming
> the event, which the doc recommends the use of lseek(2) or
> close-and-reopen to reset the file offset afterwards.
> 
> The recommendations however, require at least 2 syscalls to consume
> the event. Gladly, use of pread(2) require only 1 syscall for the
> consumption. Let's advertise this usage by prioritizing its placement.
> 
> [...]

Applied, thanks!

[1/1] docs: gpio: prefer pread(2) for interrupt reading
      commit: 7f1e45f4ae7671550e15354ef87194bccd99ecec

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>