linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v9 0/1] gpio: add simple logic analyzer using polling
Date: Mon, 10 Jun 2024 13:26:58 +0200	[thread overview]
Message-ID: <20240610112700.80819-1-wsa+renesas@sang-engineering.com> (raw)

Here is the next version of the sloppy GPIO logic analyzer. Changes
since v8 are mentioned in the patch itself. For those new to this
sloppy GPIO logic analyzer, here is a small excerpt from a previous
cover-letter with the links updated:

===

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.

A branch is here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/gpio-logic-analyzer-v9

And an eLinux-wiki page with a picture of a result is here:
https://elinux.org/Kernel_GPIO_Logic_analyzer

I've used the analyzer in a few more scenarios and on multiple SoCs
(Renesas R-Car H3 and M3-W) and was happy with the outcome. Looking
forward to other tests and comments. From my side this is good to go.

===

Thanks and happy hacking,

   Wolfram

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     | 340 ++++++++++++++++++
 tools/gpio/gpio-sloppy-logic-analyzer.sh      | 246 +++++++++++++
 6 files changed, 698 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


             reply	other threads:[~2024-06-10 11:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 11:26 Wolfram Sang [this message]
2024-06-10 11:26 ` [PATCH v9 1/1] gpio: add sloppy logic analyzer using polling 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
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=20240610112700.80819-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).