linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>
Cc: "Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Kent Gibson" <warthog618@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v9 1/1] gpio: add sloppy logic analyzer using polling
Date: Fri, 14 Jun 2024 13:58:46 +0200	[thread overview]
Message-ID: <3bb9b39c-c15f-49e3-987b-26cd47e05f3e@app.fastmail.com> (raw)
In-Reply-To: <slpwvai5q24qwymh7nktihvykmlhi5j3nhqjxruxb6yacruu47@27b7rhykw2f3>

On Fri, Jun 14, 2024, at 12:03, Wolfram Sang wrote:
> Hi Arnd, everyone,
>
>> I could imagine treating both gpio-virtuser and this code as
>> a gpiolib extension rather than a consumer (which is usually
>> part of some other subsystem's driver).
>
> I have difficulties seeing this. For the analyzer, at least. It does not
> extend gpiolib in a way another consumer could make use of it?

That's the same as the chardev support in gpiolib: it doesn't
provide functionality to in-kernel consumers but does give
an interface to userspace.

Arguably, integrating the logic analyzer into the chardev
device itself would make sense from an interface, as you
could define it as ioctls and mmap instead of the debugfs
interface.

Of course we don't want to make it a first-class interface
because of the reasons you explain in the cover letter,
but it would totally make sense to me to call it a
debugging feature of libgpio instead of calling it a
standalone driver.

     Arnd

  reply	other threads:[~2024-06-14 11:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 11:26 [PATCH v9 0/1] gpio: add simple logic analyzer using polling Wolfram Sang
2024-06-10 11:26 ` [PATCH v9 1/1] gpio: add sloppy " Wolfram Sang
2024-06-10 14:30   ` Andy Shevchenko
2024-06-12 10:03     ` Wolfram Sang
2024-06-11 20:03   ` Bartosz Golaszewski
2024-06-12 16:03     ` Wolfram Sang
2024-06-13  8:17       ` Bartosz Golaszewski
2024-06-13  8:27         ` Linus Walleij
2024-06-13  8:50           ` Arnd Bergmann
2024-06-13  9:43             ` Bartosz Golaszewski
2024-06-13 11:48               ` Wolfram Sang
2024-06-13 13:47               ` Linus Walleij
2024-06-13 13:51                 ` Bartosz Golaszewski
2024-06-13 14:20                   ` Arnd Bergmann
2024-06-14 10:03                     ` Wolfram Sang
2024-06-14 11:58                       ` Arnd Bergmann [this message]
2024-06-14 12:14                         ` Linus Walleij
2024-06-16 16:04                           ` Wolfram Sang
2024-06-18  9:23               ` Wolfram Sang
2024-06-18 12:50                 ` Bartosz Golaszewski
2024-06-18 16:09                   ` Wolfram Sang
2024-06-18 18:58                 ` Geert Uytterhoeven
2024-06-18 19:46                   ` Bartosz Golaszewski
2024-06-13 15:04             ` Geert Uytterhoeven
2024-06-13 16:33               ` Wolfram Sang
2024-06-13  8:30       ` Linus Walleij
2024-06-13 11:45         ` Wolfram Sang

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=3bb9b39c-c15f-49e3-987b-26cd47e05f3e@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=corbet@lwn.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=warthog618@gmail.com \
    --cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).