From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: brgl@bgdev.pl, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org, linux@armlinux.org.uk,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH] gpio: pca953x: Print the error code on read/write failures
Date: Fri, 23 Aug 2024 18:25:54 +0300 [thread overview]
Message-ID: <ZsiqApDv_eL9zLn1@black.fi.intel.com> (raw)
In-Reply-To: <20240821114202.2072220-1-festevam@gmail.com>
On Wed, Aug 21, 2024 at 08:42:02AM -0300, Fabio Estevam wrote:
> Print the error code in the pca953x_write_regs() and pca953x_read_regs()
> functions to help debugging.
May be, or may be better to use (implement?) proper filters for regmap
tracepoints? In that case we may drop all these noisy messages and leave
only the fatal ones.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-08-23 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 11:42 [PATCH] gpio: pca953x: Print the error code on read/write failures Fabio Estevam
2024-08-21 12:11 ` Bartosz Golaszewski
2024-08-21 12:16 ` Fabio Estevam
2024-08-21 12:28 ` Bartosz Golaszewski
2024-08-21 12:29 ` Bartosz Golaszewski
2024-08-23 15:25 ` Andy Shevchenko [this message]
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=ZsiqApDv_eL9zLn1@black.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=brgl@bgdev.pl \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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