From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpiolib: cdev: add fdinfo output for line request file descriptors
Date: Tue, 20 Sep 2022 22:22:10 +0800 [thread overview]
Message-ID: <YynMkm3ef3tEMw7M@sol> (raw)
In-Reply-To: <20220920135435.15593-1-brgl@bgdev.pl>
On Tue, Sep 20, 2022 at 03:54:35PM +0200, Bartosz Golaszewski wrote:
> Add fdinfo output for file descriptors created for user-space line
> requests in GPIO uAPI v2. The fdinfo file now contains the name of the
> GPIO device that is the "parent" of the request as well as offsets of
> the lines requested. This allows user-space to parse the /proc/$PID/fdinfo
> entries and deduct the PID of the process that requested a specific line.
>
deduce
Using deduct in this sense is unusual (not sure I've ever heard it used
that way, and some dictionaries don't even acknowledge it as a valid
option). In common usage deduct = subtract.
> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
> ---
> drivers/gpio/gpiolib-cdev.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/gpio/gpiolib-cdev.c b/drivers/gpio/gpiolib-cdev.c
> index f8041d4898d1..0f7b5562c410 100644
> --- a/drivers/gpio/gpiolib-cdev.c
> +++ b/drivers/gpio/gpiolib-cdev.c
> @@ -1497,6 +1497,21 @@ static int linereq_release(struct inode *inode, struct file *file)
> return 0;
> }
>
> +#ifdef CONFIG_PROC_FS
> +static void linereq_show_fdinfo(struct seq_file *out, struct file *file)
> +{
> + struct linereq *lr = file->private_data;
> + struct device *dev = &lr->gdev->dev;
> + u16 i;
> +
> + seq_printf(out, "gpio-device:\t%s\n", dev_name(dev));
> +
So "device" rather than "chip"?
I realise it is the device name being reported here, but don't we use chip
for this in user-space?
> + for (i = 0; i < lr->num_lines; i++)
> + seq_printf(out, "gpio-line:\t%d\n",
> + gpio_chip_hwgpio(lr->lines[i].desc));
> +}
So the exploded form. That works for me - in case we ever need to add
more line details, and also makes it easier to grep for a particular line.
Other than the comment nit and the device/chip question it looks good to me.
Cheers,
Kent.
> +#endif
> +
> static const struct file_operations line_fileops = {
> .release = linereq_release,
> .read = linereq_read,
> @@ -1507,6 +1522,9 @@ static const struct file_operations line_fileops = {
> #ifdef CONFIG_COMPAT
> .compat_ioctl = linereq_ioctl_compat,
> #endif
> +#ifdef CONFIG_PROC_FS
> + .show_fdinfo = linereq_show_fdinfo,
> +#endif
> };
>
> static int linereq_create(struct gpio_device *gdev, void __user *ip)
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-09-20 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 13:54 [PATCH] gpiolib: cdev: add fdinfo output for line request file descriptors Bartosz Golaszewski
2022-09-20 14:22 ` Kent Gibson [this message]
2022-09-20 17:19 ` Andy Shevchenko
2022-09-20 17:29 ` Andy Shevchenko
2022-09-20 17:47 ` Andy Shevchenko
2022-09-20 20:35 ` Bartosz Golaszewski
2022-09-21 14:44 ` Andy Shevchenko
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=YynMkm3ef3tEMw7M@sol \
--to=warthog618@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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