From: Dan Carpenter <dan.carpenter@oracle.com>
To: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
Cc: gregkh@linuxfoundation.org, realwakka@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] staging: pi433: add debugfs interface
Date: Fri, 4 Feb 2022 12:02:27 +0300 [thread overview]
Message-ID: <20220204090227.GZ1951@kadam> (raw)
In-Reply-To: <YfzeEHJcd+qvYGZ8@mail.google.com>
On Fri, Feb 04, 2022 at 09:04:32PM +1300, Paulo Miguel Almeida wrote:
> This adds debugfs interface that can be used for debugging possible
> hardware/software issues.
>
> It currently exposes the following debugfs entries for each SPI device
> probed:
>
> /sys/kernel/debug/pi433/<DEVICE>/regs
> ...
>
> The 'regs' file contains all rf69 uC registers values that are useful
> for troubleshooting misconfigurations between 2 devices. It contains one
> register per line so it should be easy to use normal filtering tools to
> find the registers of interest if needed.
>
> Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
> ---
> Changelog:
>
> v5: I had mistakenly forgotten to git add changes to the rf69.(c|h) in
> the previous patch
Oops.
Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
regards,
dan carpenter
next prev parent reply other threads:[~2022-02-04 9:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 7:38 [PATCH 0/2] staging: pi433: add debugfs interface Paulo Miguel Almeida
2022-01-23 7:39 ` [PATCH 1/2] staging: pi433: add missing register contants Paulo Miguel Almeida
2022-01-23 7:40 ` [PATCH 2/2] staging: pi433: add debugfs interface Paulo Miguel Almeida
2022-01-23 11:20 ` Greg KH
2022-01-24 4:14 ` Paulo Miguel Almeida
2022-01-24 4:25 ` [PATCH v2 0/2] " Paulo Miguel Almeida
2022-01-24 4:26 ` [PATCH v2 1/2] staging: pi433: add missing register contants Paulo Miguel Almeida
2022-01-24 4:27 ` [PATCH v2 2/2] staging: pi433: add debugfs interface Paulo Miguel Almeida
2022-01-26 12:03 ` Greg KH
2022-01-29 3:35 ` Paulo Miguel Almeida
2022-01-26 13:21 ` Dan Carpenter
2022-01-29 3:30 ` Paulo Miguel Almeida
2022-01-30 2:57 ` [PATCH v3] " Paulo Miguel Almeida
2022-01-31 13:45 ` Dan Carpenter
2022-01-31 16:45 ` Greg KH
2022-01-31 19:37 ` Paulo Miguel Almeida
2022-02-04 5:06 ` [PATCH v4] " Paulo Miguel Almeida
2022-02-04 8:04 ` [PATCH v5] " Paulo Miguel Almeida
2022-02-04 9:02 ` Dan Carpenter [this message]
2022-02-04 8:55 ` [PATCH v4] " Dan Carpenter
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=20220204090227.GZ1951@kadam \
--to=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=paulo.miguel.almeida.rodenas@gmail.com \
--cc=realwakka@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.