From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Jonathan Corbet <corbet@lwn.net>,
Linus Walleij <linus.walleij@linaro.org>,
linux-doc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v10 0/1] gpio: add simple logic analyzer using polling
Date: Thu, 20 Jun 2024 11:41:57 +0200 [thread overview]
Message-ID: <20240620094159.6785-1-wsa+renesas@sang-engineering.com> (raw)
Changes since v9:
* add comment why late_initcall is used
* use .remove_new instead of .remove
* add needed includes
* use devm for allocating mutex
* remove stray ',' in compatible-array
* remove success message in probe()
Thank you everyone for the valuable feedback so far. Thing is, I am not
sure anymore if this is suitable for upstream. Maybe it is a tad too
hackish. v9 had some ideas for improvements (IIO interface, configfs
support) which I am not going to tackle. For me, it is (and has been)
useful as is, but I need to move on. The latest version of what I use
can be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/topic/gpio-logic-analyzer
If someone wants to continue from here, I am all for it. If that thing
is useful or educational for someone, I am happy. And for those who
don't know what this is about, here is an old coverletter:
===
Here is the next update of the in-kernel logic analyzer based on GPIO
polling with local irqs disabled. It has been tested locally and
remotely. It provided satisfactory results. Besides the driver, there is
also a script which isolates a CPU to achieve the best possible result.
I am aware of the latency limitations. However, the intention is for
debugging only, not mass production. Especially for remote debugging and
to get a first impression, this has already been useful. Documentation
is within the patch, to get a better idea what this is all about.
And an eLinux-wiki page with a picture of a result is here:
https://elinux.org/Kernel_GPIO_Logic_analyzer
===
Wolfram Sang (1):
gpio: add sloppy logic analyzer using polling
.../dev-tools/gpio-sloppy-logic-analyzer.rst | 93 +++++
Documentation/dev-tools/index.rst | 1 +
drivers/gpio/Kconfig | 17 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-sloppy-logic-analyzer.c | 344 ++++++++++++++++++
tools/gpio/gpio-sloppy-logic-analyzer.sh | 246 +++++++++++++
6 files changed, 702 insertions(+)
create mode 100644 Documentation/dev-tools/gpio-sloppy-logic-analyzer.rst
create mode 100644 drivers/gpio/gpio-sloppy-logic-analyzer.c
create mode 100755 tools/gpio/gpio-sloppy-logic-analyzer.sh
--
2.43.0
next reply other threads:[~2024-06-20 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 9:41 Wolfram Sang [this message]
2024-06-20 9:41 ` [PATCH v10 1/1] gpio: add sloppy logic analyzer using polling Wolfram Sang
2024-06-26 10:11 ` Linus Walleij
2024-06-26 11:46 ` Bartosz Golaszewski
2024-06-26 12:02 ` Wolfram Sang
2024-07-01 8:54 ` [PATCH v10 0/1] gpio: add simple " Bartosz Golaszewski
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=20240620094159.6785-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--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 \
/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).