[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYYy_0QnzO-qPusYPFK2qFs=NG-t-X=GRjLg5DHX_k82w@mail.gmail.com>
Date: Thu, 13 Jun 2024 10:30:03 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>, Bartosz Golaszewski <brgl@...ev.pl>,
linux-renesas-soc@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Linus Walleij <linus.walleij@...aro.org>, Kent Gibson <warthog618@...il.com>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org
Subject: Re: [PATCH v9 1/1] gpio: add sloppy logic analyzer using polling
On Wed, Jun 12, 2024 at 6:03 PM Wolfram Sang
<wsa+renesas@...g-engineering.com> wrote:
> [Bart]
> > I really dislike drivers being called in an ambiguous way like
> > "simple" or - in this case "sloppy". I understand why it is - in fact
> > - sloppy but can we call it anything else? Like
> > "gpio-logic-analyzer.c"?
>
> Sure, we can if you prefer. I named it like this to make the limitations
> super-clear. And even with that in place, I still got a private email
> where someone wanted to build a 400MHz-RPi-based logic analyzer device
> with it. Which would not only have the latency problems, but also
> likely have a max sampling speed of whopping 400kHz.
What about "gpio-low-fidelity-logic-analyzer.c"
(+/- Kconfig etc adjusted accordingly)
It says what it is, not really sloppy but really low-fi.
Yours,
Linus Walleij
Powered by blists - more mailing lists