Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Nuno Sa <nuno.sa@analog.com>
Cc: <linux-iio@vger.kernel.org>, Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Olivier Moysan <olivier.moysan@foss.st.com>
Subject: Re: [PATCH 3/9] iio: backend: add debugFs interface
Date: Tue, 16 Jul 2024 19:14:43 +0100	[thread overview]
Message-ID: <20240716191443.397c1278@jic23-huawei> (raw)
In-Reply-To: <20240709-dev-iio-backend-add-debugfs-v1-3-fb4b8f2373c7@analog.com>

On Tue, 9 Jul 2024 13:14:30 +0200
Nuno Sa <nuno.sa@analog.com> wrote:

> This adds a basic debugfs interface for backends. Two new ops are being
> added:
> 
>  * debugfs_reg_access: Analogous to the core IIO one but for backend
>    devices.
>  * debugfs_print_chan_status: One useful usecase for this one is for
>    testing test tones in a digital interface and "ask" the backend to
>    dump more details on why a test tone might have errors.
> 
> Signed-off-by: Nuno Sa <nuno.sa@analog.com>
Debugfs deserved docs as well as sysfs.
Same place in Documentation/ABI/

Obviously we've neglected this in the past, but nice to do it right
nor new stuff.

one trivial comment below.

> +
> +/**
> + * iio_backend_debugfs_add - Add debugfs interfaces for Backends
> + * @back: Backend device
> + * @indio_dev: IIO device
> + */
> +void iio_backend_debugfs_add(struct iio_backend *back,
> +			     struct iio_dev *indio_dev)
> +{
> +	struct dentry *d = iio_get_debugfs_dentry(indio_dev);
> +	char attr_name[128];
> +
> +	if (!IS_ENABLED(CONFIG_DEBUG_FS))
> +		return;
If this happens, d will be null anyway...  Maybe it's worth keeping
as a form of local docs though.

> +	if (!back->ops->debugfs_reg_access || !d)
> +		return;
> +
> +	snprintf(attr_name, sizeof(attr_name), "%s_direct_reg_access",
> +		 back->name);
> +
> +	debugfs_create_file(attr_name, 0644, d, back,
> +			    &iio_backend_debugfs_reg_fops);
> +}
> +EXPORT_SYMBOL_NS_GPL(iio_backend_debugfs_add, IIO_BACKEND);
>

  reply	other threads:[~2024-07-16 18:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 11:14 [PATCH 0/9] iio: adc: ad9467: add debugFS test mode support Nuno Sa
2024-07-09 11:14 ` [PATCH 1/9] iio: backend: remove unused parameter Nuno Sa
2024-07-16 18:06   ` Jonathan Cameron
2024-07-09 11:14 ` [PATCH 2/9] iio: backend: print message in case op is not implemented Nuno Sa
2024-07-16 18:07   ` Jonathan Cameron
2024-07-09 11:14 ` [PATCH 3/9] iio: backend: add debugFs interface Nuno Sa
2024-07-16 18:14   ` Jonathan Cameron [this message]
2024-07-18 14:32     ` Nuno Sá
2024-07-20  9:43       ` Jonathan Cameron
2024-07-22  7:12         ` Nuno Sá
2024-07-09 11:14 ` [PATCH 4/9] iio: backend: add a modified prbs23 support Nuno Sa
2024-07-09 11:14 ` [PATCH 5/9] iio: adc: adi-axi-adc: support modified prbs23 Nuno Sa
2024-07-09 11:14 ` [PATCH 6/9] iio: adc: adi-axi-adc: split axi_adc_chan_status() Nuno Sa
2024-07-09 11:14 ` [PATCH 7/9] iio: adc: adi-axi-adc: implement backend debugfs interface Nuno Sa
2024-07-09 11:14 ` [PATCH 8/9] iio: adc: ad9467: add backend test mode helpers Nuno Sa
2024-07-09 11:14 ` [PATCH 9/9] iio: adc: ad9467: add digital interface test to debugfs Nuno Sa
2024-07-20  9:57   ` Jonathan Cameron

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=20240716191443.397c1278@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=olivier.moysan@foss.st.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