Linux IIO development
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
	Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org>
Cc: nuno.sa@analog.com, linux-iio@vger.kernel.org,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Olivier Moysan <olivier.moysan@foss.st.com>,
	Dragos Bogdan <dragos.bogdan@analog.com>
Subject: Re: [PATCH v2 8/8] iio: adc: ad9467: add digital interface test to debugfs
Date: Mon, 05 Aug 2024 08:39:12 +0200	[thread overview]
Message-ID: <55ab0594033908ccfeb302d5c2fc9adf819bc4e1.camel@gmail.com> (raw)
In-Reply-To: <20240803143806.17bd4e56@jic23-huawei>

On Sat, 2024-08-03 at 14:38 +0100, Jonathan Cameron wrote:
> On Fri, 02 Aug 2024 16:27:06 +0200
> Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org> wrote:
> 
> > From: Nuno Sa <nuno.sa@analog.com>
> > 
> > One useful thing to do (in case of problems) in this high speed devices
> > with digital interfaces is to try different test patterns to see if the
> > interface is working properly (and properly calibrated). Hence add this
> > to debugfs.
> > 
> > On top of this, for some test patterns, the backend may have a matching
> > validator block which can be helpful in identifying possible issues. For
> > the other patterns some test equipment must be used so one can look into
> > the signal and see how it looks like.
> > 
> > Hence, we also add the backend debugfs interface with
> > iio_backend_debugfs_add().
> > 
> > Signed-off-by: Nuno Sa <nuno.sa@analog.com>
> I'll apply the series, but I would like a docs update for the
> debugfs files this patch adds.  That can be a follow up patch.
> 
> Jonathan

will do

- Nuno Sá

  reply	other threads:[~2024-08-05  6:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 14:26 [PATCH v2 0/8] iio: adc: ad9467: add debugFS test mode support Nuno Sa via B4 Relay
2024-08-02 14:26 ` [PATCH v2 1/8] iio: backend: introduce struct iio_backend_info Nuno Sa via B4 Relay
2024-08-02 14:27 ` [PATCH v2 2/8] iio: backend: add debugFs interface Nuno Sa via B4 Relay
2024-08-02 14:27 ` [PATCH v2 3/8] iio: backend: add a modified prbs23 support Nuno Sa via B4 Relay
2024-08-02 14:27 ` [PATCH v2 4/8] iio: adc: adi-axi-adc: support modified prbs23 Nuno Sa via B4 Relay
2024-08-02 14:27 ` [PATCH v2 5/8] iio: adc: adi-axi-adc: split axi_adc_chan_status() Nuno Sa via B4 Relay
2024-08-02 14:27 ` [PATCH v2 6/8] iio: adc: adi-axi-adc: implement backend debugfs interface Nuno Sa via B4 Relay
2024-08-02 14:27 ` [PATCH v2 7/8] iio: adc: ad9467: add backend test mode helpers Nuno Sa via B4 Relay
2024-08-02 14:27 ` [PATCH v2 8/8] iio: adc: ad9467: add digital interface test to debugfs Nuno Sa via B4 Relay
2024-08-03 13:38   ` Jonathan Cameron
2024-08-05  6:39     ` Nuno Sá [this message]
2024-08-03 13:39 ` [PATCH v2 0/8] iio: adc: ad9467: add debugFS test mode support 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=55ab0594033908ccfeb302d5c2fc9adf819bc4e1.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=devnull+nuno.sa.analog.com@kernel.org \
    --cc=dragos.bogdan@analog.com \
    --cc=jic23@kernel.org \
    --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