From: andy.shevchenko@gmail.com
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v8 1/1] gpio: add sloppy logic analyzer using polling
Date: Fri, 2 Jun 2023 00:39:25 +0300 [thread overview]
Message-ID: <ZHkQDTvk6I2q-9CF@surfacebook> (raw)
In-Reply-To: <20220329091126.4730-2-wsa+renesas@sang-engineering.com>
Tue, Mar 29, 2022 at 11:11:26AM +0200, Wolfram Sang kirjoitti:
> This is a sloppy logic analyzer using GPIOs. It comes with a script to
> isolate a CPU for polling. While this is definitely not a production
> level analyzer, it can be a helpful first view when remote debugging.
> Read the documentation for details.
One note since I have done recent review and realize one issue with debugfs.
...
> + priv->debug_dir = debugfs_create_dir(devname, gpio_la_poll_debug_dir);
If this fails with NULL...
> + debugfs_create_blob("meta_data", 0400, priv->debug_dir, &priv->meta);
> + debugfs_create_ulong("delay_ns", 0600, priv->debug_dir, &priv->delay_ns);
> + debugfs_create_ulong("delay_ns_acquisition", 0400, priv->debug_dir, &priv->acq_delay);
> + debugfs_create_file_unsafe("buf_size", 0600, priv->debug_dir, priv, &fops_buf_size);
> + debugfs_create_file_unsafe("capture", 0200, priv->debug_dir, priv, &fops_capture);
> + debugfs_create_file_unsafe("trigger", 0200, priv->debug_dir, priv, &fops_trigger);
...and any of these is not, we will end up with the file in a root folder of debugfs...
> + dev_info(dev, "initialized");
...
> +static int gpio_la_poll_remove(struct platform_device *pdev)
> +{
> + struct gpio_la_poll_priv *priv = platform_get_drvdata(pdev);
> +
> + mutex_lock(&priv->lock);
> + debugfs_remove_recursive(priv->debug_dir);
...and this one won't remove it.
> + mutex_unlock(&priv->lock);
> + mutex_destroy(&priv->lock);
> +
> + return 0;
> +}
...
However, I haven't checked if it's pure theoretical issue with the current code
base of debugfs or a potential problem. Easy fix is to check an error code and
skip the files creation. Not sure if driver will be useful in that case.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-01 21:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 9:11 [PATCH v8 0/1] gpio: add simple logic analyzer using polling Wolfram Sang
2022-03-29 9:11 ` [PATCH v8 1/1] gpio: add sloppy " Wolfram Sang
2022-03-30 14:51 ` Andy Shevchenko
2022-05-25 15:07 ` Wolfram Sang
2023-06-01 15:58 ` Andy Shevchenko
2023-06-01 15:59 ` Andy Shevchenko
2023-06-05 6:31 ` Wolfram Sang
2023-06-01 21:39 ` andy.shevchenko [this message]
2023-06-02 6:51 ` Geert Uytterhoeven
2023-06-02 6:57 ` Geert Uytterhoeven
2023-06-02 14:07 ` Andy Shevchenko
2023-06-02 7:40 ` Greg KH
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=ZHkQDTvk6I2q-9CF@surfacebook \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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